DRD Team

I have no idea whats going on with GZdoom today. I updated my video drivers and did some map editing and started to get some wierd crashes. Some of these i've fixed, but still don't know what caused the, If it's my wad, then I will have to change some things.

1) Crashing when I put "-nomonsters" when running the game via the RUN.EXE in windows. It would crash out instantly before the game ever gets to goto the main screen. When I ran the game without "-nomonsters", it worked fine. Turning no monsters on while already in the game then starting a map also works fine.

2 and 3)Both of these happened when I put some 3d floors in one of my maps. #2 crashed out after about 5 minutes in the game while running around the 3d floors. 3 Crashed out within 2 seconds of looking at the 3d floors. No ideaw what the deal is. can the dummy sectors that control the 3d floors to connected to a another dummy sector doing the same thing to a different sector?

Here are the error reports:

http://rapidshare.de/files/18198659/GZd ... t.zip.html

2+3 is the same bug and I can't fix it without the map and some information what to do there.

And please use the latest version when reporting bugs. This is for 1.0.03, not 1.0.04. Unfortunately I don't have a map file for that anymore so even to see where it crashes I have to recompile now...

Update: Bug 2+3 is caused by incorrect data in the nodes. I really need the level to see what is going on here. Without it there is no chance I could fix this problem.

I think I might have found the source of the issue. There was one area wear the sector was unclosed. When trying to no clip into this area via the unclosed line segment seem to have caused the crashes. Could this be such a node problem?

Indeed it could. I just added a check to validate the pointer that caused the crash. I just never assumed such a situation could happen in real maps.

Strange that it didn't crash when i was using 0,96x. Since that's been there for like months and people tested the map without actually seeing any problems.

The crash is in the GL renderer so that is not surprising.

What about the first bug? It doesn't seem to matter if I run GL render or Software rander, it causes instant crashout. It didn't do this before, which i find odd. It happened when I updated my drivers.

The first crash happens when trying to look for a lump in the WAD. Can you verify whether it happens also when you are just loading one WAD instead of 10?

Graf Zahl wrote:The first crash happens when trying to look for a lump in the WAD. Can you verify whether it happens also when you are just loading one WAD instead of 10?

Hm...lemme try that.

OK: From what i've seen, as load all but 1 of any wad, it works fine. O_o removing any wad from the list seem to fix the issue. Maybe he command list is just too long? O_o Althought it worked just fine two days ago.

Just a thought, what happens if you place all 10 wads into a zip then load that?

Enjay wrote:Just a thought, what happens if you place all 10 wads into a zip then load that?

Could I actually load wads from zips? I've never tried it before.

Sure you can. How else would you be able to put levels into zips otherwise? Just zip all your resource WADs together and load it as one file.

Graf Zahl wrote:Sure you can. How else would you be able to put levels into zips otherwise? Just zip all your resource WADs together and load it as one file.

Huh..never new the Zdoom supported zip formats, so i always loaded them like I did back when Doom Legacy was hot stuff....which was a long...long time ago.

Zdoom doesn't (yet?) but GZdoom does.