Multi-core compiling tip
Just giving everyone a heads up. I've been performing compiles recently with my quad-core machine, running Task Manager and selecting 'Set Affinity' for vvis and vrad like so...
Forces the compile processes to use only three cores, allowing me to browse web pages without my mouse completely locking up. Running on a single core temporarily, system performance is improved over the jerky non-mouse controlled wang that it is otherwise. Under absolutely no circumstances should you attempt to do anything remotely CPU intensive, since the other three cores are working flat out. Just stick to posting forum messages 
Comments on this are welcome. I've yet to experience any negative gameplay-related issues with this method.
"Such monstrous sucking-constructions aren't built within one afternoon"
Also: *rant* Valve, make your Compile Tools native 64-bit!!
"Such monstrous sucking-constructions aren't built within one afternoon"
Compiles for me never usually take more than 10 minutes at most. However waiting 10 minutes does get a bit boring... Thanks for the tip.
You're welcome. This is especially useful for me, since my partner and I watch movies on my second monitor. Keeping a core free is enough to maintain a decent playback, then I playtest on my main monitor in windowed mode
"Such monstrous sucking-constructions aren't built within one afternoon"
Hmm, I'd rather finish my compile quickly and get on to testing the map.
The longest compile time for my 15 MB maps is around 40 seconds (full final compile mode), so it's not that big of a deal to wait a few seconds.
Vengeance
Olympic
[SP] Interception
Interception PeTI
Herman
Uprise
Unified
The longest compile time for my 15 MB maps is around 40 seconds (full final compile mode), so it's not that big of a deal to wait a few seconds.
A man of optimisation!
Doing a final lighting compile with the correct settings for models etc. will make a compile take twice as long, seeing as it does another pass of the vrad. Using more cores for the final compile would be a good idea.
Yes, using func_detail appropriately is essential.
Planning ahead also helps in the map layout and VIS rendering.
When I map, I optimize as I go. I do not save it as the last step.
Vengeance
Olympic
[SP] Interception
Interception PeTI
Herman
Uprise
Unified
I'd love for you to take a look at my VMF and offer tips as to where I should be placing HINTS. My layout is... interesting :-p
I've recently tried adding a load of detail, and now my compile crashes on vrad @ 90% 'building leafs' - I've spent three days trying to work out where I went wrong?!
"Such monstrous sucking-constructions aren't built within one afternoon"
If your brushes are too detailed, you may end up with the dreaded "micro-brush" error.
From experience, hint brushes do not shorten compile time at all. They certainly do not fix compilation crashes or errors.
Using hint brushes can reduce framerates by limiting the amount of material being rendered in-game.
Vengeance
Olympic
[SP] Interception
Interception PeTI
Herman
Uprise
Unified
Hint brushes are delicious. One of my favorite in-game optimization things.
[spoiler][SP] Alternate[/spoiler]