Vorpx .exe taking too long how to#
Vorpx .exe taking too long full#

vvis.exe is a smart program and will 90% of the time do a fine job. Large areas can be cut up very quickly because they are big empty areas and it doesn't take a lot of thought to make a big empty box. From what I saw of your map this is not the case. Compile times can be long, a few hours if you have lots of small very intricate brushes.

Vorpx .exe taking too long how to#

Sorry for the long post but I really want to find more info on how to both fix this map and prevent it in later maps. So this long compule might simply be from that butДЇigured i would still ask incase theres something im not looking at or thinking of myself. Running even when you are below the map) I am plaing on later going thour and moving the sky boxД«rushes in more but right now I was just waiting. (I amДЄssuming since the skybox texture and the accual walkable map area are so far apart the vvis.exe is The frist area dont bother drawing the 2nd area until you see into the arch way leading to it. In other words how do I tell the compiler that when ur in The comiler knows what to be drawing when. BUT I dont know how to go about spliting the map up so Like the 2 areas I have now I want it so if ppl want to theД¬an try and throw nades into the other area. Know of the hint brush I think its called but am not really sure the proper way of using it in this map The map so far.(video was take with fraps from the hammer editer)Д«ut the reason I am posting this is to find out what I need to look at to help this map to compile. So below is a youtube I made for a friend and was gonna show it to here to let it be the discription of (the other map I heard ALOT of ppl complain it laged lol) Just did the cheap compile on it but the map I am working on now I want to look good and play good Now when this first happend I didnt care about making the map look fancy and such so I Map up into visual blocks to help with runtime renderings of the map and what brushes to draw whenДЄnd such.

Issue is when the vvis.exe is run and from what I know of on what the program does is it carves the

Vorpx .exe taking too long full#

It happened once on a map I was messing with but only when I did the full compile.

* And would the hint brushes fix this and how to use them properlly? * What do I need to do to help prevent long vvis compiles? * vvis.exe after like 15+hours is still grinding away(btw the compiling takes 99% of my cpu load) * Large brushed (hollowed cube) all around the map I am wanting to track down the cause or what might cause the compile time for a map to be insanlly long as in 18+ hours and still not finished.