1. Right click on Arma2 shortcut
3. In target window after the closing quote mark add switch(es) like this:
"C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -nosplash -world=empty -maxmem=2047
-winxp, use it in Vista/W7 to enable multi-GPU support
-nosplash, skip those splash screens
-world=empty, doesn't load as much stuff for menu, starts faster
-maxmem=2047, allows game engine to use more RAM (2047 is hardcoded maximum atm, anything higher falls back to 2047). Make sure you have at least 3-4Gb for this to work.
-window, windowed mode
-noCB, turns off multicore drawing, slow down rendering but may resolve visual glitches
-cpuCount=X, change X to a number equal or less than numbers of available cores. This will override our autodetection.
Changing affinity on the fly is definitely not good, because worker threads are spawned on the game initialization,
and by lowering affinity later you cause threads competing for cores.
The best way to simulate dual core on quad core is to use -cpuCount=2 when you run the game
and then change the affinity to 2 cores to make sure additional cores can never be used when some overshedulling happens.
It might be also possible to set the affinity in the OS before you launch the process, that would work as well.
-mod=XYZ where XYZ is modfolder in "C:\Program Files\Bohemia Interactive\ArmA 2\"
-profiles=profiles - will store profile info and missions in main C:\Program Files\Bohemia Interactive\Arma 2\profiles folder
Keep adding new things you discover...
Edited by Skeptic, 04 June 2009 - 14:39.
incorrect info about maxmem maximum