Compiling error Created 17 years ago2007-03-26 17:52:02 UTC by blast strike

I'm trying to compile my map, but it stop here:

I waited more than 15 minutes... but it stayed to "0%".

Can someone help me?

Thanks

I don't see the 0% in that screenshot...

It might still be working. If you open the task manager, you'll see if the RAD procedure is still taking up a lot of CPU usage.
You should also give some sort of description about your map. If one of those 4 direct lights mentioned in the compile window is a light_enviroment lighting up a big level, compile times can end up being hours. (My last Source-engine compile was 5 hours long).

You should write an -estimate parameter next to all the commands, this will show you how much the compiler has left. 1000/4570 for example.

The buildvisleafs is one of the two hardest and most time and power comsumining phases of the compiling. The other is leafthread

It... well... may have frozen. I'd hate to sit there when the damn thing isn't working, thinking it's still working...

open up task manager... if the CPU Usage percentage is low, its not working.... if its 100%, it sure as hell is working...

It's 100%, but at -estimate is 0...

I waited for long time, and it still 0...

347 leafs... that shouldn't cause any problems, the map isn't really big or complex. My recent map had 11000...
I don't really know why it is frozen, does it happen in any other map compiles?
Were there any errors in the compile log before the rad procces?
Describ the map, maybe we can understand whats causing the problem if you'll give us a short discription of the map.

By the way when Barttylord asked you to look in the task manager he ment that you should check the procceses tab.(the procces is called Hlrad, If it's working and taking all the CPU that means you might need to wait more)

It happens only in this map...
There were no errors before the rad procces...
It's a surf map... But some time before I could compile the "ramps"...

PS: The compile was getting a leaf error... then I change the ramps brushs to func_wall... Now it's not getting any error, but it stop there...