Quote:
Originally Posted by
grazr
In fact Hammer has an in built safety which prematurely ends the compile should a leak prevent a successful compile.
I'm not really sure what you mean by that... I've never seen any such thing, and have on numerous occasions purposely compiled with a leak (completely unsealed/unskyboxed) early on to check scaling/etc and it goes through and loads in the engine just fine. Leaks are never fatal to a compile.
As for the whole discussion at hand... once past VBSP there is very little need to actually see what the compilers are writing to the console, you'll probably have a decent idea of how long it will take after one compile... and you know the old saying "a watched pot never boils"

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.
If there
is a necessity to see what they are saying before it finishes, one can go open up the log file and check it, as that is written to simultaneously with the console window.