ZDoom

I didn't see any information that looked wrong.

So this seem to clear the mystery of "why doesn't ZDBSP generate the same nodes as ZDoom itself".

Randy, can you check I'm not saying anything dumb [url=http://zdoom.org/w/index.php?title=Node&curid=1079&diff=35135&oldid=29592]here[/url]?

[quote="cocka"]OK, but this is the circumvention of the problem and the fact remains that it is a bug.[/quote]
Indeed. I wasn't trying to say that it wasn't a bug or that you should try to work around the problem. I was providing evidence suggesting that your suspicion was correct. (Albeit that when I did so I it seems as if I was typing using rubber fingers or something.)

Anyway, it looks like its fixed now. Thanks Randy & Graf.

Now it's fixed for real. ;) ([rev]3982[/rev])

Fixed in [rev]3980[/rev] (ZDoom) and [rev]3981[/rev] (ZDSP). I will try to get an updated version of ZDBSP up within 24 hours after I'm satisfied that the introduction of a new node format didn't break the writing of any of the existing formats.

That could indeed explain why I was never able to get satisfactory results out of ZDBSP for ZDCMP2. If that's fixable, that'd make me a happy Xaser. :D

I have reconfirmed that, aside from off-by-one-bit differences when loading fractional vertex data, the internal node builder and ZDBSP are, indeed, generating absolutely identical nodes. There's just one problem: None of the node formats support node splitters with fractional coordinates, so ZDBSP cannot save its nodes exactly as generated. Oops.

I'm completely dumbfounded as to why zdoom's internal nodebuilder produces different (and better) results than ZDBSP. Aren't they (almost) exactly the same thing?

[quote]to move the few vertices that were using fractional coordinates to vertices to whole number coordinates[/quote]

OK, but this is the circumvention of the problem and the fact remains that it is a bug.

[quote="cocka"]I think it has something to do with the vertices using fractional numbers for their coordinates.[/quote]
I think you're right. I just used DB2 to move the few vertices that were using fractional coordinates to vertices to whole number coordinates then saved the map. On testing it, the problem had gone.

[quote]but gennodes 1 removes the glitch.[/quote]

If you "convert" it to hexen format, the glitch will be gone too.

[quote]As to why this is happening, I have no idea.[/quote]

Obviously, this is a bug. I wouldn't have written it here, if there were no problem at all.

I think it has something to do with the vertices using fractional numbers for their coordinates.

Just confirming that when I build the nodes manually from the command prompt using my usual settings ( -x -z -w -b -r ) or build them via DB2, the glitch persists but gennodes 1 removes the glitch. As to why this is happening, I have no idea.

OK, but the question is: why does zdbsp not work properly? If there is a routine in zdoom for building the nodes perfectly, why does zdbsp not use that routine? And why does it produce glitches by building nodes?

No. What I was saying is the problem is with the nodes and running it with gennodes enabled is the proof that it is.

There's an alternative: Delete the nodes from the map (use SLADE) and don't build them yourself. ZDoom will do it for you when you start the map. The downside to this, however, is that the map will take longer to load/start the larger it gets.

So are you telling me that every time I load the map I should use a console command and reload the map to correct the glitch? :lol: