- User Since
- Jun 28 2013, 12:36 AM (367 w, 2 d)
May 10 2016
I just want to add my support for rolling this into the stable branch ASAP. It's really negatively affecting our Wasteland server, and I don't particularly want to advise everyone to change to the dev build branch.
We tried adding an AI character to each side on our server, to see if that might help prevent the lose condition, but it doesn't. I'm out of ideas to try to get around the bug.
Yep, very frustrating. Please give this some attention, your developer community could do so much with this!
I solved this, and it was when I've been logged out of Steam. This happens if you're updating a standalone server instance with a batch script (as I regularly was). Using the standalone Steam command-line will log you out of your main client's session.
Steam just says 'no connection' at the bottom of the main window, but everything else seemingly works. Solution is to rerun or reconnect your local Steam client.
I'm also having this problem on our dedicated servers, and I can't find anything in the logs which seems to help point at a specific problem.
After being logged in for 30 seconds or so, I am told the my client is losing connection, and then 30 seconds later I get a red chain and no more server messages.