Do we already know command line parameters?

[tortuosit 486]

Subject says it all. In A2, we were able to skip into, not load video and had some CPU control there. Haven't tested old command line parameters yet, am not at home. Guys?

[Redphoenix 1540]

-skipIntro and -noSplash as well es the -world=empty do work.

But I would like to now if ArmA3 already supports full usage of Quadcores (or more) or if it just is a pipe dream.

[Dwarden 1125]

majority unchanged http://community.bistudio.com/wiki/Arma2:_Startup_Parameters so you can use them

[tortuosit 486]

Thank you! As for future modding, I feel it will work the same way as before ("-mod=@xyz;...") :) Arma III directory structure is similar, that's why... Will it?

[nineball 10]

majority unchanged http://community.bistudio.com/wiki/Arma2:_Startup_Parameters so you can use them

Does the 2047 limit still apply on "-maxVRAM="?

[Dwarden 1125]

the command not changed so max is still 2047 yet VRAM parameter and video memory 'option' should be irrelevant as the game is DX11 and that uses VRAM differently ...

[tonygrunt 10]

Most of the old parameters are here. In the arma3.exe there are appear to be some new ones but I have no idea what they do or if they even work.

enableSimulWeather=
d3dDynCB=
nobenchmark
benchmark
d3dNoHashStates
d3dCreateNoThreadOpt
d3dCreateSingleThreaded
d3dNoMultiCB
d3dNoLock
noland
epeAllowHWScene
epeSimulationPrecision=
noAsserts
userGroup=
jExportInterface
jPerfTest
jSuspend
jDebugPort=
disableEpeStreaming

Any comment from a Dev if these are parameters and what they do would be appreciated. :)

[chortles 263]

Thank you! As for future modding, I feel it will work the same way as before ("-mod=@xyz;...") :) Arma III directory structure is similar, that's why... Will it?

Modding currently uses the same methods and format as with Arma 2, the only difference being that if you were enabling mods through a modline shortcut, you'd now put that into the Steam Launch Options for the game just like with the other parameters, while putting mods into one's Arma 3 folder within My Documents and then enabling/disabling from the Expansions menu also still works. :) Just the thing for people who stick their Arma 3 install on a SSD but the My Documents folder and thus their Arma 3 profile on a HDD, I say...

Also, note that the directory is going to culminate in "\SteamApps\common\Arma 3" irrespective of where you choose to install, due to Steam's folder structure for game installations, so no more "C:\Games\ArmA2" or something as the install directory.