MOHLIGHT crashes in my new machine !?!?

mcunha98 · Post by **mcunha98** » Sat Dec 23, 2006 8:46 pm

Hi,

People, i replace my old machine (a pentium III - 1.2ghs with 1gb memory) for a new machine (dual core 1.86 with 1gb memory).

The OS is Win2k (in old and new machine, the two machines have equal configuration), but in new machine the MOHLIGHT.exe crash when have 99% of work done !

Some idea (runtimes or another file is required for mohlight.exe) ???

Green Beret · Post by **Green Beret** » Sun Dec 24, 2006 9:17 pm

Update your video graphics, Most likely theres a new update

Make sure entdefs.pk3 is in the main folder, And make sure all your directories are correct on mbuilder.

mcunha98 · Post by **mcunha98** » Sun Dec 24, 2006 10:13 pm

Green Beret wrote:Update your video graphics, Most likely theres a new update
Make sure entdefs.pk3 is in the main folder, And make sure all your directories are correct on mbuilder.

Green Beret,

The problem is only with the map i editing.
I start the development of the map into a machine and now, i use a new machine to finish the work (powerfull new machine). I compile others maps in my folder and all work fine, only with THIS MAP exists the problem !

Post by **Rookie One.pl** » Mon Dec 25, 2006 8:17 am

What are the symptoms of the crash? Error messages, etc.?

mcunha98 · Post by **mcunha98** » Mon Dec 25, 2006 12:50 pm

The directives:

Code: Select all

"d:\maps\mohaa\Q3map.exe" -gamedir C:\ARQUIV~1\EAGAME~1\MOHAA d:\maps\mohaa\maps\obj\user_98sully.map
"d:\maps\mohaa\MOHlight.exe" -gamedir C:\ARQUIV~1\EAGAME~1\MOHAA d:\maps\mohaa\maps\obj\user_98sully.map
"d:\maps\mohaa\precacher.exe" -all d:\maps\mohaa\maps\obj\user_98sully.map

The error:

For each 15 trys, 1 work fine, the rest or make a error or compile the map without light

Post by **Rookie One.pl** » Mon Dec 25, 2006 8:18 pm

Sorry, I don't speak Portugese, could you translate that message?

Is, by chance, that new CPU of yours a 64-bit one?

mcunha98 · Post by **mcunha98** » Mon Dec 25, 2006 11:26 pm

Rookie One.pl wrote:Sorry, I don't speak Portugese, could you translate that message?

Is, by chance, that new CPU of yours a 64-bit one?

Rookie

The message dont "tell" nothing important !
The new CPU is 64-bit, now, i edit into a machine and compile and another (32 bit)

Post by **Rookie One.pl** » Tue Dec 26, 2006 5:49 pm

If it's 64-bit, that might be source of the problem. The compilers do a lot of pointer-based operation, with the assumption of a 32-bit system (it was coded for and compiled under one), which, quite obviously, fails. Even if it didn't crash, it would probably produce erratic lighting.

mcunha98 · Post by **mcunha98** » Wed Dec 27, 2006 1:19 am

Well Rookie,

Thanks for reply.
The problem is that.
Dont have what i do, how i have a second machine, i edit in 64 (more fast) and compile in another (slow, but work).

Thanks again...

bdbodger · Post by **bdbodger** » Wed Dec 27, 2006 1:36 pm

Another thing to concider is that the new cpu is dual core . Cod2 players had problems with cod2 and dual core cpu's . The way to over come that problem was to set the affinity of the cpu . That means you set the program to use only one core . If you use google and look there is a program called setaffinity.exe that can set mohlight to always use only one core . You can do it on the fly or set it to always use only one core . Another way to set affinity is on a windows machine to right click the process in task manager and choose set affinity then choose a core . To do that the process has to be running .

Post by **Rookie One.pl** » Wed Dec 27, 2006 11:13 pm

Bodger can be right, the compilers use multithreading. I just wonder why should it cause problems.

bdbodger · Post by **bdbodger** » Wed Dec 27, 2006 11:19 pm

No idea but if compiling bogs down your dual core machine because it is using both cores and you can't do anything else this can leave one core open for you to do other things while you are compileing . Of course it may mean it is a tiny bit slower to compile not sure about that but makes sence .