SEG Limit or something?

[Phobus]

To summarise the problem:

I've got my map, which has a room built as shown below in the screenshot:



And for some reason whenever I look up to the sky from various angles (close enough to actually be able to see it) I get kicked from ZDoom instantly, with no crashlog and no real indication of whats going on. Below is a screen of the room as it is currently (running forwards raises a large staircase from the lava).



My question is: Is there some sort of SEG Limit or whatever that I'm bumping into in this room (with the silly detailed arrows) or is there just a bug of some sort that I should report?

EDIT: Removing the four arrows on the x and y planes solved the problem... so I assume I'm right with the SEGS thing. Anybody able to verify for sure?

[FuzzballFox]

Is it possible to post the map here to see if anyone else gets the same problem?
EDIT: Just noticed the edit- XD Nvm

[Graf Zahl]

Whether there's a SEG limit depends on the node format. Regular nodes have a limit of 65535 but ZDBSP will refuse to write them if it overflows. Compressed nodes have no limit. In fact, some of KDiZD's maps were far above 100000 segs.

[Remmirath]

Try to build the nodes by compressing them, like Graf suggested, but first place those old details you removed.

From the command line, write "zdbsp -z quicky2.wad" and see if it crashes.
-z means that zdbsp will compress the nodes, so there will be no SEGS limitations.

[Phobus]

It seems to me that it might be more along the lines of a visible SEGS issue then, as ZDBSP isn't having problems writing the nodes. Is there such a thing as a visible SEGS limit in ZDoom? I know there is in the original exe files, but those were rarely seen due to visplane overflows getting in the way first.

My current work around has been to remove four of the arrows and put in some pillars to break up the amount of visible mapping, as I'm still expanding and filling in the area with architecture and decoration.

[Graf Zahl]

Have you tried GZDoom? It uses completely different rendering code that never triggers any potential limits that somehow might lurk deep in the bowels of the software renderer.

Although I have to say that I don't know of any such limits. Can you let me have a look at the map (with a description how to trigger the crash.)?
Being able to run it from a debugger might yield more useful results.

[Phobus]

Err... problem there. I've changed the map around now and probably saved enough so that there's no backups which feature the architecture which presumably caused the crash...

With the changed layout I'm yet to have any crashes with the software renderer. Sorry - I probably should have thought to preserve the problem so it can be looked into properly rather than just making a work-around.

If it happens again with the new layout I'll send it to you via PM straight away.