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 :(

Hello everyone, Recently got a copy of OA and loving it so far, apart from a couple of niggling issues: I play a lot using the mission generator wizard, using it to generate a "combat" mission with secops and support etc. It worked fine in vanilla ArmA, but now when playing a combat scenario in OA with the KSK troops, some of them insist on switching to their pistols, even when engaging at 400m and beyond. If I teamswitch to them, they have ammunition available - and their currently loaded magazines are not empty. Bit of an immersion killer, and frustrating as hell. Any ideas? The other issue, which I assume is addressed a lot on the forums is the driving AI. Even when a vehicle is already on the road, if I give it a move order, it moves off-road for a bit, then returns to the road - which is incredibly annoying and unrealistic. Knowing BIS however, I am sure this is work in progress :) Any solutions to the first issue would be appreciated!

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.

Well that is disheartening! I can forgive the driving to a certain extent - it is one of those things I have just come to accept. But the promises of having both ArmA2 and OA content in one, yet finding that you might as well just run the games separate (because next to no features have been ported) is a bit of a kick in the teeth to be frank. I love BIS games, I can see through the bugs and enjoy them for what they are - but when things are just broken, and there is such a disparity between the quality of OA's content and the original ArmA2 content - after it was promised that everything is compatible etc, it is slightly disappointing. Edit: Also @Sputnik re the pistol thing - I never had any such issue in ArmA2 vanilla, the issue only started for me in OA :(

Good to know that it is a known bug and I am not just losing my mind! Having played a little more, especially with exiting ArmA2 content, there are a few things that are now glaringly obvious - such as ArmA2 weapons having a laser pointer at them and no way to use it, and the one that disappointed me most - the AH-1Z Cobra is pretty much un-useable. I can't view ammo levels in the Cobra without being the gunner, and there is now no HUD. This is in the Armory, I have not tried in the editor yet. Are there any plans for BIS themselves to fix these issues? I couldn't find anything about the Cobra in the community issue tracker anyway. I really do hope they plan on bringing at least some of the ArmA2 content up to OA's level, some of the ArmA2 content (such as the Cobra) is barely worth playing any more IMO.

This actually happens in real life. Banking and turning without applying rudder can result in the aircraft yawing from side to side when you re-align.

I loved the SPR in ArmA, but in ArmA2 the model and textures seem really low-res for some reason.

Hello all, I really enjoyed the first ArmA and am currently loving ArmA2! I do have a few questions regarding gameplay however. Firstly, if I call in a CAS strike in one of those "Combat" scenarios that you can make - will the ordinance impact right at the point I call the airstrike in, or will the aircraft look for a suitable enemy target in the area first? With no laser designator in your kit there is no way for me to give the strike a target that is moving. The reason I ask is that I tend to come across a few APCs in these missions - and the squad that you start with has no AT capability at all. I can evade some and take a different route to the objective - but there have been a couple of times where I have been engaged by the APC and as such I need to get rid of it - especially if it is near the SecOp objective. Secondly, I am starting to think that I am an awful tactician. If I require to assault a position, I try and approach it in a way that I can see the enemy and they can't see me. I start to open up, but sometimes my team-mates (still talking combat scenarios, not campaign) just don't open fire along with me - even after I "spot" the enemy. Every time I try to move position - my team ends up getting killed, 90% of the time, me first. Am I missing a fundamental rule of combat here? I guess what I am asking for is some advice on how to effectively command my team and take a position with minimal losses. Telling a team member to "attack" a unit specifically usually results in them running out of cover and getting killed, so I am not really sure how to go about completing objectives well rather than by the skin of my teeth and after several "first aid" actions. Lastly, when flying a Cobra - I am having trouble commanding the gunner. Sometimes he will refuse to switch weapon, no matter what I do. To give an example - I target another enemy chopper, and the gunner starts popping away with the cannon. Fair enough, but I need to kill it slightly faster than that. I press F repeatedly to select sidewinders, and my character repeatedly shouts "missiles". Yet the selected weapon only flickers to hellfires for a split second before going back to the cannon. Meanwhile the enemy aircraft has fired missiles of its own and I'm dead. Am I doing something wrong? Sorry for the wall of text - I love this game, and I would like to learn to play it properly rather than just using guesswork all the time. Sure I could lose my entire squad getting the objective completed and then go pick up reinforcements - but that's not playing the game right imo ;) I am also very glad to see that ArmA2 has stopped the AT-soldier stupidity of ArmA - where they used to fire AT rockets at infantry, leaving me with no AT capability at all :D Cheers BIS for an awesome game :)