Apparently this problem is tied to the map in question, but not unique to it (as it happened with map01 as well). In this case, the log is several thousand lines long (it went to 220 000 once, when I kept the game open for less than half a minute), and contains the same thing as above, then a wall of "TryRunTics: lowtic < gametic" occasionally broken by "Tried to transmit to another node".Īn autosave from a different map loads without trouble. I can Alt-F4 the game, and if I take a look in the task manager, GZDoom task is there and even marked as "working". Nothing happens, and I can press Esc to hear "menu opening" sound (Doom cursor appears as well), but there's no way to do anything. When I load an autosave, the menu, music and video mode stay, same as above, but the game doesn't close.
In this case, the logfile contains the usual startup text, then this: When I open the task manager (the only way out of this, really), there is no task for GZDoom, but gzdoom.exe is in the process list (I have to kill it to continue working). Mouse cursor changes to system default, and the focus switches to whatever other window was open - I accidentally closed my browser when I tried to Alt-F4.
When I load a regular save (made 18 minutes into the map), the loading menu stays on-screen, the music for the map starts playing, and the video mode/resolution stays, but other than that, the game basically closes after a moment. Also, it happened both with a regular save and with an autosave from the same map, but in different ways.
It doesn't matter if I load from Load menu or if the game auto-reloads after my death, the result is the same. It happened on different maps (I first saw this on map01, and now on map03). Today, after starting a new megawad, I have encountered a problem that crashes the game when I try to load a save.
0 kommentar(er)
