When compiling my map.

[Little Pixel]

So I'm having a problem for when I compile my map.


The problem is that when I do it, it seems to be working fine at first, but than it just freezes and starts not responding and just doesn't finish at all, I even have it so it starts tf2 when it's done so I can test it, but it never gets to that point.

 

[Dadema]

So I'm having a problem for when I compile my map.


The problem is that when I do it, it seems to be working fine at first, but than it just freezes and starts not responding and just doesn't finish at all, I even have it so it starts tf2 when it's done so I can test it, but it never gets to that point.

Does hammer crash entirely, or just the compile window?

 

[Vel0city]

Compiling takes up lots of your computer's power. In fact, it completely fills the CPU with work. It will look like your PC/the compiler hangs/crashes, but in reality it's just crunching numbers together.

What are your computer's specs, and at what point during the compile process does it appear to be freezing?

 

[Little Pixel]

Does hammer crash entirely, or just the compile window?

It doesn't crash, it's just not responding in a way. It doesn#t start up tf2 when it's done because it doesn't seem to ever finish and I've had it stay like that for like two hours now and still nothing has happened.

 

[killohurtz]

This is actually normal. Hammer will stop responding during a compile, but as long as any of the processes (vbsp.exe, vvis.exe, and vrad.exe) are running in Task Manager, it's still doing its job. Compiles most often get hung up on vvis, so if that's the case with your map then you should look into optimization to help reduce compile times.

 

[seth]

Yeah, that's normal. Compiling is a really CPU intensive process and if you're compiling with Hammer's native tools, then yeah it'll be totally unresponsive. I'd recommend checking out CompilePal if you want to be able to use Hammer while compiling.

 

[Crowbar]

I would not recommend using whatever while compiling because it slows down both compiler and the program you are using, since neither will have enough CPU to work normal.

 

[henke37]

Compiles most often get hung up on vvis, so if that's the case with your map then you should look into optimization to help reduce compile times.

It's vrad that tends to take forever. vvis is barely measurable.

 

[nickybakes]

It's vrad that tends to take forever. vvis is barely measurable.

Vvis and vrad can usually take some time to compile. Sevin suggested using a program called CompilePal. You could also use a program called VBCT (Valve Batch Compiler Tool). It's just another interface for compiling, but it doesn't freeze up/not respond like Hammer does.

 

[worMatty]

Hammer's compile window appears to freeze because Windows thinks there is a problem with it and overlays it with a static image of itself with a working Close button. It does this to make the user feel like they have some influence over, and interaction with a frozen app. App authors can program their apps to prevent Windows from doing this. External compile interfaces such as CompilePal and VBCT don't have this problem, so by using one of those you will see what's taking so long.

If after trying that, @Little Pixel, you would like some help figuring out why it's taking so long to compile, we can look at your VMF.