Page 1 of 3
Munge Problem (short munge) (FAQ)
Posted: Sun Sep 28, 2008 9:04 am
by SilvaDalek
I don't know if it is me skrewing up, or if something is wrong.
Munging now takes less than a second. And because I can't actually see the map until later when I hae graphics card installed, I have no idea if it worked. I put my odf, msh, effect, and munged folders in data_###/Worlds/###/.
There's quite a bit of stuff in there, so I'm assuming something went wrong.
Edit: I get this when I munge
Edit:
I have Vista, so I'm guessing this is Vista related.
Re: Munge Problem
Posted: Sun Sep 28, 2008 9:23 am
by obiboba3po
im just gonna take a shot in the dark, i dont think this is vista related. it could be but i doubt it. if you have the right graphics, video, and sound cards modtools works like a charm. (but you said you dont have the right graphic card so...) but based on those errors, it says something about a clean...is it possible that you hit clean instead of munge?
Re: Munge Problem
Posted: Sun Sep 28, 2008 9:37 am
by SilvaDalek
No, I hit the right buttons lol.
I don't have a graphics card in my comp yet. It's sitting next to me on the floor. Would that effect the munge?
Re: Munge Problem
Posted: Sun Sep 28, 2008 9:50 am
by RED51
SilvaDalek wrote:No, I hit the right buttons lol.
I don't have a graphics card in my comp yet. It's sitting next to me on the floor. Would that effect the munge?
lol

, I think that might affect your munge, but I'm not so sure. Are your mod tools are installed in your C drive? I read some where that that might affect the munge process.
Re: Munge Problem
Posted: Sun Sep 28, 2008 12:06 pm
by [RDH]Zerted
The graphics and sound cards have nothing to do with VisualMunge. The graphics only matter for ZE startup problems.
Yeah, it does look like you attempted a clean. If not, then why are you trying to munge everything? You should never need to do that.
You did a clean (in which case all that output is normal), you have a space in the folder path where you installed the modtools (in which case you need to install the modtools somewhere without a space), or Vista is putting some of your files in a secured, hidden folder (in which case you need to move them back to their real locations).
Re: Munge Problem
Posted: Sun Sep 28, 2008 1:18 pm
by SilvaDalek
I know, the information in the hide thing is a clean.
The munge looks perfectly fine to me, but when I munged common and localize it does it in less than a second and I don't see any of the stuff it has munged...
Where should I look for these hidden folders then?
Re: Munge Problem
Posted: Sun Sep 28, 2008 3:02 pm
by Thunder
the hidden folders can could probeblly be in your C:\Users folder
if not there, Open VisualMunge at click on the toolbar there, select options set your directory to somewhere basic (ex. an easy to retreave folder) and your map will be munged to that location, open the folder and there you are.
Re: Munge Problem
Posted: Sun Sep 28, 2008 11:27 pm
by [RDH]Zerted
Create a new, blank map and try to munge Common on that. If you can, then your first map is messed up. If you can't, then your modtools are messed up.
Re: Munge Problem
Posted: Mon Sep 29, 2008 5:09 pm
by Frisbeetarian
This speedy munge problem is the same one I have, though the end of the munge looks like this:
Code: Select all
\Common was unexpected at this time.
Munging addme.lua...done.
Copying files to Battlefront II directory:
"C:\ProgramFiles\LucasArts\Star Wars Battlefront II\GameData"
Addon dir exists, continuing...
Mod dir "ABC"exists, continuing...
Copying addme.script to mod dir...done
Copying "mission.lvl" to modDir\data\_LVL_PC\...done
Copying "core.lvl" to modDir\data\_LVL_PC\...done
Copying "ABC" to modDir\data\_LVL_PC\...done
Copying "SIDE" to modDir\data\_LVL_PC\...done
Munge process finished
And yes, this happens on a brand new map.
Re: Munge Problem
Posted: Mon Sep 29, 2008 6:22 pm
by SilvaDalek
That's what my munge looks like with the wierd "Common unexpected at this time"

Re: Munge Problem
Posted: Thu Oct 02, 2008 7:57 pm
by [RDH]Zerted
What folder did you install the mod tools in?
Re: Munge Problem
Posted: Thu Oct 02, 2008 8:29 pm
by Frisbeetarian
For me it's in C:\.
Re: Munge Problem
Posted: Thu Oct 02, 2008 9:21 pm
by SilvaDalek
It's in C:/ BF2_Modtools
Re: Munge Problem
Posted: Mon Jan 05, 2009 4:01 am
by Frisbeetarian
Sorry for the bump, but I have an update that might help someone else help me solve this problem. I have narrowed down the cause of the error "\Common was unexpected at this time." to be in the batch file _BUILD\munge.bat. Specifically, by adding pauses in the code (a pause before this line prompts to continue while a pause after this line won't go as the munge has already crashed). The munge crashes at the highlighted line
which is about two thirds of the way down the file. The only references to "MUNGE_BIN_DIR" are in this excerpt here.
Just to get through what it's not: I've installed the tools multiple times and the same thing happens, the directory it's installed in is above, and I've compared the files and folder structure to that on another computer that can munge and it's identical.
EDIT:
So I'd still like to figure out what was wrong with the original files, but after working on it for another 10 or 15 minutes, I found a work around. I assumed that since my munge bin directory would always be ToolsFL\Bin, I went ahead and deleted the highlighted line above (and the closing parenthese) to make the file always set the bin directory to this. The munge went on a few lines until it reached the munge common portion, in which case it failed upon running the _BUILD\Common\munge.bat. I looked in this file and I noticed the last five lines quoted above also appeared. After making the same changes, I could run a full munge properly with common checked.
I looked into the other munge.bat files littered about and noticed they had similar lines as well, so all my munges should work. I still don't understand, however, what was wrong in the first place and why the munge on this computer failed when it didn't on my other. Could it be an update to Windows NT that slightly changes how batch files are read?
If anyone can shine some light on this mystery, I would be very appreciative.
Re: Munge Problem
Posted: Mon Jan 12, 2009 10:00 am
by impspy
Okay, i deleted the lines but i still get the /common was unexpected line whenever i munge
Re: Munge Problem
Posted: Mon Jan 12, 2009 11:23 am
by Frisbeetarian
From what you said in the other thread, you are just trying to munge changes to a shipped world. If this is the case, post (in hide tags please) the contents of your _BUILD\munge.bat and _BUILD\Common\munge.bat. If this is not the case, what are you trying to munge?
Re: Munge Problem
Posted: Mon Jan 12, 2009 11:48 am
by impspy
Frisbeetarian wrote:From what you said in the other thread, you are just trying to munge changes to a shipped world. If this is the case, post (in hide tags please) the contents of your _BUILD\munge.bat and _BUILD\Common\munge.bat. If this is not the case, what are you trying to munge?
yeah, I'm trying to edit a shipped map.
_Build/munge.bat
_Build/Common/munge.bat
Re: Munge Problem
Posted: Mon Jan 12, 2009 5:22 pm
by Frisbeetarian
Woops, looks like I should have caught your mistake when you said "lines." If you read what I said again, you'll notice I only mentioned deleting the highlighted line, not the entire text I quoted (I just quoted it all for a reference point) (I also mentioned deleting the closing parenthese, and since that's on another line, I guess you should delete "lines"

).
I've uploaded the fixed _BUILD\munge.bat and _BUILD\Common\munge.bat to Filefront at this link:
LINK REMOVED See next page for expanded fix.
All I did for these files was to edit my original files and upload them (I actually commented out the unnecessary sections instead of deleting them). Don't forget to delete the old munge.bat files and rename the new ones to just munge.bat; I included in their file names the folder each should go in.
DISCLAIMER: I am not recommending that you overwrite the orginal files in the BF2_ModTools\data folder. You can do this at your own risk, but heed what the getting started document says, which is "
DO NOT MODIFY ANY FILES IN THIS FOLDER." Just modify the files in BF2_ModTools\data_ABC (where ABC is the 3 letter mapID).
Also, if you want to munge more than just common, you have to edit the munge.bat files in each of the respective folders the same way it was edited in these batch files.
Re: Munge Problem
Posted: Tue Jan 13, 2009 3:01 pm
by phazon_elite
My god, THANK YOU!!! I've been having this same problem for a long time now, and I thought I wouldn't be able to mod anymore. Man, what a relief!!
EDIT: It works, although what would you do to edit, say, the batch file that munges sides?
Re: Munge Problem
Posted: Tue Jan 13, 2009 3:19 pm
by impspy
i installed it and the munge ran longer then it had, but it still didn't create a lvl file
