.Map :: MoHAA Mapping

cancelling a compile destroys the files so the game isn't unstable when opening it.

As to how long a compile it depends on your processor, RAM, what else you have running, how big the map is, and if your computer is struggling with anything, like power or overheating.

You might have paused ur compilation, e.g. by pressing the pause key in ur compile window.
Open the Windows task manager and see how much % of cpu power is used by the process 'q3map.exe' or 'mohlight.exe' depending on the stage it's hanging. It ought to be a rather high value. If there isn't any process relating to ur compilation, well, it isn't compiling at all.
(If it was paused, u'd have to focus the compile window and press space to let it go on.)
Btw, what compile settings did u use?

Q3map.exe is at 99%. My computer doesn't have any overheating problems. I have a gig of RAM I have a Duron 1 GHz processor.

ok, a 1 ghz processor is pretty slow, so that right there may be your problem. mine is 2.1, and most home users have about 2-2.5

Wacko meant go to processes on your ctrl-alt-del menu, and the far right value should be mem usage, and the second far right value should be CPU usage. also check the next tab (performace) and tell us how much % of CPU power is being used.

but compiling is notorious for taking weird amounts of percentages at a time. 99% for example....

Golden-Hammer wrote:I started compiling my map two weeks ago and it stopped at 99%... Bummer!

I first read that as it hung on 99% for two weeks, that cant be right, how long did you let the compile run?

edit: and is a duron really up to the job ?