the_duality

The only real issues I have found are pretty small. Sounds on the British .50 are the same as a 7.62, which sounds like a config issue more than a serious bug. There are some bugs with sound with the new Warrior - and the MG seems to muzzle flash each time the main gun fires :P The only other thing is the power of the Warrior 2 main weapon - that seems a little high although I might just not know what I am talking about :P

DLC is fantastic so far - really pleased with it. Mission 2 of the campaign however - is proving incredibly frustrating. Not because of the mission itself, but because of the terrible driving AI. I am trying play the mission "properly" (so to speak) by using the commander seat in the vehicle and giving move orders via the map. Sometimes though, the AI just has a complete brainfart and goes exactly where he shouldn't and gets us all killed. Or, he just stops randomly. While being targeted with mortars. Bleh. Don't give us so many driving based missions when the driving AI simply isn't up to scratch :(

I ran the game after installing BAF, and it told me I needed 1.54 :(

I fixed it by downloading that file from here: http://www.dll-files.com/dllindex/dll-files.shtml?msvcp71 and placing it in the same directory as sprocket.exe. Downloading at 200kb now - better than the 4kb i got with direct download

Shame about the time, was looking forward to playing some tonight :) Something to look forward to when I get back from work tomorrow!

Pre-purchased. Thankyou BIS for showing us that DLC can be done right :) Can't wait to install this!

Probably a stupid question - but Sprocket is the place to pre-order if you want the DLC for retail version right? I ask simply because I have never purchased from Sprocket before - just want to check before my payment details get sent there ;)

I have found that CAS strikes can be very "hit and miss" (no pun intended). Sometimes they will drop exactly where you put the marker, sometimes they will engage enemies around the marker with other weapons and sometimes they don't turn up at all - most likely distracted by another enemy if you have the ambient combat module on the go. I have given up trying to work out the science behind it :P

I will be buying it.

Heh, maybe I should have elaborated further :p I can't find a way to have AI units lase targets in a consistent manner - I have had units switch back and forth between rifle and laser designator, work their way far too close to the target or just sit there pointing their rifle at the target :/ I am also having a hard time working out the logic that dictates to the AI when to use a designator. Is it when there is one available and there are no other nearby AT assets? Or is it more complex than that? I am still very much learning the editor (I used to just use the wizard to generate missions) so any pointers appreciated :)

This is the one single thing I would like to see expanded upon in ArmA - and then I can finally be happy with the game. Bombing without a forward observer is next to impossible, and I have not been able to get the AI to lase targets in the editor :(

Just done some more testing - it appears to be the Scout and Paramedic units of the KSK specops squad that are using their pistols over their default rifle. Hope this narrows it down for the devs :) EDIT: Posted it on the community bug tracker too :)

Took me a while to realise there were explosives in it that I could use :P

From what I remember, it appears to be random KSK units when playing as part of a KSK specops squad. I have only noticed it in the wizard built "combat" missions. Last time I played, the paramedic and one of the operators switched to pistols. When I teamswitch to them, the game immediately switches the weapon I am holding from pistol to rifle - and there is ammunition left in the rifle. When I teamswitch away again, the unit switches to pistol again. It only happens to KSK units that have a G17 pistol, from what I can tell. No issues with any other units in OA or vanilla ArmA2. Thanks for the reply :)

This is what I have noticed. It worked fine in vanilla ArmA2, and it works fine with all other troops. It only seems to be the KSK troops with the G17 affected.