Operation Arrowhead performance optimizations/comparisons

[jpinard]

====note====

Do NOT use the latest NVidia beta drivers. They break the in-game anistropic filtering.

====note====

As some had already mentioned there's a performance hit in Operation Arrowhead. Not just in Takistan, but also running Chernarus/Utes missions with the OA launcher. This thread is to help people get performance closer to vanilla ArmA2 1.07. Some may wonder why Chenarus would run slightly slower with OA than Vanilla ArmA2. The reasons I can identify are below:

* OA allows us to set the audio sample number. By default it is 32. ArmA2 only allowed 16. ~cpu hit.

* Graphic additions to the game. These include SSAO Post Processing, extra camera shake, muzzle flash, and a host of other improvements. ~graphic card hit.

* Armor and ballistics has been overhauled. ~cpu hit

* Game doesn't yet have A2 v1.07 enhancements. ~cpu/graphic hit.

All in all, for a new release the game is in pretty good shape and no doubt when it's upgraded to match A2 v1.07, adds LMA & x64 we'll be flying
I'l keep this up-to-date, and if the bold red text (below) is diffcult to read let me know and I'll change it.
--------------------

Performance Tips Below:

--------------------

1. Set Post-processing to Low to somewhat match ArmA2's High PP settings.

2. Stop using a RAM Drive.

3. Don't use maxmem, winxp, cpucount, or exThreads switches if you have a dual-core or quad-core processor.
---edit--- Until BIS gets the OA code up to v1.07 I'm going to suggest people use the following parameters in the launcher:

Dual-Core processor:
-nosplash -cpucount=2 -exThreads=1
Quad-Core processor:
-nosplash -cpucount=4 -exThreads=7
Hexacore processor:
-nosplash -cpucount=6 -exThreads=7

(I'm not sure if the -winxp and -maxmem values are still required for XP users, for most people the answer would be "no")

4. I always suggest gamers turn off Hyper-threading technology (aka HTT) as it almost always decreases game performance. This isn't as necessary now since the game shuts down more than 4 cores and you specify the # to be used above... but I still suggest it be turned off in the BIOS.

5. Turn VSYNC OFF <--- this alone makes at least a 5 fps difference and makes the game much more responsive.

6. Play with "rendered frames ahead" values and match it to your ArmA2 OA config file. (0-8 are valid figures)

7. Windows Vista and Win 7 users - For optimum compatibility make sure you're running as an administrator... Right click the new icon, go to the compatibility tab, check-mark "run as administrator" box. You will need to redo this after Securom sends you SN activation number.

8. NVidia SLI is not working by default. You may need to rename the executable "arma2oa.exe" to something the NVidia card will try and enable SLI for. For example you can trick it by using Crysis name "Crysis.exe" instead of "armaoa.exe". See post #8 for more details http://forums.bistudio.com/showpost....45&postcount=8

9. You will need to setup a new graphics executable in your NVidia or ATI/AMD control panel (see example below).

Click for large pic: http://www.jeffpinard.com/OA_graphic_settings.jpg

[Fox '09]

thanks. I think I have some ideas on how to improve performance as well - will edit post later.

[Dwarden]

ARMA 2 defaulted to 16 3D audio samples at once
OA defaults to 32 3D audio samples at once and allows to choose from 16 to 128 in steps of 8
2D samples aren't counted into this counter ...

[jpinard]

ARMA 2 defaulted to 16 3D audio samples at once
OA defaults to 32 3D audio samples at once and allows to choose from 16 to 128 in steps of 8
2D samples aren't counted into this counter ...

Fantastic information. Thanks Dwarden.

So for Apples to Apples comparison when an individual using v1.07 ArmA2 graphic settings @ "Very High" and 3500 view distance... in OA you need to:

* Turn audio samples down to 16.
* Turn PP down to Low.
* Match all other settings.

[Spozzi]

OK gents,
Ive come to a conclusion here it is "Operation Arrowhead doesn't support SLI yet"
Meaning if you are like me and have a dual GPU card (for example my 9800GX2) then arrowhead is only using 1 where ARMA 2 for me uses both.
For me personally regardless of my setting I always get the same FPS from the benchmark (and in game play) with 1 or 2 GPU'S enabled.
This explains for me anyways why I see most people who say it has an improved FPS have fast SINGLE GPU cards and most people suffering from poor performance have a DUAL GPU card.
Before you ask I have already tried adding the .exe in the nvidia/ATI control panel like the OP says that doesn't seem to help, I'm curious to see if my theory is correct so if your using a dual card switch one of them off via the control panel and then post your results...

[jpinard]

OK gents,
Ive come to a conclusion here it is "Operation Arrowhead doesn't support SLI yet"
Meaning if you are like me and have a dual GPU card (for example my 9800GX2) then arrowhead is only using 1 where ARMA 2 for me uses both.
For me personally regardless of my setting I always get the same FPS from the benchmark (and in game play) with 1 or 2 GPU'S enabled.
This explains for me anyways why I see most people who say it has an improved FPS have fast SINGLE GPU cards and most people suffering from poor performance have a DUAL GPU card.
Before you ask I have already tried adding the .exe in the nvidia/ATI control panel like the OP says that doesn't seem to help, I'm curious to see if my theory is correct so if your using a dual card switch one of them off via the control panel and then post your results...

If it is not using SLI, then you need to rename the executable "arma2oa.exe" to something the NVidia card will try and enable SLI for. For example you can trick it by using Crysis name "Crysis.exe" instead of "armaoa.exe". Usually a dual-gpu card should work fine if you just have the multi-gpu option selected in the Nvidia control panel (that's the way it was for my GTX295 which I no longer have).

[Fox '09]

hey guys, try tuning HDRprecision to 0 in your arma2oa config.

[Spozzi]

If it is not using SLI, then you need to rename the executable "arma2oa.exe" to something the NVidia card will try and enable SLI for. For example you can trick it by using Crysis name "Crysis.exe" instead of "armaoa.exe". Usually a dual-gpu card should work fine if you just have the multi-gpu option selected in the Nvidia control panel (that's the way it was for my GTX295 which I no longer have).

Thanks mate, i can confirm that this works for me i went from getting 20 FPS in the OA benchmark to 43!!, even though I get 50 in the arma2 benchmark I can honestly say that OA is a MUCH SMOOTHER experience then Arma 2. So i guess we should spread the word that renaming the .exe enabled SLI for me. It might not work for everyone but its worth a shot to anyone who is getting poor performance.

BTW those benchmarks were with the following settings;
texture Detail = Very high, all other settings High (including PP), 64 sample rate, View distance 3000, No AA.

[Richey79]

Note that the .exe is not set as Largeaddressaware (as 1.07 Arma2 build currently is), but can easily be changed to be such.

Try http://www.4shared.com/file/-2fB1A0O/LaatiDo.html if you wish to check how this affects your performance.

[Sethos]

Well,

As I said in the impression / discussion threads for Operation Arrowhead, I'm one of the lucky few to suffer some problems with the game, despite having ArmA II run butter-smooth without any issues.

My settings for the game I've tried to closely match ArmA IIs settings, View distance of about 3000, everything on Very High except for PP, which is on low due to its changes, AA on Disabled and AF on Normal.

Running the benchmark gives me a 35FPS result, which isn't bad but far from acceptable and nothing like the performance in A2.

It isn't just low performance, game seems to suffer from constant micro-stutters that just trickles down and have an adverse effect on everything. In Zargabad it's especially bad, performance is also abysmal - Feels like the computer is struggling bad and sometimes the walk / run animation on the soldier won't even play, he'll just float because the game is too busy trying to render / deal with other issues, it's that bad!

I tried a different driver set ( ATi ) with no effect, I tried defragmenting my drive with 0 effect whatsoever, I tried renaming my .exe to both arma2 and crysis with no effect and now I'm lost for things to try, except waiting for a patch or something.

My specs are following;

Windows 7 64Bit
Core i7 940
ATi 4870X2
6GB DDR3

I solved all my stuttering problems in ArmA II by disabling HT and it's still disabled, with no effect. I'm running the game without extensions, so no -maxmem etc.