Problem:
Every map I munge, new or old, the localization refuses to work.

Information:
Too many arguments in command line: In the selection screen my maps appear by:

CAO%s_%s
RWC%s_%s

Addme script line the name originates from: I experimented and put a name in place of: The name changes in the selection screen but, since the scripts have no name of that sort, it can't read the mission.lvl

Solutions Tried:
- Unistalled and Re-installed SWBF2 and the ModTools (5) times total. ~No change
- Installed ModTools to different localtions in E: Drive ~No change

I cannot install on Drive C:

Has anyone had this problem? And any possible solutions would be appreciated.

Every time you reinstalled SWBF2, did you make sure to install the 1.1 patch as well?

The 1.1 patch won't effect how the mod tools work. You are reinstalling the mod tools in a path without any spaces in it correct?

Yeah, thats correct.

Locations I installed it in:

E:\Backup\BF2_ModTools
E:\LucasArts\BF2_ModTools
E:\BF2_ModTools ~Where it is currently installed.

[RDH]Zerted wrote:The 1.1 patch won't have how the mod tools work.

I think I got what you were going for there , but I thought that the mod maps show up unlocalized in the selection screen if you didn't have the 1.1 patch. I thought that might be the problem.

It might've been, but it has to be the ModTools because of what I found in VisualMunge. And 1.1 came with my SWBF2 game.

Frisbeetarian wrote:..but I thought that the mod maps show up unlocalized in the selection screen if you didn't have the 1.1 patch...

Ahh, good point. Also, I fixed the typo in my last post.

I assume you are getting this problem when you munge a new, blank map with only Common checked?

Yup, everytime I make a new, blank map it has this localization problem. And when I munge my old projects, they get the localization problem as well.

Does that mean that this wasn't always a problem? If so, what changes have you made to your computer between when it worked and when it stopped working?

Not much really.. My computer updated itself and that's all. I unistalled SWBF2 for awhile also but not the ModTools, could that've been the reason?

How long was it after you knew it worked until you realized it had stopped working? A computer update is not the only thing that can mess with the ModTools, I know that when I installed the DirectX SDK a while back, it screwed up my ModTools, so what other changes have you made?

It was about 3 months later when I started them up again after re-installing SWBF2. The only other major updates were DirectX 9 or 10 and some Anit-Spyware updates.