Since I can't seem to reproduce this bug, I'm go to try a different approach to find it.
I've attached a version of 5.1.1.550 with some extra error logging enabled, which might catch some extra details. It's otherwise identical to the regular release. (although it has a different name to make it easier to use)
When DROD crashs, it should hopefully add more details in the drod.err file. It might even be useful information.
words for other developers:
Click here to view the secret text
×
So DROD does have exception handling, it's just that if you build with the _DEBUG flag on to get assert reporting, the exception reporting is disabled. If you change what the #ifndef preprocessors are looking for on lines 374 and 541 in Main.cpp to something else, you too can put the entire game in a try block. It may be worth a try, ha ha.
____________________________
[Insert witty comment here]
Qzvlkx?
[Last edited by hyperme at 04-25-2024 10:05 AM]