|
Post by retroactive on Nov 29, 2008 1:59:45 GMT -5
My map is an estimated 60% complete. It is exactly how I imagined it: the size, the layout, the detail, everything is perfect save for the 40% that involves more detail, texturing, and lighting.
As I hit compile, the dreaded super-slow-never-ending vrad comes up and says "I'll never finish my work, because your map is too big! HA!"
I really don't want to make this map smaller, I don't have any advanced brushes (just blocks and 4 arches).
Here's the question: does anybody know any tips or tricks for improving this situation that don't involve major rework or changes to the map? Is there anything I can do? Thanks for reading.
|
|
|
Post by Lap on Nov 29, 2008 12:33:36 GMT -5
I would definitely take this concern to a larger mapping thread or facepunch. I don't believe we have the knowledge base for that here yet.
|
|
mp6
New Member
Posts: 11
|
Post by mp6 on Mar 18, 2009 21:49:36 GMT -5
This is actually an extremely common problem, you are not alone, the arches are your problem. its an extremely simple fix, the way the source engine renders the in-game level it essentially makes triangles. With the more complex shapes, it needs more and more of these triangles causing the compile to slow down. Tie all of your odd shapes (arches cylinders spheres etc.) to a func_detail entity. Be sure that your map is properly sealed (no leaks) and run a compile, it should speed it up exponentially.
|
|