Is there anything that allows you to start a compile with Nems Batch compiler, and save the compile at a certain point, then resume the compile where you left off? I just can't run a compile for 10-20 hours straight I have to use my comp for other things. So being able to run the compile while I sleep then wake up and suspend then restart the next night would be great.

Usually a compile time shouldn't take longer than 2hrs tops. If it is then you either have a bunch of problems in the map, or have made it very hard for VIS to calculate (basically really really big open areas). If you have the oldest computer ever, then there is something called the remote compile system where you can upload your .rmf to the site and they will compile it for you super fast, but that is if you are wanting to give out your map before it is completed.

Heres the site: RCS (http://rcs.valve-erc.com/)

whoa, good find mex. Good idea. I wont need it but I'll be sure to spread the love. And yeah, 20 hour compile time...too much..

Maybe I'm not checking the right flags when I'm doing a final compile. What are the things you check-off in Nems Batch compiler before you start your compile? I have 4 wads I include in the .bsp, but what is a pretty standard list of compiling presets for a final using Nems 2.0.3?

For a full compile I check csg, bsp, vis, rad. I don't do wad include because I made my own wad which I put in the DOD directory. I do -full vis, and -extra rad. That is the longest type of compile though.

Cracker, what kind of PC are you compiling on? (CPU type/speed, amount of RAM).

It takes me 1hr 18 minutes to do a full (full vis, extra rad) compile of my current map on a P3 1GHz, with 768MB RAM, and the worst I ever had was around 2 1/2 hours on one of my old CS maps on a much lower-specced PC. When I have had compiles appear to freeze up (i.e, they might be going to take hours) it has always been because of a map fault. In my early days I made the classic mistake of putting a big box around my map when I couldn't find a leak and that'll push your compile through the roof since the compilers will have to render eveything, including all the backs of your map that normally would not get rendered.

If your PC isn't a complete dog and it's taking 10 hours I'd say there's a very good chance your map has a problem.

if you are keeping the computer on during the "off time" you could just press the "pause/break" key on your keyboard while it's in the DOS window, and just minimize that window. I recommed having -sparse as one of your RAD tags...and other than that just use the ones that are on Nem's tutorial, they work great.

I have a P4 2.53 ghz, 512 megs of ram so that Is'nt the problem. I don't have a box around my entire map either. It's probably because I have some big open spaces necessary for the map I'm doing. It might be that my map is 635,000 square feet in size. I don't get any errors It's just a large map. Right now I'm trying different tags when I compile to see If I can shorten the time. Thanks for the replys guys.

Well I suggest you just "wait it out" and do one compile to even see if it will finish. If the compile does finish, then you know it is probably a mapper error. If you do get the compile to finish, go in and check out the r_speeds by going into console and typing r_speeds 1 and developer 1. Walk around the map and see if your w_poly and e_poly are above what they should be. A playable map limits w_poly to around 900 tops, and 10,000 e_poly. W_polies are your brushes, and e_polies are your models. I am guessing that your r_speeds are going to be way over these standards if your map is truly large and taking long times to compile.

Originally posted by Cracker
I have a P4 2.53 ghz, 512 megs of ram so that Is'nt the problem. I don't have a box around my entire map either. It's probably because I have some big open spaces necessary for the map I'm doing. It might be that my map is 635,000 square feet in size. I don't get any errors It's just a large map. Right now I'm trying different tags when I compile to see If I can shorten the time. Thanks for the replys guys.
It shouldn't be a map size deal there...my map is 450,000 square feet and compiles in 20 minutes....(I have a 1.33 Athlon and now 512 (had 256 until yesterday)).

You should post compile times of every part of compile process or better full log file.