On using steamcmd to install a new Arma3 instance on a server that has a 'normal' Steam install already the arma3server.exe will look in the old 'normal' Steam folder for some of its files and will fail to start until the 'normal' Steam install is also updated. {F19935}
Description
Description
Details
Details
- Legacy ID
- 2478852762
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Have Not Tried
- Category
- Dedicated Server
Steps To Reproduce
Some people had this issue when updating to 0.60 and using steamcmd for the first time. See http://forums.bistudio.com/showthread.php?156185-Has-0-60-patch-broken-dedicated-server
Additional Information
Here is a cut down rpt file showing the errors generated on game startup.
Event Timeline
Comment Actions
C:\Program Files (x86)\TCAdmin Control Panel\Monitor\steamcmd\steamcmd.exe +login %STEAMLOGIN% +force_install_dir G:\TCAdmin_Game_Installs\82ndab\GameServers\Arma3 +"app_update 107410 -beta" validate +quit
Comment Actions
Original folder structure was:
G:\TCAdmin_Game_Installs\82ndab\GameServers
Arma3 SteamApps common Arma3 - arma3.exe (and all relevent files/folders) here
New structure with steamcmd install
G:\TCAdmin_Game_Installs\82ndab\GameServers
Arma3 - arma3server.exe (and all relevent files/folders) here SteamApps common Arma3 - needed to update install here for it to work