Closed wolfmanfp closed 2 months ago
Also tried debugging with VS2022, this is what I got:
The thread 22452 has exited with code 0 (0x0).
The thread 20488 has exited with code 0 (0x0).
Script error, "gzdoom.pk3:zscript/engine/ui/statusbar/statusbarcore.zs" line 69:
Unknown identifier 'DI_ITEM_CENTER'
Exception thrown at 0x00007FFAD43D53AC in gzdoom.exe: Microsoft C++ exception: CRecoverableError at memory location 0x000000FBC90FD970.
Script error, "gzdoom.pk3:zscript/engine/ui/statusbar/statusbarcore.zs" line 70:
Unknown identifier 'DI_ITEM_CENTER'
Exception thrown at 0x00007FFAD43D53AC in gzdoom.exe: Microsoft C++ exception: CRecoverableError at memory location 0x000000FBC90FD970.
Critical error detected c0000374
A breakpoint instruction (__debugbreak() statement or a similar call) was executed in gzdoom.exe.
Woops, I can see that this is a duplicate of #2531, and that it will be fixed in the next devbuild, so I'm closing this. Sorry.
GZDoom version
4.12.0, 4.12.1, 4.13pre-19-gd9f03863b
Which game are you running with GZDoom?
Doom 2
What Operating System are you using?
Windows 11
Please describe your specific OS version
Windows 11 Pro 22H2
Relevant hardware info
Intel i5-4460, NVIDIA GeForce GTX 1060 6GB
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
Starting Doom II with Eviternity II RC5 and a new config file crashes GZDoom after the loading screen. Very rarely it gets through the loading screen and I can start a new game, but it's very random. Other mapsets and mods work fine. The latest nightly GZDoom and VKDoom builds also have the same problem. 4.11.3 worked fine.
CrashReport.zip I attached the crash report from the latest GZDoom devbuild, 4.12.1 wouldn't let me save a crash report for some reason.
Steps to reproduce the behaviour.
Explain how to reproduce
Your configuration
Provide a Log
https://gist.github.com/wolfmanfp/5550bca57afcf2c93f371600ef944328#file-gzdoom-log