Fireball

Everyone reporting here, do not report if you get it with any vanilla version. Only report it if you see it with the latest beta. Thanks.

Try again with latest beta 61032.

With the latest beta I always get the message "No entry 'bin\config.bin/RscDisplayMultiplayer/controls/CA_ValueSessions.addons'." When clicking on "Multiplayer" and the server listing comes up. Apart from that everything seems okay. Anybody else getting this?

If anything was removed/disabled, then it was certainly only a mishap and you can expect it back by the official patch, I guess. If it was never really there, well then I don't know - maybe they'll put it in by the next patch. :-)

I've found the AI behavior in patch 61012 to be very erratic to say the least. They get stuck in danger mode and head off wherever they want, when I tell them to "return to formation". CIT Ticket: http://dev-heaven.net/issues/show/6476#note-12 YouTube Video: I hope I could reproduce this somehow.

Corrupted archives don't extract. Something went missing while it was packed, yes.

Helmut, I think in the built in Warfare it's via Communications menu, where you can dismiss them or send them to another squad. Warfare BE offers a "Team Menu" to remove unneeded squad members.

I just noticed that I have massive problems playing more than 0.5-2 hours (max) before the rendering window detaches. I think it has to do with the complex and long games like Warfare Benny Edition. I've filed a CIT ticket about it. Please let me know if you experience the same - apparently short rounds in less complex missions do not exhibit that problem. EDIT: Reverted to 60091 recently and it's much less prone to the resource leak(s) then (freeze/crash only happens every 4 h avg.), so it must have been worsened in 60141 and later.

Eh? Did anyone of you read the original post about the A2 CIT? So could you please stop posting dumps and bug reports into this thread and use either the CIT or the Beta Testing Forum? When reporting CTDs please always use the latest BETA: http://www.arma2.com/beta-patch.php The BETA patch installs as mod (thus can always be reverted) and is multiplayer compatible.

This ESRB warning is not in every distribution, where did you buy it/do you live?

We also did some testing yesterday and came up with that: Sorry for the little audio desync, but tell me what you think. It's not a ghilie suit and it's also around 250m distance, but it's in the shadow and at the little wood. Potentially the issue is that shadows make you feel too safe, when they are in fact not observed/applied to detection rating.

Well, they do adjust after you walk on for a while, it just takes longer And for some soldiers it's impossible to get into the new formation since they cannot/should not run faster to catch up next or ahead of you for the new postition - do you want an outpowered soldier in the battle just for the sake of a formation change while running?

Not exactly...the grass layer should always be on...if grass is not rendered in distance, well, it's still there, basically. So feet/boots are not shown, for example, or if you kneel, the leg/knee is not visible then...etc., but it should never be off.

I think the grass layer needs to be "observed" by the AI - or properly observed rather. Right now I have the feeling that the AI does ignore the grass layer, or, it just sees any head sticking out equally well as the body wholly exposed. http://dev-heaven.net/issues/show/5785

First, not only bugs that get highly voted on in DH are fixed, the voting is mainly for features. The second issue already has a ticket on DH: http://dev-heaven.net/issues/show/2436 That's the same bug as with the F-35. EDIT: not exactly the same...but it's keeping on a laser designated target, but not with the laser on the plane

Copy the BETA shortcut from your game directory, this should fix it.

Hmm, well then I'm not absolutely sure, if it worked in 1.04. Maybe if something was changed in the mission, so the chopper gets in combat mode or something if it feels threatened, or whatever in detail causes the "hanging" chopper. EDIT: but what you described are the exact symptoms of the bug I mentioned (and reproed)

Thats this bug: http://dev-heaven.net/issues/show/3919 It happens when the chopper gets under fire in the LZ, in the bug ticket is a nice repro mission which demonstrates it reproducibly.

That stutter you encounter is after playing for hours, when the memory leak starts to gnaw on your ArmA II. When it starts stuttering, you can play for another 30-40 minutes and it will eventually detach the rendering window and the arma2.exe process will hang. Or are you talking of something else?

Happens to me too on WinXP 32bit.

Thing is, if you do not delete or rename your beta folder, it might happen, that files get left over (from earlier patches) which shouldn't be in the beta folder anymore. This affects mainly when there are official patch releases (e.g. 1.04) and you install new betas going from this one over old betas (e.g. 1.04 beta). Also, in earlier 1.04 beta patches, the installer did forget to put -mod=beta; in the BETA shortcut placed in the game directory, thus if you have troubles, just use the current shortcut from there and overwrite your old one on the desktop/wherever.

Looks like a driver issue to me, I cannot see this on my Nvidia 8800 GTS 512 MB with drivers 191.7.

Can't you tweak it to autocenter it and give some resistance with the configuration tools from Logitech?

no it should continue with the next mission

Did you try the latest beta patch?