MistUnky
MistUnky
I just checked all the levels on the wad and it seems that the level size and the monster amounts have no effect on the level crashing, nor does the...
GDB Output when crashing: Emulating the behavior of the 'Ultimate Doom' executable. HU_Init: Setting up heads up display. ST_Init: Init status bar. [New Thread 0x7fffe0980700 (LWP 13985)] [New Thread 0x7fffbffff700...
@AXDOOMER How do I do that? Github says it won't allow uploading of unrecognized files or something.
Oh. Here it is then. [ultrawad.zip](https://github.com/chocolate-doom/chocolate-doom/files/4705196/ultrawad.zip)
Alright, I rebuilt it with debugging symbols and here is the output: Emulating the behavior of the 'Ultimate Doom' executable. HU_Init: Setting up heads up display. ST_Init: Init status bar....
I tested a few levels with varying complexities, and it seems that high complexity levels have a higher chance of causing this segmentation fault than lower complexity ones. I'm not...
Just tested on DOSBOX, it seems that Ultimate Doom just hangs once the level is started (E4M1), and then sometimes collapses to DOS or continues hanging. I'm not sure if...
I tried running it with complevel 3 but it just segfaulted again. With gdb it gives two (now three) different errors when I run the level(sometimes one or the other):...
does complevel even work on chocolate doom anyways??? I'm pretty sure it's not on this port, though I may be wrong
Yeah, I just grepped the sourcecode of chocolate-doom and complevel does not seem to be a valid argument. It seems to be for prboom source ports.