ArmA 1 Forum, ArmA 1 Home, ArmA 1 Config, ArmA 1 Tools, ArmA 1 File Formats, ArmA 1 Missions, ArmA 1 3D Modeling, ArmA 1 Terrain, ArmA 1 Texturing, ArmA 1 Scripting

ArmA 1 aka Armed Assault (ArmA)

These parameters can be configured by creating a new shortcut on your desktop or creating a startup batch file and then adding the appropriate option.

Example:

“C:\…\some_path\ArmedAssault.exe” -nosplash -mod=vietnam

One of the most powerful feature is the -mod= parameter, where you place all your addon directories. Another very important feature for us old schoolers is to setup where ArmA places the user made content directory, ie User/ dir. Use -profiles= parameter to set this dir up, for example:

-profiles=d:\arma

Would create the user dir into ArmA root, which would be D:\arma\Users\ directory. Now all your config files and missions are placed under this dir.

config

The option -config allows you to specify a specific server.cfg file.

profiles

-profiles is a startup option allowing you to choose an alternate location for the user profile files, such as downloaded missions and .cfg files.

The windows user account would need permissions to write to the folder of choice.

An example might be like this:

"C:\ArmA\ArmA.exe" -profiles=C:\ArmA

Or

"C:\ArmA\ArmA.exe" -profiles=profiles

Would store all your profiles into your ROOT ArmA folder under the folder name “Profiles”

ranking

-ranking is a startup option allowing you to output ranking info or othewise know as player stats.

The windows user account would need permissions to write to the folder of choice.

An example might be like this:

"C:\ArmA\ArmA.exe" -ranking=C:\ArmA\ranking.log

nosplash

-nosplash is a startup option that allows you to bypass the splash screens on startup of Operation Flashpoint and Armed Assault.

Note: Real speed-up gained with this is likely to be negligible with Armed Assault, as the loading screens are handled in parallel with the game data being loaded, and the loading itself takes quite long thanks to the amount of data needed.

These settings only apply for ArmA 2 (does not work in Armed Assault).

The config file can be used to put startup parameters in, instead of specifying them at a shortcut / command line.

NOTE: low level parameters are NOT supported. .par file does not (and will not) support some low level parameters, like: -cpuCount, -malloc, -exthreads and -maxMem. The reason is those need to be initialized before any file operations are done.

Pre ArmA 2 build v1.59.86060

Location: Inside game directory.

Naming depending on game: ArmA2.par or ArmA2OA.par.

Format:

class Arg
{
        startupParameter="-startupParameter"
        startupParameter2="-startupParameter2=value1;value2"
};

Example:

class Arg
{
        nosplash="-nosplash";
        skipIntro="-skipIntro";
        world="-world=none";
        mod="-mod=Expansion;Expansion\beta;Expansion\beta\Expansion;x\vte";
};

Post ArmA 2 build v1.59.86060

Location can be defined with -par=parameterFileName startup parameter. If file extension is .par the formatting described previously is required. With any other extension (like .txt) a plain text is assumed, with one command line option per line. In both cases the file is preprocessed before parsing, allowing C++ style comments and #define-s to be used.

Format:

-startupParameter
-startupParameter2=value1;value2
MissionFileToOpenInTheEditor

Example:

-nosplash
-skipIntro
-world=none
-mod=Expansion;Expansion\beta;Expansion\beta\Expansion;x\vte
"c:\arma2\Users\USERNAME\missions\MissionName.Desert_E\mission.sqm"