|
|
Multiplayer Connection Freeze.savemet (153 bytes) |
|
|
Is this when the exceptions are happening? If so, the host might not be in a fit state to continue. Once an exception has happened, the game is not definitely going to keep running. If it's happening out of the blue, no exceptions, then that's more baffling. It's possible that the underlying steam connection is having some sort of issue, but not if you're able to reconnect players. |
|
|
That save was taken during one such permanent no-actions-allowed pause. As far as I know, there is no visible popup error message associated with the error, and she was not able to reconnect to make it work - when she rejoined, the game simply paused indefinitely again (not shown in save). However, each time after she left, the game was able to continue normally. |
|
|
...So basically, yes, Steam might very well be throwing a fit. |
|
|
If there's no client connected, the host can do whatever. With the client connecting in, it's hard to say why they were in a state where there was an inability to proceed. I don't think this is a steam issue, since the client was able to disconnect and reconnect. I would suggest that if this happens, the host exit to the menu and go back, but that's not ideal of course. |
|
|
We'll try that, thanks! If it pops up again, would it help you find the underlying issue if we made and submitted save(s) with a few instances of freeze -> unable to resume after rejoining -> freeze -> unable to resume after rejoining? It'll probably be most of a week before we can do that, though. |
|
|
Probably the save is unrelated, since there were no errors. Something is a bit stuck on the client, and I don't know quite what. Having the ArcenDebugLog.txt from the client might be helpful, since it might show something directly after they exit (the stats about MP are logged there). That said, there are a few other things. I'm going to make a series of posts here to explain what I'm looking for, since otherwise the images will get scrambled around. |
|
|
First off, right-clicking the clock in the bottom left corner brings up this screen. There's a fair bit of interesting stuff in here, but one of the most interesting is the "Details" statement on the fourth line. That states why the local machine (we're interested mainly in the client here, but the host is also slightly interesting) isn't running the next sim step. |
|
|
Secondly, in the network tab of the settings, and the debug section of the settings, having the client and the host turn on these two options will make some stuff show up in the upper right corner of the main game view. NetworkTab.PNG (123,199 bytes) |
|
|
This is part of what you'll be seeing. If the client looks like they are stuck on a bunch of waiting gamecommands or something else, that would be informative. topright.PNG (134,171 bytes) |
|
|
There is some other logging that could be interesting, mainly if the client turns on the logging for all network messages and then sees what is being sent from the host. This is something to only do after it's already frozen, before disconnecting or doing anything else like that. This is a really heavy amount of logging that will make the game lag like crazy, so avoiding that if at all possible is good. |
- Anonymous
