Compiling takes too long
Moderator: Moderators
-
Krane
- Lieutenant General
- Posts: 782
- Joined: Sat May 31, 2003 4:18 pm
- Location: California, USA
- Contact:
Compiling takes too long
I realize that the more brushes I'm putting on my map, the bigger is the time to compile. The problem is I've just made a grandstaircase (27 steps, 27 square brushes). Now my compiling time jumps from 15 min (strange I only have 1 house...) to an hour (after the staircase).
So, is that normal? There's nothing there but 1 house.
So, is that normal? There's nothing there but 1 house.
-
Bjarne BZR
- Site Admin
- Posts: 3298
- Joined: Wed Feb 05, 2003 2:04 pm
- Location: Sweden
- Contact:
-
Bjarne BZR
- Site Admin
- Posts: 3298
- Joined: Wed Feb 05, 2003 2:04 pm
- Location: Sweden
- Contact:
Not really shure how you ment this, but this is what happens if you "open the skybox":Zip wrote:I think if you have a leak in your map it reduces the compile time (it misses out the .prt file) You can then re-seal it at the end for your final compile. That's what he meant i think
The VIS compile process is destroyed completely and can not be done: so the VIS stage takes virtually no time at all ( compared to a proper VIS compile ).
Because of this, all VIS optimizations are gone, and the map will have bad FPS...
So why would I do it?
Because when mapping you often want to just see "how it looks with that thing moved to there"... and if you dont give a rats ass about preformance: you sacrifice it to the God of fast compiles.
Because of this it is NOT a solution for released compiles and for complies made to test map performance.

