Hey guys ive got a new problem, none of the command posts are appearing on my map. I have not done any editing on the map and did not fiddle with the command posts or LUA other than setting up the custom sides. I did a search and came across this thread http://www.gametoast.com/forums/viewtop ... isappeared. That guy has the same Severity: 3 error that I do.
Here is my BF2Log: And heres my GCW LUA: Also heres the munge log after the munge:

SpartanA259 wrote:I have not done any editing on the map

Those map-related warnings and errors just don't all the sudden happen.

Are you using any animated props whose required animation files are not currently in your world's munged folder? How many textures are you layering over one another on your terrain?

SpartanA259 wrote:Message Severity: 2
C:\Battlefront2\main\Battlefront2\Source\LuaCallbacks_Mission.cpp(3776)
Command Post "cp1" not found

Make sure that your cp is also named "cp1" in ZE.
But I doubt that's the real reason, it's rather caused by the following errors preventing the munger from reading your script correctly:

SpartanA259 wrote:Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\LoadUtil.cpp(1010)
Data in C:\Program Files (x86)\LucasArts\Star Wars Battlefront II\GameData\AddOn\BOG\Data\_lvl_pc\BOG\BOG.lvl is not a binary UCF file.

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\LoadUtil.cpp(829)
Unable to find level chunk BOG_conquest in C:\Program Files (x86)\LucasArts\Star Wars Battlefront II\GameData\AddOn\BOG\Data\_lvl_pc\BOG\BOG.lvl


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

Just reading the munge log... Are you using a custom texture? I think they mustn't be bigger than 4096 x 4096.

@AQT The only thing I added before the cps disappeared was a new handgun model and it worked fine. I dont have any animated objects on the map and in the box on the right side of ZE were you put your textures I have eight of them filled.
@Locutus Yeah I checked its called cp1 and im using one new custom texture. I resized it the the size of the stock Yavin ground texture.

AQT wrote:How many textures are you layering over one another on your terrain?

Did you check?
It's not about how many textures you have defined but rather how often you painted over textures.

Ah I see. I painted over the terrain Six times

If you have errors in your mungelog then you must fix these first. The map is broken and the generated Bfront2.log is useless since the munge was incomplete. There is no need to even play the map until you fix the errors(not warnings).

Backtrack any edits since the last time the map worked, proofread everything for typographical errors and edit script files with a code editor instead of Notepad.

I never got the errors until now. The last edit was when I put the handgun ingame and that was a little over a month ago. I just munged it because I deleted the original map in my addon and had no back up and that was two days ago when I got that error without editing any files. Ill go and look through things though.

Have you tried a manual clean and munge first? It doesn't always help, but its definitely worth doing before trying anything else...from what i saw in the log, it looked to me like the munge hadn't finished.

Yes I did both then got those errors.

SpartanA259 wrote:Ah I see. I painted over the terrain Six times

Have you fixed this or what? Because it's the source of one of your errors.

You always say the last things you did are so and so, but you get these munge errors that say otherwise, which don't lie for the most part. Maybe you should start keeping a journal of the things you do. It might help.

I think I fixed that but I dont know.
Heres the new munge log: I dont mean to sound like im lieing or stupid or anything I just cant remember what I made changes to because I havent worked on the map for awhile.
Here is what I can remeber doing on the map. The map is pretty much made of custom objects. There is only one custom ground texture which is the grass and I was working on a custom texture for the sky dome. I was only working on one era (GCW) and one mode (Conquest) at the time. The only files I ever edited were when I added new weapons and troops to the side, the LUA and the .sky file.
Here is the topic for the map before it crashed.

Mungelog doesn't help at all, there is still something wrong with your level.
Try removing all textures except for one and check whether it still crashes.

Perform a 'clean' then munge again to see if you get any new errors in your mungelog.
If you get errors(not warnings) then fix them.
If you don't understand what the errors mean then post them here.

Munge again, if you get no mungelog errors then you can play the map with the BF2_modtools.exe to generate a Bfront2.log. If you experienced problems with the map then examine the Bfront2.log for errors (usually severity 3 for crashes) and track these back to the source of the problem.
If you don't understand what the errors mean then post them here.

If you can't track the errors back to the source then play the 'process of elimination' game by removing things until your map works again. Perform a 'clean' then munge after removing things. Worse case is recreating the map from scratch which might actually be quicker depending on the progress made.

This is just general troubleshooting.