For some reason, all my maps are apparently not munging properly. I get variations of these same three errors on every map, and have no clue why. This has happened even without me editing the mission LUA. I just tried it with a space map and got the same errors:

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\LoadUtil.cpp(1019)
Unable to find level chunk in MISSION.lvl

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\LuaHelper.cpp(112)
OpenScript(DPSc_Diet Dr. Pepper): script (1fdde5c1) not found

Message Severity: 5
C:\Battlefront2\main\Battlefront2\Source\GameState.cpp(1283)
Could not open MISSION\DPSc_Diet Dr. Pepper.lvl

I get the same thing when I munge land maps, only it'll say ABCc_con.lvl instead. I have no clue what's causing this, as I used the vistamungefix already.

Are you over BFII's 500-mission limit?

Do you get any mungelog errors?

Some of the munge logs have been giving me errors, although I keep getting these same three even on maps that munge apparently error-free.

500 mission limit? I would have no clue how to check. I just started moding recently, so I would guess I'm not over. If so, how would I remedy the situation?



EDIT:
Okay, I'm getting the same three errors even on unedited maps. I can go straight from VisualMunge to finishing the map and the same errors show-up... does that mean there's a problem with the default LUA Visualmunge is copying or something?



EDIT2
I keep getting these same three errors involving .cpp extensions inside of .lvl files. I haven't messed with any .cpp files, so I have no clue why these same three cpp extensions keep showing-up in my crash logs on all my maps. Any clue what could be causing this?
--------
Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\LoadUtil.cpp(1019)
Unable to find level chunk in MISSION.lvl

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\LuaHelper.cpp(112)
OpenScript(GCCc_con): script (e4915022) not found

Message Severity: 5
C:\Battlefront2\main\Battlefront2\Source\GameState.cpp(1283)
Could not open MISSION\GCCc_con.lvl

What OS are you running? How long does the munge take? Look for "Common was unexpected at this time" in your munge output window. You might need the Vista/Windows 7 munge fix. (Look in the FAQ thread)

I'm using Windows 7 and already ued the vistamungefix, so it's not that. However, I've found a couple more clues in other places and it appears my issue may be with the ABC.req or the ABC.mrq. I found something interesting in my munge window on one of my maps:
--------------------------------------------------------------------------------------------------------------
Munging ABC.req
0 file(s) moved.
The system cannot find the path specified.
Munging ABC.req
0 file(s) moved.
The system cannot find the path specified.
1 file(s) moved.
1 file(s) moved.
--------------------------------------------------------------------------------------------------------------
I also got errors on a few of my PCmungelogs stating it cannot find [levelpack ABC_conquest.mrq] and [levelpack ABC_conquest.req]. I have no clue why it can't find ABC.req, as I can find it under worlds\ABC\world1.

Strangely, one map in particular (GCC) doesn't have those errors in the PC Mungelog, but when I run it, it still has the same three errors on the crash log with the .cpps... so it finds the .req, but for some reason still isnt functioning as a map. When I look under data\common, it has a GCC_conquest.mrq, which may explain why there's no error on the PC mungelog, but there's no GCC_conquest.req to go with it. The rest of my maps have no .req or .mrq under data\common.

Any clue where the .req and .mrq files should be or where they might be so I can move them there? Also, if they happen to be absent, how would I go about creating new ones that function properly?

EDIT: I know how to use an .req file, I just have no clue which files I'd need to include or where to place the .req once I'd made it. The same goes for the .mrq and where to put it.




EDIT2
For some reason, even though my abc.req and abc_conquest.mrq are both in the words\abc\world1 directory, I get this error near the end of the munge:

Munging ABC.req
Munging ABC_conquest.mrq
0 file(s) moved.
The system cannot find the path specified.
Munging ABC.req
0 file(s) moved.
The system cannot find the path specified.
1 file(s) moved.
1 file(s) moved.
Munging addme.lua...done.

The crash logs haven't given me any hints as to if this is causing me problems either, so I'm assuming the lack of an req is causing this... any way to ensure it actually munges the req, considering it's in the folder already?

Nobandwidth25 wrote:Munging ABC.req
Munging ABC_conquest.mrq
0 file(s) moved.
The system cannot find the path specified.
Munging ABC.req
0 file(s) moved.
The system cannot find the path specified.
1 file(s) moved.
1 file(s) moved.
Munging addme.lua...done.

I get that too. Mine I guess munges them, dunno if it really does or anything. But if you crash there's definitely something wrong.

these are probably the problems
did the munge do really fast ?
is so you might want to try the munge fix
and if not
what did you edit?

It takes about 2 minutes to munge the map. I already have the mungefix in place, and I confirmed that all my batchfiles are the new editions. The only editing I did was to the ABCc_con LUA (I had to add locals, change the sounds, adjust memory pools, etc.; most of the code was copy-pasted from an asset LUA, so there shouldn't be any typos in the codes), and I also did the "Update REQs" thing in ZoneEditor, and I've gotten the same errors on either side of doing so.

The weird thing is... I've gotten similar errors on maps where I have touched neither the LUA nor updated the REQs. They all have the REQs in their \world1 folder, and they keep giving me those same three errors, although it appears the second and third are caused by the first.

im 88% sure that i get always these errormesages in visualmunge too and everything works just fine anyway. i think they arent the cause for your problem

Okay, now my crash logs just revealed it might be something with my settings or something...

I'm getting the same messages on my crash logs for downloaded maps now, so I guess my machine or settings or something is causing the problems.

Thanks for the help.



EDIT
Okay, this has been bothering me for almsot two months.... I can't get any maps to munge properly. Regardless of what I do or don't do to the map, I'm getting a different variation of these same three errors every time I launch the game: My mungelogs didn't show any errors, so I went to the crashlogs. The thread on here explained that my three errors were caused by a problem with the munging process, so I went to work on fixing it.
-I'm using Windows 7 32-bit, and so I applied the VistaMungefix. Nothing changed.
-I tried running every program in every compatibility mode I could... nothing.
-I tried making new maps from scratch... nothing.
-I tried searching the LUAs for errors... nothing.

Anybody else have any clue what else could be sabotaging me here?

Just to check, are you running it as an Admin? (Right-click on .exe, select "Run as Administrator", click "Yes" on the popup.)

I've just run Visualmunge.exe and modtools both as administrator on two seperate maps.... still getting same three errors.