Complie Process Not Responding For Endless Hours!

  • Site Migration: See bugs? Report them here. Want something changed or have an idea? Suggest it here.
  • If you're asking a question make sure to set the thread type to be a question!
  • Something not downloading? Download authors read this.


Professional Nap Taker
Server Staff
Jun 22, 2017
I have a very simple map; the map is pretty much a cude with a tiny house in the cude. Everytime I try compiling the map, it freezes (Which I understand is normal) and I wait, but after 2 hours maybe more, nothing happens. I restarted my computer, I tried to run everything at fast, yet it's "Not Responding". I use to compile maps in under 10 minutes, but now it's not even compiling at all. What can I do?

Da Spud Lord

Occasionally I make maps
Mar 23, 2017
Which part of the compile process is it getting stuck on? The compile log should give an indication. If you post it here, we should be able to get a much better idea of what your problem is.

Dr. Bum |SCG|

L1: Registered
Oct 2, 2017
I find Hammer's compiler to be fairly unreliable, so I usually stick with compile pal. If you're able to copy the compile log, you can paste it to and most of the time it'll pick up any errors in the compile, tell you how serious of a problem it is, and how to fix it.


Half a Lambert is better than one.
Nov 14, 2009
Step one: Compile with just VBSP and see what happens. The most common causes of long compiles are:
  • Leaks, causing VRAD to drag on forever
  • Overly complex geometry that hasn't been func_detailed, causing VVIS to drag on forever
Assuming your compile ends, look at the log for a line that reads "*** leaked ***". If you find one, hit Map > Load Pointfile. This will show a red line going from a random light source or prop through the gap in the world. Seal the gap and repeat step one until there are no more leaks.

At this point, hit Map > Load Portal File. This will show you how your map was broken up into chunks to be easier to digest. If it looks way too complex, you might have run into scenario B and you'll need to employ func_detail. (That picture of the blue lines going around the cylinder is a good example of what to look out for.) During this process, you can check whether you got all the trim brushes by going to the Visibility Groups panel on the right and hiding all the details. (Just remember to un-hide anything you hid before compiling again, since hidden objects will be left out during the compile as well!)

This stuff can happen to anyone. Just last night I found myself with a stupidly-long VVIS due to me forgetting that blockbullets brushes aren't automatically considered detail.