
01-06-2003, 08:12 PM
Guy- you gotta realize that most of us are working on our own projects.
Compiling can take hours and sometimes days on large maps depending on your system and the construction of the map.
It eats up the processor and leaves almost nothing for other pc functions--basically rendering it useless because it is just too slow to use for anything else.
If I had a system dedicated to compiling only, I would do it for you. But I don't. I don't know that too many people will do this for you. As far as I'm concerned it's part of the mapping process. And long compiles help you to learn what mistakes you are making, and how to fix them. (The console is a good friend.)
You can do a non-vis compile for testing purposes. Since you won't compile the vis or light, your world willl be overbright, but at least you can get a feel for the placement of brushes and entities.
If you are using MBuilder, simply copy the .bsp file that it writes in the first step into dm if you are making MP non-obj map. You can then start your game and run your map from the maplist.
When you are satisfied, you can then do your full compile (that may take forever!).
One word of advice-- remove the .bsp from the dm folder before you compile again! Sometimes, it won't write the new file.
Good Luck
Kill Ya Later.
|