the software renderer traversed the bsp tree and rasterised the convex faces, which were not necessarily triangles. 

True, and the epoly had that optimization we talked about before where it would only render the vertices if a model got too far away.

However, that doesn't change the fact that the source file format has nothing to do with how the software renderer works. QBSP shreds the brushes into a tree ... after that the source format is irrelevant. 

In fact in the actual bsp file the plane struct is a normal vector and distance (and a type field), so the three point version of a plane disappears completely after qbsp. 

 

Of course, you are right. What I wrote is nonsense. I will rephrase this in the TB2 docs. Thank you for pointing it out! 

Keep it up, looking forward to having HL1 support out of the box in TB 2.0, this has some serious potential to ignite the HL1 modding community back up again like it's 1999 ;) 

Haven't compiled the tb develop branch in a while and its failing with thousands of the same wx-3.0 Wdeprecated-declaration warnings where previously there where none. 

Those are just warnings, the error is missing pandoc.

make[3]: pandoc: Command not found 

Appreciate that. I was up very late when I attempted to compile and wasn't thinking clearly. 

Re #1907 by Kin on 2015/11/12 17:08:10:
I've read this post today and just fired up the Doom 3 Editor and looked at a freshly saved map file.
And oh my, this is real. They are really using the numerically unstable way of saving brush plane information using just a normal vector and a distance value.
Why on earth would ANYONE do that? Move the whole level geometry forward and back a bit a few times, and you're _guaranteed_ to have everything that's not perfectly straight entirely screwed up! That's lunatic!
O_O
X_X 

I think Sikkpin or someone modded the editor to use the quake-style plane format and the problem of course just went away - you could try to dig up some info about that. 

I lost a couple of maps to that feature before I realized that you're really meant to so complex get with models. 

Would this be something that could be supported in the future by TB?

https://www.youtube.com/watch?v=rJzguNJsivM 

but I have no interest in developing plugins for Unreal. If anyone wants to do it, I'll support it, but I won't do it myself. 

I am having trouble loading FGDs for Hipnotic and Rogue into TB2. Has anyone else tried these in this build? Maybe I am doing something wonky. Trying the FGD versions from Quaddicted archives. wanted to ask before submitting to Github.

Error and then crash:

Unknown entity definition class @Main (line 8, column 1)

TrenchBroom-Win32-2.0.0-36e49c4-Release 

Cannot load this in TB1 either same error although it doesn't crash. 

 

Working fgd in a text editor 

Looking at recent changes and the 2.0 issue list it seems like an official 2.0 release is close? Would be awesome! Is Q3 (Warsow, Xonotic etc.) editing in by now?

Thanks for creating this cool tool! 

I just need to write the docs.

Sorry, no Q3 support, but that's the first feature I'm going to work on for 2.1. 

so I can make pipes super easily -

https://www.youtube.com/watch?v=nKH2FiUmY5M 

Fun fact ... I wrote that tool. :P 

you know what you need to do then, make it for quake! ;) 

And maybe you can explain to me what's happening in that video, I didn't understand it.