Closed Binary-2 closed 3 years ago
Here's a pastebin of the server's logs. I've noticed a few issues but the server's been running smoothly and people don't have much issues playing so I haven't payed much attention to them.
Also, I'm not sure if the lines denoting a failure to read are my fault, I ran the docker service as directed and it's made the required volumes. I've not messed with paths at all and when I enabled mods, I just used the Bepinex folder that was generated automatically.
That said, if it's just messed up beyond any debugging possibilities, I could just try redeploying it fresh.
After leaving it to run overnight, it'll constantly be found like this, but I'm not certain what the issue is? Does this just happen after a certain number of loops?
The real question is: does it also happen natively on Windows? If so, hopoo pls fix.
I figured out this state can also be reached by the server trying to load a map without any players.
If a player leaves the game right before or during a map changes and the server is now empty, it'll fail to realize the server is in an empty state and end up like the image posted above.
I'm not sure, but I think @InfernalPlacebo / his group patches the executables for this behaviour?
Possible, I tried adding a GPU to my server hardware and it runs much better now. Risk of Rain 2 itself just wants to use a GPU most of all I guess.
Mild speculation on my end, but even with a docker container with unlimited resources, my server will begin to lag as soon as a moderate number of enemies begin to fill the map.
Network ping does not seem to be a factor, and here are some resource stats from portainer and htop:
It's entirely possible I'm running ancient hardware and I've ordered more modern processors even, but I'm not sure where to begin helping debugging this issue