How can I fix the VisualMunge problem? (once and for all)

Droideka88 · Post by **Droideka88** » Mon Aug 14, 2006 10:57 am

Here's the documentation for "getting started".

ModTools VisualMunge – Munging and running your new world

This is very important. The steps I just outlined are the only time that you’ll run VisualMunge from the main \data directory. Once you’ve created your new level, you’ll run VisualMunge from inside your \data_abc\_BUILD mod folder, which VisualMunge has created for you. Always be sure that you’re running VisualMunge from the correct folder, to avoid problems. To make things at least somewhat foolproof, you’ll notice that the Munge options have been grayed out when you run VisualMunge from the main data folder, and conversely, the Create New World options are grayed out when you run VisualMunge from inside your new mod folder.

The term “munge” is the term that we use for basically compiling your data for use in the game. We’ll get to actually modifying your new world in a bit, first I’m going to cover munging, and running your new level in the game.

So, by now you should have opened VisualMunge from inside your new mod folder, and you’ll notice that all the Munge options have been enabled, and the Create World options disabled. Your new level will automatically show up in the Worlds drop-down menu, and the only other option that should be selected by default is Common. You can leave everything as is when you run the program. Note: you MUST have your world selected in the worlds list in order for everything to munge and copy correctly.

Click Munge.

Once VisualMunge finishes working it’s magic, you’re all done. You have a level that you can run, and play in the game. Visual Munge copies all the necessary files for running your level into your Battlefront II folder in the following location: \Star Wars Battlefront II\GameData\Addon\ABC (where ABC is the 3-letter name that you gave to your level). Run the game, and your new map should show up in the Instant Action, and Multiplayer playlists.

Apparently that's not case. First off, here's my main problems. For some reason my *** folder only has the core.lvl so it's missing the world file, mission.lvl, and now the addme.script. Maybe I munged in the wrong location but I followed precisely as the doc said. Do I open VisualMunge from the main data folder in LucasArts folder and not from my data_*** > BUILD folder?

Also, I have another problem that may relate to the VisualMunge. In my data_*** folder, I have a SIDES folder. However, inside SIDES, there's a folder called REP (not republic side) and inside contains an empty MUNGED folder. Should I simply delete or what?

If anybody can solve this, then perhaps this common issue could be adressed in the sticky topic in the near future.

RC-1290 · Post by **RC-1290** » Mon Aug 14, 2006 12:21 pm

Do I open VisualMunge from the main data folder in LucasArts folder and not from my data_*** > BUILD folder

Where did you install the modtools? Correct me if I'm wrong but you are supposed to instal them directly under C:\(or whatever the harddrive is called at your computer). I don't know why but if you install it, for instance, at C:\LucasArts\ the program seems to get bugged.....

darthpingu · Post by **darthpingu** » Mon Aug 14, 2006 12:30 pm

I installed it directly on D(programfiles), since the documentation told me to do so because they wouldn't support me if I installed elsewhere...

Droideka88 · Post by **Droideka88** » Mon Aug 14, 2006 12:30 pm

Here's what I have in my LucasArts folder.

It's like this C:Program Files\ LucasArts\ then what?

darthpingu · Post by **darthpingu** » Mon Aug 14, 2006 12:31 pm

ooo that's just a mess

. ou should reinstall the mod-tools in an own folder...

RC-1290 · Post by **RC-1290** » Mon Aug 14, 2006 12:42 pm

This what you should do: Turn on some music you like, so you can relax while reading the documentation. Trust me, it works. (Very usefull while modding as well).
Re-install the tools at C:\
So eventually its set up this way: C:\BF2_ModTools

First, unzip your BF2_ModTools zip file into the root of your C: drive. We can’t be held responsible should you put it somewhere else, and things don’t work, so just take our advice…this is where you want to put your BF2 Mod Tools files. Inside, you’ll find the following folders:

So DON'T extract it under Program Files

Ace_Azzameen_5 · Post by **Ace_Azzameen_5** » Mon Aug 14, 2006 1:07 pm

Cut n paste!
Just move the folder, don't reinstall. Move it to the root of the drive, C:\ or D:\ etc.

crazytieguy · Post by **crazytieguy** » Mon Aug 14, 2006 1:34 pm

Also, you should move BF2_Modtools to the Gamedata folder...

Droideka88 · Post by **Droideka88** » Mon Aug 14, 2006 1:37 pm

So eventually its set up this way: C:\BF2_ModTools

Also, you should move BF2_Modtools to the Gamedata folder...

Ok now I'm being given two things at different locations. Explain please.

xwingguy · Post by **xwingguy** » Mon Aug 14, 2006 1:39 pm

he means modtools.exe should be moved to the gamedata folder.

Post by **[RDH]Zerted** » Mon Aug 14, 2006 2:59 pm

Location doesn't matter, put it where ever you want. I have mine on a memory stick.

If you have the CD version, copy BF2_mottools.exe to the game's GameData folder.

You may need to copy a .dll from the game's files to where you placed the mod tools.

Droideka88 · Post by **Droideka88** » Mon Aug 14, 2006 3:08 pm

Yes! Ok it finally works. Now my only question is do I have to re-munge if I want to place all the sides into my data_*** folder?

Also now I have something weird...Look.

Post by **[RDH]Zerted** » Mon Aug 14, 2006 3:25 pm

Did you update SWBF2 to version 1.1?

RC-1290 · Post by **RC-1290** » Mon Aug 14, 2006 3:48 pm

looks like a localisation error to me...ofcours I'm not an expert. Try to munge localize; click the checkbox.

Zerted, location DOES matter. You have installed the tools in correct place as well; The Root of a USB stick( uge memmory capicity you got there) wich is probably F:\BF2_ModTools...

Post by **Teancum** » Mon Aug 14, 2006 5:49 pm

The rule of thumb for installing the mod tools is that it cannot be in a directory with a space in the name.

C:\Program Files\Star Wars Battlefront II\Mod Tools == VERY BAD

C:\Games\No\Spaces\In\My\Folders\BF2_Tools == fine

Post by **[RDH]Zerted** » Tue Aug 15, 2006 1:45 am

Just look at your picture: Star Wars Battlefront 2 v. 1.0. You need to upgrade to version 1.1.

off-topic: I moved the tools to the stick while I am wipeing out the hard drive they where on. I have them at w:\backups\nDrive\development\SWBF2\BF2_ModTools. Munging runs really slow, but I'm not keeping them there long.

Droideka88 · Post by **Droideka88** » Tue Aug 15, 2006 2:05 am

@ Zerted: Already upgraded.

Off-topic: Teancum seeing as how you are in charge of this thread...

http://www.gametoast.com/index.php?name ... pic&t=3497

...do you think you can make a link directly to this explaining how things should be installed correctly? That way future questions like these will be directed towards using the Search bar or checking the links that may contain somebody's anwsers.

One more question: If I want my mission.lvl to be changed, I have to modify the LUA scripts correct?

Post by **Teancum** » Tue Aug 15, 2006 7:52 am

Depends on what you want to do. It's not recommended to replace the original mission.lvl.