Page 1 of 1
Localization error message.....?
Posted: Tue Mar 02, 2004 2:09 am
by Twig Masters *MBC*
I am fairly new to mapping for MOHAA and I have a limited knowledge of how the whole process works.
I am using Mbuilder to compile my maps. For a while I was using a command line and or batch file to compile the map. Had no problems before now.
But now that I'm using Mbuilder I am getting an error message when I start MOHAA. It goes directly to the main menue and the consol is open with the error message. I dont even see the EA game logo or the game intro.
The game seems to run fine but I am just wondering why this error is there and how I can get rid of it. Its rather annoying.
Here's a screenie of the error.

Posted: Tue Mar 02, 2004 3:15 am
by omniscient
do u have a no-cd patch installed?
Posted: Tue Mar 02, 2004 3:30 am
by Random
ok you might not of seen this but somewhere in the command lines you have +1 skipintro. Also when you skip the intro game goes right into console and yes you will see a ton of annoying localiztion errors in game. Like when playing an obj map every second the clock tics down you will recieve another localization error.
Is this normal im not sure but i havent noticed any detrimental effects on mohaa do to localization errors yet. I'm not stating for a fact that it is not a problem only that i get them all the time and i see no drop off in game play or map development.
Hopes this sets your mind at ease a bit.
Random
Posted: Tue Mar 02, 2004 3:32 am
by bighoss
I have had that same problem. I didnt have a no-cd patch installed either. I uninstalled and reinstalled my game to get rid of the error. That is the most simple way I know to get rid of it. I'm sure that there is another way that someone else knows about though.
Localization.txt
Posted: Tue Mar 02, 2004 8:31 am
by tltrude
If you want to get rid of the localization errors (they don't really matter), just modify the "localization.txt" file located in pak0.pk3/global. However, you should never add a localization file to your mod pk3 when you release it. Not everyone that will download and install your pk3 will be using the english version of it, and you could screw up their game!
But, it is alright to add text to your own localization.txt file. Just put it in main/global to override the one in pak0.
Posted: Tue Mar 02, 2004 11:53 am
by crunch
Interestingly enough, I also have the same problem. But I have learned to ignore it.
The funny thing is, that about 1/2 of the original localizations no longer work.
I tried c&p the localization.txt into main\global from both the pak0 and pak6.pk3's, and neither worked.
Even more strange, is that when I edit it to add my owqn localizations (the one in global) they always work.
Go figure.
Posted: Tue Mar 02, 2004 7:49 pm
by Twig Masters *MBC*
Random wrote:ok you might not of seen this but somewhere in the command lines you have +1 skipintro...
...Hopes this sets your mind at ease a bit.
Random
Where do I find the +1 skipintro line? Can I remove it ? And If I do will it fix it?
I realize its not a big deal but it is kind of annoying seeing that error all the time.
developer mode
Posted: Tue Mar 02, 2004 8:47 pm
by tltrude
It should be in the poperties of your desktop shortcut for playing the game. The console is open because developer mode is set. Here is what the target line in my shortcut looks like.
Target:
"C:\Program Files\EA GAMES\MOHAA\MOHAA.exe" +set cl_playintro 0 +set ui_skip_eamovie 1 +set ui_skip_titlescreen 1 +set ui_skip_legalscreen 1 +set developer 1 +set ui_console 1
It might also be in Mbuilder, if you are running the game from there. Click on other options and you will see the commmand line that looks like this.
+set developer 1 +set thereisnomonkey 1 +set cheats 1 +set ui_console 1
It is better to just not let Mbuilder run your game. Just uncheck "Launch MOH:AA after compile" to stop it.
Posted: Wed Mar 03, 2004 10:41 pm
by M&M
set ui_skip_eamovie 1 +set ui_skip_titlescreen 1 +set ui_skip_legalscreen 1
what are those for????
i only use cl_playintro 0 and i get into mohaa without any loading screens or the logo or the movie or anything.i click mohaas shortcut and i get mohaa with the console window opened up. btw how can i stop that console window from opening up ?it didnt use 2 open up b4 i installed mohradient so who 2 i do 2 return it 2 normal?
Posted: Mon Mar 15, 2004 1:53 am
by Blackjaxe
Somehow my reply to this post went somewhere else....just like my Localization error....hehehehehe.
I am somewhat hesitant about fooling around with or modifing Pk3 files. Is it neccessary to alter these in order to get my maps to compile properly.
I get the same message ...does not have a localization entry. Exactly what do I need to do to solve this problem and get my maps to work. The tutorials make it sound easy...I have added player start and lights and whatever else but it will not compile for me......HELP anyone......argggggggggg.
Oh yeh I do not use the No Cd Crack...in fact because my clan uses Missionary I'm running pure stock, right out of the box.
Blackjaxe

Ignore them
Posted: Mon Mar 15, 2004 2:52 am
by tltrude
Ignore the errors, they are just something you have to live with. When you print messages in your script, try to use "noloc" which means "no localazation".
Posted: Mon Mar 15, 2004 5:08 am
by Blackjaxe
OK...here's something I haven't done yet. I need to script my path for the compiler to work ?????? is that what your saying Tom
Blackjaxe.
Sorry but I'm really new at this and the questions might sound real downright Dumb.....But I want this to work.
error
Posted: Tue Mar 16, 2004 5:42 am
by tltrude
If your map is not compiling, it is not because of a localization error. The script I mentioned is something you can make for your map to use in the game.
For MBuilder:
You can make seperate logs for all steps, or just the one you need. Click on "change" and put the code after your compile options. The text file can have any name you wish.
-v > c:\WINDOWS\desktop\log_bsp.txt
-fast > c:\WINDOWS\desktop\log_vis.txt
> c:\WINDOWS\desktop\log_light.txt
I have them going to my desktop, so they can be trashed easily after looking them over. But, your path to the desktop may be different. Also, using these logs, nothing will be printed to the DOS window during the compile.
Post the log(s) here and we will find the problem.