Hi all,

I just started with modding Battlefront II, but I think Vista doesn't really like VisualMunge... When I munge, this is the munge output: And the addon\ZZZ\data\_LVL_PC dir is empty, but the addme.script is there.

As said, i'm using vista, to be precise Ultimate 64-bits SP2.

I tried to munge it 3 times, 1st with a change 2nd a whole new map, no changes, and the 3rd time I redownloaded the mod tools, no changes.

Does anybody know what might cause this problem?

are some items hidden for you on your computer? If so you might need to "unhide" them. I'm not too sure how to do this - a experienced modder might though.

No, there are no files/folders hidden. Besides, if I open Battlefront II and select that map, the game crashes upon launching with a fatal error.

try a clean then munge again. It might be your visual munge - maybe it wasn't downloaded properly - I don't know.

There is nothing to clean, as there's nothing that is munged. A clean won't help... and btw, there's no _LVL_PC folder in the data_zzz folder.

Thats normal, I get it all the time. It can be ignored

Well, that was just a side note -- the fact is that the munging process doesn't work (as mentioned earlier, I've tested it in-game and I got a fatal error).

I'd normally go through a short round of questioning, but in order to head off any other misleading questions, go ahead and follow THIS as it seems like you have the same problem.

I tried that one -- in fact, I searched 4 pages for topics with 'visualmunge' and I didn't find anything that helped me out.

So, said that, I'm ready for your (short) round of questioning!

Go to the folder:
users/(username)/Appdata/local/virtualstore/program files/lucasarts/star wars battlefront II/gamedata/addon.
With some users, the new map gets stored there.

I tried that one, but there's no gamedata\addon... So that isn't the problem.

In fact, the munge output is way too short for a good munge, I guess.

Have you tried this?

I was just going to ask questions to see if that fix would work. How fast is your munge? Are you sure that what you posted is the full munge output (i.e. is there a scroll bar where you can select more or do you see a bunch of stuff fly by before it gets to that)?

The reason I assumed that would work is because your symptoms would seem to match that perfectly.

Fierfek wrote:Have you tried this?

As mentioned before, yes.

Frisbeetarian wrote:I was just going to ask questions to see if that fix would work. How fast is your munge? Are you sure that what you posted is the full munge output (i.e. is there a scroll bar where you can select more or do you see a bunch of stuff fly by before it gets to that)?

The reason I assumed that would work is because your symptoms would seem to match that perfectly.

It is the full munge output, and the munge takes about 1 second. And, in fact, the guys for who that fix worked, had a lot more munge output, and also a '\Common was unexpected at this time.', which I don't.

Its because its on ur D-Drive. reinstall it onto the C drive, the default location, that'll work, trust me.

King Kong wrote:And, in fact, the guys for who that fix worked, had a lot more munge output, and also a '\Common was unexpected at this time.', which I don't.

Not true. The only output I had was what I posted in that thread. There have been people who have posted exactly what you did, not realizing that there was the extra "\Common" line that they didn't see. If you downloaded that file, extracted it, ran the batch file, and then remunged and got the same result, there's not much more I can do without more information (not that I know what else you could give me).

riku2211 wrote:Its because its on your D-Drive. reinstall it onto the C drive, the default location, that'll work, trust me.

Feel free to ignore this, he's wrong.

@riku2211
Please don't offer advise when you don't know. It's been said multiple times that you can install the ModTools to any path without a space in it. Not only that, but in case, the D:\ path is his default.

A quite experienced modder teached me the bare basics yesterday, and he already gave me a lot of advise -- including moving it from the C: drive to the D:, because SWBII is installed there. It didn't work either.

This morning, I tried again -- the munge output doesn't grow, and it's still 1 sec or less...

First off, you shouldn't MOVE it. You should try reinstalling. It might be your map - maybe there's an error with that which wouldn't let you munge. This happened to me once when I made a map but fiddled with the addme.lua and made the munge exit.

I already tried reinstalling it, from a different file download, and I already tried an empty map, with no changes. It didn't pay out, though...

hmmmm..this is very strange.
Perhaps it's your computer? Or maybe the computer will not let you munge? (It can be done)
Try setting your Administrative Rights to something higher (depends on your make of computer)