PurpleBlurpL Posted June 11, 2018 Share Posted June 11, 2018 It looks like the dedicated server (https://steamdb.info/app/380870/)is set to the wrong branch (IWBUMS). I'm on Ubuntu Server 16.04 and there is a client server mismatch when a steam version client attempts to connect to this dedicated server. I am using steamcmd to keep the server up to date. Steam version client is running 39.66.3. (ran integrity check already) Steam version server is running 37.67.3 (IWBUMS??). I am on the normal branch and am using `./steamcmd.sh +login anonymous +app_update 380870 validate +quit` as my update command. Thanks in advance. Link to comment Share on other sites More sharing options...
milspec Posted June 12, 2018 Share Posted June 12, 2018 Same here. The server I just loaded from my serverhost is: versionNumber=39.67.2 It doesn't show on the server browser because "show different versions" is off by default. Link to comment Share on other sites More sharing options...
lemmy101 Posted June 12, 2018 Share Posted June 12, 2018 This is an odd one we're all puzzled by. Main branch on linux ded server hasn't changed since the public vehicle build 15 days ago according to steam backend. but we'd have had more than two reports if this had been an issue since then and its hard to see how it could habe changed to a newer build. We're waiting on testing but are looking into it. PurpleBlurpL 1 Link to comment Share on other sites More sharing options...
EnigmaGrey Posted June 12, 2018 Share Posted June 12, 2018 Can't get back to the public branch without including an empty "-beta " tag, as SteamCMD does catch info about the applications you install (the SteamApps folder in SteamCMD's install dir). This is why, sometimes, validate doesn't actually do anything (it just compares the timestamp/hash in the manifest file and calls it a day). Thus, the command is app_update 380870 -beta validate Just tested on Ubuntu. Got build 39.66.3 correctly. Link to comment Share on other sites More sharing options...
milspec Posted June 13, 2018 Share Posted June 13, 2018 Thanks for looking into it. I use gameservers. A fresh install was the newer 39.67.2 build. I was able to use the host's provided update mechanism to get back to 39.66.3. I agree there are only a few reports. Batsphinx 1 Link to comment Share on other sites More sharing options...
PurpleBlurpL Posted June 14, 2018 Author Share Posted June 14, 2018 @EnigmaGrey Just tried that fix, seemed to work! Thanks! Link to comment Share on other sites More sharing options...
Faalagorn Posted June 17, 2018 Share Posted June 17, 2018 If it's a Steam bug shouldn't the bug be closed here and optionally moved to Steam for Linux GitHub issue tracker (not sure if there's other place to report that, even if the issue may not be linux-only)? Adittionaly, I guess someone from dev team can make a pinned thread about this workaround somewhere in forums, so people would avoid the issue in future :). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now