.Map :: MoHAA Mapping

Hi peeps i've seen it here before but cant find it,
as my map is fairly large and will take a fair old time to compile can some one please tell me how to pause the compile process.
Thx in advance
Seere.

hit otehr options in MBuilder and choose pause after (BSP, Vis, Light)

No thats not what I mean, i'm sure there is something you can press to pause it because as the vis stage takes many hours I want to be able to pause it to enable me to do other things so pausing after vis is kinda useless.
Seere.

Press the Break key, 3 buttoms away from the F12 key

If you want to continue, press enter.

You can also:

1) press CTRL+ALT+DELETE to bring up the task manager.
2) Select the Processes tab.
3) Right click the MOHLight process. (or Q3map or what it is again, I forget)
4) Select Set priprity... -> Low.

This way the compile will continue at almost full speed if you dont use the computer, but as soon as you do anything else with it: the compile backs off immediately

Thx bjarne...thought as much...however some kind soul has given me remote access to their comp so im compiling from there...however with vis data size 1 million 800,000 its taking a fair time hehe.
I can and will reduce this figure but i do assume that as frustrating as it is the more you allow vis to do its stuff the better results will come of it.
PS....51% after 30 hours :S
Bjarne how long did the canal take to compile (the vis stage) and what was your vis count please?
Thx.
Seere.

The vis was not that long, perhaps an hour tops at full blast... light is the main time hog if you do effective detail/structural brush work.

well,there is a very key component forgotten here .the cpu !!
bjarne's might have been more powerful .

If your VIS compile is huge ( say 10+ hours ), then you can be pretty sure its not the CPU:s fault, bad VIS design is probably the reason. Doing effective VIS design is very hard.

I've got a AMD 1800+ b.t.w., so its not really powerful....

I've never understood what causes such long compile times that people talk about, unless the compile gets exponentialy longer as the data grows past a certain point. My longest map compiles have never passed 5-6 hours with final light. Maybe im doing something wrong or there are some key advanced compiling options that I dont indulge in or something heh.

though ive never had visdata of 1.8 million - I'd guess my maps are designed usualy for 12 - 24 players(but could hold more, but like stock maps they would be very full at 30+). My visdata on what i compiled last night was 460328 and it compiles on final light in about 3 hours. (actualy the test version I wanted to see that I compiled last night compiled in just about an hour+ cause it only has spotlights in that version vis compile took 13 minutes - light compile took 62 minutes.)

What is it that makes maps take so long to compile?

Splaetos wrote:What is it that makes maps take so long to compile?

This is not a tutorial type answer, but basically: Not knowing how the compiler thinks gives you long compile times...

well a long time ago, before I had ever mapped, It seemed i should be preparing myself for neverending huge compiles... and ive never really had one that was interminable or anything... so its just wierd lol

Ok..I feel im a reasonably expierienced mapper now and maybe my post was a little misleading.
As i am not using my computer to compile the map i am not bothered about the vis count as it isnt stoping me doing other things and I purely want to see how it performs with more structual brushes....(bear in mind prior to detailing brushes the vis count was 5 million plus)
More can and will be detailed but im interested to see how it deals with it.
Thx for the replies.
Seere.

to aswer seere: word!

Some people (often programmers) have an inherent understanding of how computers work (and therefore compiling) (VIS compie is also a compile).

Thats why im a plumber hehe