Command line parameter -nosplash and -nointro do not work with the Beta.
Description
Details
- Legacy ID
- 3432837555
- Severity
- None
- Resolution
- No Bug
- Reproducibility
- Always
- Category
- Other
Event Timeline
-noSplash works for me too, though with steam, you have to put the start-up parameters within the A3 “set launch options” options in steam, as the desktop icon for A3 starts steam, which then in turn starts A3 using the “set launch options” parameters.
Start steam.
Right click on A3 and select properties.
In the window that opens on the first page (general) there is a “set launch options” button.
Press the “set launch options” button and enter the start-up parameters in the box provided with a space between each as you would a conventional command line parameter, once done, close all the A3 properties pages and start the game.
Works with the Steam method. However, in ARMA 3 Alpha, individual desktop shortcuts could be created, each with their own command line parameters. So, I take it, with the beta, only one command line parameter can be used at a time?
Unable to reproduce, they still work for Windows shortcuts pointing directly at the Arma3.exe.
Correct, but the standard steam A3 desktop command line e.g.
“steam://rungameid/107410”
Wont except -noSplash etc command lines, it’s only when you use a link to the arma3.exe directly that –noSplash etc will work, as you are starting the arma3.exe directly which in turn starts steam, whereas with the default steam desktop icon, you are starting steam which then in turn start the .exe.
The standard steam A3 desktop icon is a web link type shortcut, if you want a conventional .exe link, then you need to go to you A3 folder and copy and paste a link to arma3.exe to you desktop or other preferred place, then you can use command lines as normal.
e.g. ignoring []
["C:\FolderName\Valve\Steam\SteamApps\common\Arma 3\arma3.exe" –noSplash]
With the direct link to the .exe, you can have as many different shortcut links as you want provided they have different names, so you can run different command line parameter for each.
Okay, thanks b101uk! I've got it to work. Turns out I was using semicolons between parameters, which broke the shortcut. Apologies for my carelessness, please close! :-)