Latest update becomes unstable after module reload
Melkior
Member Posts: 204
What it says in the title. I play on a persistent world which does a module reload every 8 hours or so, and it often happens when players are online (10 mins warning plus more warnings closer to time).
Before the latest update, a module reload while being logged in was no problem. Players were automatically re-logged into the module and everything just worked.
Now, if you're logged in when the module reloads, immediately after the reload your character starts behaving like it was filmed using an 1800's film camera at 10fps. Very jerky and difficult to watch.
I haven't personally tried to persist in playing like that, but others have reported a complete game crash if they attempted to continue to play.
The only solution is to exit not just the server but the whole game, then reload the game and log back in to the server, so it's very obviously a problem with the game and not with the server.
My first guess is that the programmers neglected to anticipate a memory leak which happens whenever a module is reloaded. Maybe they're failing to unload the previous module data and are loading a new copy into free memory, leaving very little memory allocated for graphics processing? (A memory leak)
A fix for this problem would be appreciated.
Before the latest update, a module reload while being logged in was no problem. Players were automatically re-logged into the module and everything just worked.
Now, if you're logged in when the module reloads, immediately after the reload your character starts behaving like it was filmed using an 1800's film camera at 10fps. Very jerky and difficult to watch.
I haven't personally tried to persist in playing like that, but others have reported a complete game crash if they attempted to continue to play.
The only solution is to exit not just the server but the whole game, then reload the game and log back in to the server, so it's very obviously a problem with the game and not with the server.
My first guess is that the programmers neglected to anticipate a memory leak which happens whenever a module is reloaded. Maybe they're failing to unload the previous module data and are loading a new copy into free memory, leaving very little memory allocated for graphics processing? (A memory leak)
A fix for this problem would be appreciated.
0
Comments
https://nwn.beamdog.net/discord