by Matt » Tue Sep 12, 2017 9:00 am
d0fbdd relwithdebinfo and debug crashlogs attached.
There is also a crash when I start a new game or IDCLEV or map (but not changemap) when I am in a game, or if I type endgame and then quit.
EDIT: I was able to get rid of the crash by deleting a large chunk of my gzdoom.ini.
It does not even crash if I delete that chunk, run GZ+HD, quit, then run it again and quit again, so it's not something that HD is systematically re-introducing but some old kipple left over from something else.
This would explain why:
1. it only happens in HD (presumably the offending lines are old HD cvars)
2. it only happens to me (bunch of stuff that only exists in my particular configuration files)
3. it happens on quit, when GZDoom is writing to the ini
I'll try later to isolate just what part of that ini is causing this.
I don't want to have this closed, though, since surely there must be a more graceful, informative way to detect whatever sort of error is going on here???
d0fbdd relwithdebinfo and debug crashlogs attached.
There is also a crash when I start a new game or IDCLEV or map (but not changemap) when I am in a game, or if I type endgame and then quit.
EDIT: I was able to get rid of the crash by deleting a large chunk of my gzdoom.ini.
It does not even crash if I delete that chunk, run GZ+HD, quit, then run it again and quit again, so it's not something that HD is systematically re-introducing but some old kipple left over from something else.
This would explain why:
1. it only happens in HD (presumably the offending lines are old HD cvars)
2. it only happens to me (bunch of stuff that only exists in my particular configuration files)
3. it happens on quit, when GZDoom is writing to the ini
I'll try later to isolate just [i]what[/i] part of that ini is causing this.
I don't want to have this closed, though, since surely there must be a more graceful, informative way to detect whatever sort of error is going on here???