What is causing GZDoom to crash? (UDMF map in progress)

[Koko Ricky]

I haven't had any issues with this UDMF map until recently and unfortunately, after much experimenting, I simply cannot figure out what went wrong. The player start is located in the only room causing this issue. There are portals and 3D floors involved and it's possible one of them is causing a problem somewhere. This map requires OTEX. Download the file here: 

 

https://drive.google.com/file/d/1IMUcypDedO2VJgUKs4xAP1czP5i4pDsz/view?usp=sharing

Edited January 20, 2021 by GoatLord

[Kappes Buur]

 

Works for me™ 

I played the map several times.

The only thing I found in the starting room were 2 missing textures.

Edited January 20, 2021 by Kappes Buur

[Koko Ricky]

That is very weird, because GZDoom crashes over and over! Is it possible I just need to update to the latest build? Upgrading to the latest build did not alleviate the issue. It's also not clear what's causing the issue.

Edited January 20, 2021 by GoatLord

[Koko Ricky]

42 minutes ago, Kappes Buur said:

 

Works for me™ 

I played the map several times.

The only thing I found in the starting room were 2 missing textures.

Where are these missing textures? In GZDoom Builder and in gameplay all textures appear.

 

Here is a gameplay vid of me causing the error:

 

 

Edited January 20, 2021 by GoatLord

[Kappes Buur]

Ah, yes, hmmm .....

I forgot to mention that the first thing I did was to space apart the sections and Snap Selection to Grid in each case.

 

 

It must have been during that process that I lost those two textures. Playing that arrangement caused no problems.

 

And now for the weird part.

I just played your original map and, indeed, GZDoom 4-6-32 freezes as soon the two green panels come into view. That was with fullscreen on. Playing in a reduced Windows window, that freeze did not happen.

 

I have no idea what causes the freeze. Maybe a nodebuilder thing which was corrected by moving the sections apart?

 

As an aside, wonderful use of 3D sectors.

 

 

Edited January 20, 2021 by Kappes Buur

[Mr.Rocket]

I managed to get it to stop freezing after moving the area you spawn in to a different area on the grid.

I moved the initial area from the north west to the sort of south east area of the grid.

So you might try that.

I'm not sure either what might cause that though, really strange, maybe BSP didn't like it? as I doubt that it was VP.

I haven't tried moving it back where it was yet, it might be ok now to move back after it was compiled once.

Let me know and I'll send it over as-is.

Also you should probably let Graf know about this as this sort of crash(freeze) doesn't seem very common.

 

Anyway, pretty cool map so far though man!

Edited January 21, 2021 by Mr.Rocket

[Koko Ricky]

Thanks so much for the feedback. Moving that troublesome area to a different part of the map definitely fixed it. Should I send @Graf Zahl the version of the map that crashes? What's the best way for him to see this so it can be addressed?

 

[boris]

55 minutes ago, GoatLord said:

Thanks so much for the feedback. Moving that troublesome area to a different part of the map definitely fixed it. Should I send @Graf Zahl the version of the map that crashes? What's the best way for him to see this so it can be addressed?

 

 

Posting it in https://forum.zdoom.org/viewforum.php?f=2 is probably the best idea.

[Bridgeburner56]

Once maps reach a certain size, building the nodes in UDB will cause GZDoom to crash on loading. I've had it happen on several maps, as have other mappers I know. For me it's normally around the 80k line mark but one person had it start being an issue around the 40k line mark so it varies from map to map. The solution is to not build the nodes when saving/testing in UDB and let GZDoom build the nodes from scratch. This does not cause any issues as far as I am aware. I had to do this for Bastion of Chaos and the Age of Hell version is up to 140k lines and no crashes with GZDoom.

This might not be your issue but it's worth trying because that's pretty much the only thing that I've had cause GZDoom to crash and not spit an error message in the console or a crash log. It just hangs before the map loads (music starts though) and eventually crashes to desktop. Press F6 and go to the nodebuilder menu. You can then set the nodebuilder for testing/saving to "none"

[Major Arlene]

17 hours ago, Bridgeburner56 said:

Once maps reach a certain size, building the nodes in UDB will cause GZDoom to crash on loading. I've had it happen on several maps, as have other mappers I know. For me it's normally around the 80k line mark but one person had it start being an issue around the 40k line mark so it varies from map to map. The solution is to not build the nodes when saving/testing in UDB and let GZDoom build the nodes from scratch. This does not cause any issues as far as I am aware. I had to do this for Bastion of Chaos and the Age of Hell version is up to 140k lines and no crashes with GZDoom.

This might not be your issue but it's worth trying because that's pretty much the only thing that I've had cause GZDoom to crash and not spit an error message in the console or a crash log. It just hangs before the map loads (music starts though) and eventually crashes to desktop. Press F6 and go to the nodebuilder menu. You can then set the nodebuilder for testing/saving to "none"

I've even had this happen on a 10-12k line map, it can also depend on line density and a wide variety of other geometrical factors. But yes, this can happen, and turning off nodebuilder can help. A word of caution: I've turned off nodebuilding in UDB for one map, and when coming back to a map that had a ZNODES lump when I was using a nodebuilder, I've had it hard-crash gzdoom because of a difference between the vertices the map actually has and the vertices the ZNODES lump was reading. turning nodebuilder back on and re-building nodes will fix this issue.