To have a stable system and good ingame FPS are the basic requirement to be able to play properly.
Make sure to have your system up-to-date and prime stable first.
WinXP or Win7 are recommended. With the 64 bit OS version the game makes use of 3+ GB if available.
Update your bios, operating system, motherboard with the latest drivers available. Recent GPU drivers are recommended - yet not always the latest are the best. Consult the BIF to find out which ones are to be used momentarily.
Use software to stress test your system for stability and not to overheat. Recommend ones by BI:
In addition to being very CPU intensive the game also is loading data from the HDD a lot. You may want to consider buying a HDD with low access time; especially a SSD is a good idea these days. A Intel or another high quality drive is very much recommended. It will speed up the game loading times significantly and texture loading/switching is improved as well.
The standard way of doing is to create a link to the arma2.exe.
You are recommended to you use an application like the ArmA II Launcher app to simplify the management of various launch configurations.
For beta patch and especially modfolders use you will be more than happy with the tool.
Note that there is the target line and the start in line. The standard non beta example:
Target: C:\ArmA\arma2.exe -noSplash -world=empty -window -noFilePatching -profiles=C:\ArmA -name=ProfileName
Start in: C:\ArmA\
Beta patches have the exe in a subfolder C:\ArmA\beta\arma2.exe and require the -mod=beta extension.
Beta patches have the exe in a subfolder C:\ArmA\Expansion\beta\arma2oa.exe and require the -mod=Expansion\beta;Expansion\beta\Expansion extension.
More of possible interest:
The full list of startup paramaters is available in the BIKI.
-cpuCount= is option which allows define number of CPUs/cores available.
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 over-scheduling happens. It might be also possible to set the affinity in the OS before you launch the process, that would work as well.
-exThreads= is option to define extra threads.
All file operations go through a dedicated thread. This offloads some processing from the main thread, however it adds some overhead at the same time. The reason why threaded file ops were implemented was to serve as a basement for other threads ops. When multiple threads are running at the same time, OS is scheduling them on different cores. Geometry and Texture loading (both done by the same thread) are scheduled on different cores outside the main rendering loop at the same time with the main rendering loop.
|Number||Geometry loading||Texture loading||File operations|
|Disabled||color corrections only|
|Very Low||Disabled + filmGrain + radial blur + dynamic blur|
|Low||Very low + bloom + rotational blur + other scripted post process effects|
|Normal||Low + DOF + lowest SSAO|
|High||Normal + medium SSAO|
|VeryHigh||Normal + highest SSAO|
-profiles=c:\arma2 is used for all examples.
Default location: c:\arma2\Users\SystemProfile\arma2.cfg
-cfg=arma2.cfg used: c:\arma2\arma2.cfg
Both using -profiles=c:\arma2
Render_H=960; Render_W=1280; winDefH=960; winDefW=1280; winH=960; winW=1280;
-name=MyAcc used: c:\arma2\users\MyAcc\MyAcc.arma2profile
Tweak the sensitivity in the ingame control options to your preference.
Smoothing: Default is 30. Recommended is 0-15.
Too low values can mouse jumping. Can also be set in the ArmA2Profile.
Make sure to disable mouse smooth and acceleration in the windows settings.
Basically recommended to remove all default settings and build them from the ground up yourself.
Either drop and drop the assigned keys away in the controls options ingame or remove all numbers in your arma2profile.
You can try the controls by kju. AWSD centered and designed with much thinking and testing: sample.ArmA2OAProfile
No knowledge available.