Fireball

I was trying to register a new unit tonight, and I think it wants me to log in on the site. But instead of the login dropdown I just get an empty dialog: https://i.imgur.com/Lprg5nH.png

Wow, I've really never seen that, this is awesome! :o :D Then I guess what I'm referring to with the sun warmth is more the colour tone of the sunlight during evening hours which is usually more red-ish due to atmosphere. For my comparison animated gif, I also used an evening time. I thought the original goes better with the evening tint, daylight tint with clear weather looks perfect *looks outside*.

Hi googlova et al, I revisited the topic of the "missing sun" or at least "missing sun warmth" of the visual upgrade and this is the best I came up with (bottom right you can see the watermark on the dev build one); and to say yet, the weather setting was completely "clear" on both shots - in fact I created the first pic on dev build the way i placed the player initially in 3DEN editor and then just reverted to stable build and only loaded the same scenario to take the second screenshot. EDIT: Btw., do you see what happens to some of the arid vegetation on the floor in front of the player? Some of the shrubs just disappear and the grass becomes a little juicier.

Sorry, I just had to chime in now; I saw those screenshots and downloaded dev immediately: versus new: And my first impression was: Who turned off the sun? Second thought was: This can't be the same weather condition! But yes, it is. :( So I checked now in dev build and really: The warmth of the sun is completely gone. There is no "warm summer day" mood anymore, it's all cold and gray, even though the weather is supposedly clear at a Mediterranean noon! This needs remediation before thinking about release.

You could host a Zeus mission! That would be awesome! Simply prepare a short story arc and take 10 min for initial setup and then proceed and improvise.

You've got a point there. Let's leave it here - it won't be supported anymore though.

You must know that Iceman is now full-time busy with the FT, but probably can only (if even) catch up with what was reported recently, which in turn shows that FT was left dwelling alone for too long, as Astaroth (back in time) was only doing it aside his main job in QA and was also only appointed, when the FT was already bursting with ticket. Then, what you missed within those xx% new tickets is probably that 80% of them are defacto unusuable due to reporter XYZ seen an issue and thus had a bad day and went on the FT to rant what should be improved in his opinion, instead of delivering a proper bug report. Also within those new tickets are probably many untreated dupes (if you see some, let me know). I've also seen that crash tickets are assigned (probably internally passed on to devs) and hardly ever closed, since noone can really confirm that that particular crash is resolved, as for end users one crash might look another. So we can also assume that many assigned crash tickets were already resolved without us/you knowing. Also, the cartoon in the beginning totally neglects that multi-core CPU support is in the game for a long time. Only because your cores don't all max out while you're playing, you can't say that there's no SMP support, but there's only so much you can divide among the cores without risking the game going fubar, so only expect small steps, but (hopefully) safe ones.

They're onto it: http://feedback.arma3.com/view.php?id=18733 But it's a bug that's apparently a bitch to reproduce. Can anyone check if 1.24 RC is affected?

Since that overhaul of the AI difficulty settings (removal of separate difficulty sliders and Super AI) the AI accuracy is still too high in all including the lowest preset. I currently have to teach DS admins on how to provision an .Arma3Profile using custom difficulty class definitions, so AI doesn't one-shot you the very instance they spot you, across 200+ meters. Accuracy as low as 0.2 make sense eventually as far my tests go; skill may be higher (such as 0.5). There is certainly something wrong...some hyperbolic attenuation of accuracy within the slider range.

It's more than a filter issue for me. I can filter correctly (or not filter at all), and my DS is not listed on Steam, but only on GS.

Please drop me a PM with links to solved tickets, so I can set them resolved or close them.

Can it be or is static weapon re-assembling (after it was disassembled and divided to two different players) broken again in 1.16 stable? Might have to use a DS in order to test it... EDIT: Nah, it was too long since I've done it before, so I/we did it wrong. It's kinda counter-intuitive, that you get two backpacks next to eachother when you disassemble them, but to assemble them you can't put both on the floor, you gotta keep one on.

I would agree with you if engaging the turned out crewmen was a serious option (in the game), but in fact it isn't, specially while its moving. The AI turns in extremely quickly (maybe a tad too fast) and the attacking AI in the video from pappy.rabbit does not seem to realize this. There is certainly room for improvement.

That's actually mostly a mission/scripting issue, not the other way around. I mean of course when they do react.

Try this again, when you're alone, e.g. in the scouting missions.