None of your suggestions solve the main problem with ARMA games, that is, the old Operation Flashpoint engine is still largely CPU-limited (to the point where I can enable/disable 8xMSAA without seeing any significant difference in performance) whilst only using two cores fairly efficiently. They've promised us big changes when it comes to utilisation of resources by the engine (heck, I even remember someone mentioning a new engine before Alpha was out) and yet it's still the same 12 year old Real Virtuality engine, albeit very impressive on the graphical side, it chokes in more intensive scenarios and offers a very dated AI model.
And before any of you mention "herp derp, it's still in beta", well, I don't remember ARMA games ever making a giant leap from Beta to RC, but I'd like to be positively surprised.


For a test I even capped my FPS at 30 the other day, even at that its pretty playable. I always find a console at 30fps seems smoother then a PC at 30fps. Sure there are reasons why.
Gamepad.

I seem to be getting a solid 30fps+ on VH settings which I'm liking. Dropping to just under 25fps in busy places like some of the Combined Ops mission, so if they optimize it well enough that I can get 30fps anywhere that would do me![]()

I guess thats down to threading, something is holding it back. Or it might be the server, somehow this game relys on the server far more then most games. To test I have to put the CPU clock on max as it doesnt use all the cores, also turn off HT might help if I remember right![]()
Any card will struggle to maintain 60+ fps on this game at that resolution on very high preset. The game is more CPU bound anyway, even high clocked i7's can't do a brilliant job. Some servers are to blame on multiplayer as well. The MBS server I get really good fps on but some other servers run like dog poop.
Anyone getting problems since the beta with Windows running low on memory?
Its getting on my nerves.