why did the compile stop?

[The Ottogirl]

 

[Crash]

That is generally one of the longest steps, if you've got a lot of small things cutting your vis it can take a long time. It probably didn't freeze, it's just really slowly working on that last tick.

 

[The Ottogirl]

That is generally one of the longest steps, if you've got a lot of small things cutting your vis it can take a long time. It probably didn't freeze, it's just really slowly working on that last tick.

i pressed compile, then slept for half an hour AND THEN i took a shower for 40 minutes. i dont think this is supposed to take this long because my visleaves arent that damn complicated:

 

[nesman]

You are correct they aren't too complicated. But having a lot of diagonal cuts like this can slow down the compile time. Look into making some of this stuff func_detail so it doesn't cut vvis.

 

[Tiftid]

i pressed compile, then slept for half an hour AND THEN i took a shower for 40 minutes. i dont think this is supposed to take this long because my visleaves arent that damn complicated:

Yes, it really can take that long.
Looking at your compile, it says 6345 numportals, which is the number of visleaves you have.
This is a pretty high number.

VVIS compiles are also longer if your map is large and open such that all your visleaves can see each other.
I recently made a quick little Half-Life 2 map with just 2500ish numportals, but since it's very open and they can all see each other, it takes nearly half an hour to compile.