-TwK-Danny

It makes forcing HDRPrecision in the ArmA2.cfg file actually work. So if you force change HDRPrecision=8; to HDRPrecision=32; you will lose alot of performance, because your HDR is better. This is a horrible change because i used to use this to fix the post process bug in the game. The Post Processing option ingame does not work after restarting the game, its been this since the devs screwed it up in a early patch. Why isn´t this fixed yet? Basicly if you set it to "very high" and restart the game it will be back to low/off (even though it still SHOWS as "very high" ingame). You need to change it to e.g. high and then back to veryhigh to get it working..

Suma, this patch is causing some serious performance issues on my rig. There is a 33% measured drop in performance. I do not know why, i use the exact same settings and run the same mission for testing (start of village sweep). I cannot comment on stuttering because the game, with the beta patch, is compleatly unplayable. My system is a AMD Phenom X4 965 (a quadcore at 3.4GHz), 4GB of DDR 7-7-7-24-1T memory and a AMD Radeon HD 4890 1GB graphics card. Here are 2 screenshots with a FPS counter in the top-right corner. This is with the official 1.05 patch: http://img23.imageshack.us/i/arma22010042319323299.jpg/ As you will see, its running at 30fps. But with this beta patch: http://img691.imageshack.us/i/arma22010042319345234.jpg/ The performance drops to 19fps on the exact same scene! Basicly for me these current tweaks are not working at all. If you want a screenshots of what settings i use i can take one. But its 1920X1200, all veryhigh except for AA, terrain and detail (all three set to "normal"). 3600m draw distance.

Depends on what people are playing. Maybe your friends are only playing multiplayer? Fact is the campaign runs like crap on the majority of computers. I can imagine high end core i7s and 4890 crossfire/gtx285 sli systems to handle it. But normal PCs - no chance. I mean with a PC like yours, what fps do you get on the harvest red mission (city mission)? huh? Tell us what you define as "fine". This is my HD4890 trying to run this mission: at 1920x1200 everything on lowest http://img23.imageshack.us/img23/3205/arma22009101911001842.jpg WOW 19 fps! Yeah sure there are no problems at all with performance in this game. Only the fact that this game is compleatly unplayable. Lets try 1280X800: http://img7.imageshack.us/img7/999/arma22009101911004532.jpg WOW 20 fps! The game is looking like operation flashpoint 1 and still performs like ... well ... nothing really runs this BAD so there is no reason to compare arma2 to anything. ArmA2 has gone as far as setting a new standard on how shitty a game can run on a PC. Have you read other forums? The only thing people whine about ArmA2 is the godawful performance. Nobody enjoys gaming at 20fps. And again, I am only talking about the actual campaign. Multiplayer runs much better for me (on almost max settings even, 4xAA), as do the single missions. Its only the campaign that runs like crap. Lets see your performance? Can you achive 60 fps (on lowest possible settings) in that missions? Please do show.

Been a while since the last beta. May one hope for performance improvements? :D

This setting (GPU_MaxFramesAhead) actually depends on the fps youre getting. With tripplebuffering (wich arma2 uses), the optimal values are as follows; Fps below refreshrate: GPU_MaxFramesAhead=1; Fps above refreshrate: GPU_MaxFramesAhead=0; Since ArmA2 is so demanding, most computers cannot keep fps above 60 (or whatever you set refreshrate to) so hence for most people MaxFramesAhead should be set to 1 (to reduce mouselag). Read more at: http://www.anandtech.com/video/showdoc.aspx?i=3601&p=7

Why cant we still turn Vsync off ingame? That would help mouse-resposiveness when fps is "low", ie all the time in this game.

Tophe, force vsync off in nvidias control and disable mouse smoothing - is mouselag reduced? Also set "max frames to render ahead" to 0 (just to try). Does that reduce mouselag futher?

It should be under "controls", on the right side below Y axis and X axis settings.

The mousesmoothing at 0 fixes one of the cause for mouselag in ArmA2. The second issue is forced Vsync with TrippleBuffering. At 60fps, mouselag isnt quite the issue. But when fps drops (wich you can be certain it does in this game), due to timing with frames, you WILL encounter input lag due to the delays caused by the Vsync. You may also not want to forget the fact that tripplebuffer takes up more video memory aswell - wich might mean performance drops when you run out of vidmem. An ingame option for Vsync on/off is a wanted and elegant fix - and honestly i expected this to be added to the game a long time ago. Any Dev care to comment?

Well they still refuse to add Vsync options to config/ingame. Disabling Vsync (incl tripplebuffer) would probably remove mouselag once and for all (i dare say).

BIS should really flag their exe or give us a 64bit version of ArmA2. This game uses about ~600mb swapfile and i have 4GB of RAM installed. Note that no other game (including Crysis Warhead) have ever used this much of the swapfile on my PC. This could be the cause of stuttering and slow texture-loading that i get.

Hi Just thought i´d make a thread about this here since its starting to annoy me. Everytime you launch ArmA II, with post process set to VeryHigh, the game ignores this and the graphics look ugly, like with post process is set to low. What you have to do, each time you start the game, is to set post process to low and then back to veryhigh to get the effects back. This is how the game looks just after launching it: Please notice the look on the trees for example. Now this screen shows that it looks like this with PostProcess set to VeryHigh: Now, to fix this, we have to set PostProcess to e.g. low and then back to VeryHigh. Only then do we get the correct look, as you can see here:

New one out, 58932. [58930] Fixed: Broken kill scoring in MP (two points for unit kill).

Yeapp, i can confirm setting HDR to 32 fixes the problem. Basicly the devs should fix that the HDRPrecision command doesnt change with postprocess (should be simple enough).

Yes, the game is bugged with 8GB RAM or more. So if you have, like you, 12GB installed you need to use the -winxp switch.

Thanks for testing JW Custom! May I ask what OS you use? kklownboy, thanks to you too. Setting the arma2.cfg to read-only does not help. The postFX is already at 3, and ingame always show as veryhigh. My config: language="English"; adapter=-1; 3D_Performance=48387; Resolution_Bpp=32; Resolution_W=1920; Resolution_H=1200; refresh=60; Render_W=1920; Render_H=1200; FSAA=0; postFX=3; HDRPrecision=8; lastDeviceId=""; localVRAM=1068449792; nonlocalVRAM=1459253248; I´m thinking its maybe OS-dependant seeing as you have XP.

Of course I haven´t set it to read-only. This bug has already been reproduced by many others and was introduced when BIS "fixed" that PostProcess was enabled by default even with the settings disabled (Basicly, same as now but the other way around). http://forums.bistudio.com/showthread.php?t=84227 Release notes: http://forums.bistudio.com/showthread.php?p=1330520 "* Fixed DOF always enabled on game start." Yeah now its always disabled instead. I had this bug both in Win7 RC, and now 7 RTM (meaning the bug is there after full reformats).

Loving mousesmoothing at 0. The mouse is just that much more responsive. Thank you so much BIS. No stuttering here, running mouse @ 2000dpi, 1ms response time. As for your question about default value. You have to add this option ingame for the next official patch (its the only way normal people will be able to tweak it correctly). And in my opinion, it should be disabled by default since all other games comes with this setting OFF by default - despite people having issues with it here (would be interessting to know what mouse they use).

Because it was added in a ArmA1 patch, v. 1.08. ArmA 1 was released when GPUs had no more than 512mb memory (more was not common). But with the release of the 8800GTX, 768mb card, it became more common (HD2900XTs with 1GB also showed up). In the patch release notes it says; * New texture detail "Default" that autodetects the amount of VRAM. Recommended Texture Detail setting for users of cards with more than 512 VRAM. So yes, Default is the recommnded option for cards with more than 512MB of VRAM. What i dont understand is why i get a big performance drop using Default instead of VeryHigh.

Default option, for me, lowers performance considerbly when using veryhigh settings. Video Memory at VeryHigh: Video Memory at Default: As you can see, Default option reduce perfromance by quite a bit (i have a 4890 1GB GPU).

Set to "Application Controlled" in CCC, and then use INGAME options (high, veryhigh) to set AA/AF.

Notice that the beta patch does not affect your original games, or shortcuts. So when you install a beta patch, you have access to your regular 1.03patch game, aswell as the latest beta. Just save the Uninstall_ARMA2Patch_1_03_beta file so that you can uninstall the beta when you want to!

http://www.arma2.com/beta-patch.php There you go :p

Great work on these beta patches Maruk and everyone else. Mouse respons is MUCH better. However, the postprocess settings are still bugged (default to low everytime you start the game - there is a thread about it). Also, we still do not have the option to enable/disable Vsync in the game. This is the only game in the world that force Vsync ON without letting users disable it. Performance still needs to be optimized, but i am sure you are already working on that for 1.04.

Tried to format Windows, installing Windows 7 RTM and patch directly to 1.03 - same bug.