User Tools

Site Tools


arma:startup_parameters

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
arma:startup_parameters [2008-05-06 00:13]
snakeman created startup_parameters initial page
arma:startup_parameters [2011-11-06 16:50] (current)
Line 5: Line 5:
 Example: Example:
  
-"​C:​\...\some path\ArmedAssault.exe"​ -nosplash -mod=@vietnam+"​C:​\...\some_path\ArmedAssault.exe"​ -nosplash -mod=vietnam 
  
 ====== Display Options ====== ====== Display Options ======
Line 15: Line 16:
 | -nosplash | Disables intro and splash screens | | -nosplash | Disables intro and splash screens |
 | -benchmark | Intended for automated benchmarking,​ but was never finished and is not working. | | -benchmark | Intended for automated benchmarking,​ but was never finished and is not working. |
 +| /secuexp | Starts Securom Support (for Troubleshooting) |
 +
  
 ====== Misc ====== ====== Misc ======
Line 34: Line 37:
 | -vm108 | Mimic the 1.08 version virtual address space handling (Uses more virtual space, but can be handy if you know 1.08 was stable for you, and 1.09 for some reason is not) | | -vm108 | Mimic the 1.08 version virtual address space handling (Uses more virtual space, but can be handy if you know 1.08 was stable for you, and 1.09 for some reason is not) |
 | -noPause | Allow the game running even when its window does not have a focus. | | -noPause | Allow the game running even when its window does not have a focus. |
 +
  
 ====== Modifications ====== ====== Modifications ======
  
 ^ Parameter ^ Function ^ ^ Parameter ^ Function ^
-| -mod= | Allows you to subdivide your addons into different folders, folder names separated by semi-colons. See [[arma:modfolders|modfolders]] for more information. Under Linux you need to separate multiple folders like this: -mod=mod1\;​mod2\;​mod3 | +| -mod= | Allows you to subdivide your addons into different folders, folder names separated by semi-colons. See [[arma:moddirs|moddirs]] for more information. Under Linux you need to separate multiple folders like this: -mod=mod1\;​mod2\;​mod3 | 
-| -cfg= | Selects a config file like your Server Basic Config file. Prcessed ​at startup. |+| -cfg= | Selects a config file like your Server Basic Config file. Processed ​at startup. |
 | -config= | Selects a config file like your Server Config File. Processed after startup. Config file for server specific stuff like admin password and mission selection. | | -config= | Selects a config file like your Server Config File. Processed after startup. Config file for server specific stuff like admin password and mission selection. |
 | -profiles= | Alternative placement for per-user content. User/ dir! | | -profiles= | Alternative placement for per-user content. User/ dir! |
 +| -BEpath= | Set [[http://​www.battleye.com/​support.html|Battleeye]] path Default is C:​\Documents and Settings\[User Name]\Local Settings\Application Data\ArmA\BattlEye |
 +
 +
 +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:
 +<​code>​
 +-profiles=d:​\arma
 +</​code>​
 +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.
  
 ====== Network Options ====== ====== Network Options ======
Line 94: Line 106:
  
 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. 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.
 +
 +
 +====== ArmA 2 Startup Parameters Config File ======
 +
 +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:
 +<code cpp>
 +class Arg
 +{
 +        startupParameter="​-startupParameter"​
 +        startupParameter2="​-startupParameter2=value1;​value2"​
 +};
 +</​code>​
 +
 +Example:
 +<code cpp>
 +class Arg
 +{
 +        nosplash="​-nosplash";​
 +        skipIntro="​-skipIntro";​
 +        world="​-world=none";​
 +        mod="​-mod=Expansion;​Expansion\beta;​Expansion\beta\Expansion;​x\vte";​
 +};
 +</​code>​
 +
 +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:
 +<​code>​
 +-startupParameter
 +-startupParameter2=value1;​value2
 +MissionFileToOpenInTheEditor
 +</​code>​
 +
 +Example:
 +<​code>​
 +-nosplash
 +-skipIntro
 +-world=none
 +-mod=Expansion;​Expansion\beta;​Expansion\beta\Expansion;​x\vte
 +"​c:​\arma2\Users\USERNAME\missions\MissionName.Desert_E\mission.sqm"​
 +</​code>​
arma/startup_parameters.1210032797.txt.gz · Last modified: 2008-05-06 00:13 (external edit)