-X- Charlie

@Admiral Sombrero I've been having an issue with stuttering and textures. While moving, I would get a series of stutters and some serious texture loading issues, blurring etc. How did you fix it?

To update, deleting (obviously backing-up, too) the MSVCR100.dll files from my ArmA2 directory and Battleye sub-directory seemed to fixed the issue when starting the game. If it creates any other issues, I am yet to find out.

Yep, similar error to walker, expect my dll that is missing is MSVCP100.dll. Trawled the net for a solution, and found the same as you have suggested jaynus. Installed the C++ redistributable, and I'm now getting this error, even when trying to run vanilla ArmA:OA:

@Speederin: I know that you said that you tried to manually update Battleye, but did you do it correctly? My video here demonstrates the problem I was having earlier this evening, it sounds like the same one as you: http://forums.bistudio.com/showpost.php?p=1828225&postcount=10 I went to update my Battleye .dll and accidentally replaced my ArmA 2 BEClient.dll (in ArmA 2/Battleye) with the new ArmA 2: OA one from the BE wesbite (which should have gone in ArmA 2/Expansion/Battleye). Luckily, I realised, and got it the right way round eventually. Just checking that you didn't make the same mistake as me, as I'm now up and running fine.

Something like my video, here? I was getting this earlier this evening. Manually updating my Battleye client .dlls sorted things out.

Overclock, overclock, overclock. Exactly the same rig, apart from a GTX260, with my Q6600 @ 3.0Ghz. Trundles along happily, never really lower than 30FPS and genereally 40FPS+ in most situations. ArmA2 is a highly CPU intensive game. Take heed of this.

Grea-... oh, nevermind. I already bought the game... :P

Absolutely nothin', say it again now y'all! Sorry. :o

Just tried this myself, as I was thinking of doing an ambush mission. Only way I could get it to work was by synchronising the trigger with the waypoint before the 'open fire' waypoint. I assume the trigger activation gives permission for the AI to move onto the next waypoint [makes sense]. Now here is my question. In this ambush situation, is there any way to make the person being amushed hold fire until they are fired upon? I tried to simulate this using the same trigger as above [i.e. when the ambushers detect BLUFOR they open fire, engage at will and when the ambushees are in the same trigger they can also open fire, engage at will], but the BLUFOR seem to endlessly hold fire.

My ArmA2 folder weighs in at 8.13GB.

How is this handled MP wise? Can just the host have his AI modified and it will be reflected to all clients?

Used the ArmAholic optimisation thread, further jump to ~3400.

Right, rolled back to the 182.50 WHQL drivers and jumped to ~3200. Worth looking at if you own a pre-GTX295/285/275 card.

ArmA 1.02 All settings as per OP. Q6600 @ 3.2Ghz GTX260 896MB C216 XT (GTX280 Clocks) 4GB DDR2 PC8500 @ 1066Mhz Vista x64 186.08 Beta Drivers 1680*1050 2896 Points on Run Three Is this about right, or is something going wrong here? I can't make my mind up.

Yeah, I'm slightly confused. Ship direct? To who? I ordered mine from Amazon on next day delivery. I hope mine arrives tomorrow...