[TIP] Stopping builds on leaks

[xzzy]

Not to mention, previously known length is all you have to go on. Nothing in the during-compile output will give an accurate estimate of the time remaining.

Sometimes vvis goes nuts and takes 3-4 times longer to complete for no reason that I can discern, and I normally only catch it when I see the "1..2..3.." stuff going much slower than normal.

Yeah, there's no timestamp going, but the output can be useful.

 

[Bloodhound]

Got another pro argument for VBCT.
If you want to make a test compile, with VVIS, it would take some time.
But if you are using VBCT you can work in hammer at the same time, for example making some detail work.

 

[grazr]

It's called crashing and not telling you.

If there are too many visportals with unnassigned adjacent visleafs because of a hole to the void where it tries to make a whole bunch of visleafs outside, Hammer skips vvis altogether. I'm surprised either of you aren't aware of this.

 

[Dr. Spud]

I've never seen a sentence with the phrase "hardcore pro elite" taken so seriously. But really, default hammer compile is fine I think. Certainly fine enough not to dismiss more expert compile tricks. Speaking of which, does there exist a document that contains all the commands for it?

 

[xzzy]

The Valve wiki lists all the command line arguments for the three compilation binaries.

VBCT has checkboxes for all of them. :O

 

[Dr. Spud]

Oh I see, the commands are listed in the the vbsp, vvis, vrad sections seperately. Never looked past the general Expert Compile page.

https://developer.valvesoftware.com/wiki/VBSP