-TwK-Danny

Default for singleplayer 0% for multiplayer

Thank you BIS, for not ruining the MP community. I was afraid the DLC(s) would sperate it compleatly. Thank you!

All this crap becuse BIS do not add a simple toggle in video options like 99% of all games. Even console ports have options for Vsync. How about they look at valve? They provide Vsync off, Vsync (double buffered) aswell as Vsync (tripplebuffered). Heck they do in in Alien Swarm, a FREE game.

Add a Vsync option in the graphics meny.

This is compleatly wrong. Whoever wrote that doesnt understand how vsync works, nor dicuss any imputlag brought by it. Its stupid that this game doesnt have a simple Vsync option. Even console ports have options for Vsync.

DOF is always disabled on game startup despite what Post Process is set to in options.

Can you please run the benchmark supplied with operation arrowhead, once with default and once with very high and report back?

Sounds like you suffer from frame-skipping. Try the following settings Distance view: 1600 Texture detail: Very High Video memory: Very High AA: Disabled AF: Very High Terrain detail: Normal Object detail: Normal Shadows: Very high Postprocess effects: Normal Resolution: Your monitors native Now go to C:\Users\***name***\Documents\ArmA 2 and open arma.cfg Change the following settings to make them look like this; GPU_MaxFramesAhead=1; GPU_DetectedFramesAhead=1; With your system, these settings should run pretty well. If you want to increase graphics futher, you should try enabling AA (low or medium) and try to increase Distance view. Terrain Detail and Object Detail can cause stuttering when looking around, so keep them at normal. Make sure you are using Catalyst 10.6 aswell. http://game.amd.com/us-en/drivers_catalyst.aspx

Havent notice any issues with flash nor an fps drop in ArmA II with Catalyst 10.6 on my HD4890. But i doubt that will change anything. Perhaps it really is a game bug then, introduced in some of these newer betas..

Yes ofc, but the issue is blurred image using AA, why would he be interessted in using SSAA aswell? Sounds like asking for an avg fps below 5 to me. And SSAA tend to blur the image, and since he did use a higher 3D resolution (and hence enabled SSAA) it might be the cause of his problem.

Ah, so you actually get GPU_DetectedFramesAhead=0; ? Now that is wierd. When i delete my ArmA cfg i get GPU_DetectedFramesAhead=3; What OS, graphics card and graphics driver are you using?

You cannot set it in ATis Control Center, but you can set it using a third party program called ATi Tray Tools (you do NOT need this though since you can already set it the way you did via the .ini). By default the ati (and nvidia driver) set this to 3. With nvidia, you can change this setting in your control panel (its called "max frames to render ahead"). Since ArmA II forces Vsync and tripple buffering on, this setting is depending on what fps you get. If you mostly get fps below your monitors hz (eg below 60fps on a 60hz LCD), then setting is best at "1" when it comes to reducing mouselag. If, however, you have a PC that manage fps constantly higher or equal to monitors hz, eg in ArmA fps constantly 60fps (without ANY drops) on a 60hz LCD and you should set both to "0" for reduced mouselag. What seany meant is that there were two lines you changed, one showing 1000 and the other 3. This means the game uses 3 by default, since that is what your graphics driver is telling the game to use. This is what happens normaly, without you doing anything.

Combining several effects into one setting is never a good idea. Game looks absolutly horrible without DOF on (IMO) and no1 can have that on without also forcing SSAO on.

Have you ran the benchmark comparing Default and VeryHigh? VeryHigh is constantly 3-4fps faster than Default for me.

Hmm, you shouldnt really have such diffrent resolutions for interface and 3D. At least use the same aspect ratio. Interface should be set to what your monitors native is, eg what you use in windows. 3D should then be either the same as interface or something lower but with the same aspect ratio. Only time interface shouldn´t be the same as native is when, for example, wanting to use widescreen resolutions on a 4:3 monitor. In your case Hunter123, Set interface to 1280x1024. Set 3D to 1280X1024 aswell and aspect ratio to auto or 5:4. If you want widescreen, set 3D to 1280x800 and aspect ratio to 16:10. Or even wider, set 3D to 1280x720 and aspect ratio to 16:9. Now try using AA.