For some strange reason, when I have made my map, and I load my map ingame, there are no objects in it!? Please help! I have had help from someone who said - "Put all your assets that you used into C:\BF2_ModTools\data_***\Worlds\***. I tried that, and it still didn't work, and instead caused a crash! Help!!!
Also, if I put on any alternate colours it crashes too! Help! I have no custom sides and new to modding, so any advice would be appreciated...

Do not paint the terrain colors with the tools in the "colors" tab in ZE. Use the "terrain" tab instead.

In C:\BF2_ModTools\data_***\Worlds\*** you need to make a few more folders, called odf, msh, (and effects if you want any custom effects, and MUNGED if you want any animated props such as the Rancor). Then in the odf folder put all your odf files, and in the msh folder put all your msh and tga files.

WOW! Replies on Gametoast are QUICK! Thanks for help dude! I'll try it out now.

If you read the Getting Started.doc, it will explain everything you need to begin modding. Further questions about ZE are addressed in the ZeroEditor_guide.doc.

Once you give both those documents a once over, come back with questions (you could even read the other documents, too, that's what's they're there for).

Not to mention this bit of modding gold.

My map keeps crashing and when I loaded it once i could not see any objects on it...

Find, in C:\BF2_ModTools, something called BF2_modtools.exe. Move it to C:\Program Files\LucasArts\Star Wars Battlefront II\GameData and launch it.

Play through your map (or try to, at any rate). Once done, go to C:\Program Files\LucasArts\Star Wars Battlefront II\GameData and look for a file called BFront2.txt. Open it up and search for any Severity 3 errors. Post these on this site, and we can help you.

If you have Vista, BFront2.txt may be located in C:\Users\*username*\AppData\Local\VirtualStore\Program Files\LucasArts\Star Wars Battlefront II\GameData instead.

I found BFront2 before I came on Gametoast. I put it into GameData folder. I will now go onto my game and do it... I hope it's going to work right.
Also, when I munge, there is a error at the end, saying.
PC_MungeLog data:
soundflmunge.exe : Error : Unable to open file ..\gcw\streams\PlayerCommands_vo\AI1COM474.wav - while munging C:\BF2_ModTools\data_RPM\Sound\global\all_unit_vo_quick.stm
soundflmunge.exe : Error : Unable to open file ..\gcw\streams\PlayerCommands_vo\AI1COM474.wav, format may be invalid - while munging C:\BF2_ModTools\data_RPM\Sound\global\all_unit_vo_quick.stm
---
There is lots of other stuff in it, loads of errors, but if I post it all it will be too long a post.
EDIT: I've just edited it, it might have been too long a post anyway


EDIT2
Aargh
It wont stop crashing! Should I restart my maps? I tried going to the BFront thing when I went on the map but I was only on the map for like 5 seconds and then it crashed!!!

This is...

The bf2_modtools.exe is the debugger. It tells you what's wrong with your map through the BFront2.txt file. So if it's crashing, that's ok, because this thing will tell you why.

That being said, it's unreliable if you have any munge errors, like it seems you do.

It seems to be a sound error. I've never had sound errors before. Anyone know if one like this would get you a CTD?

Erm...still no objects can be seen on my map!!!!!!!!!!

Par3210 wrote:Erm...still no objects can be seen on my map!!!!!!!!!!

If you won't cooperate with what we tell you to do, we can't help you. Lets start simple.

Post all of your munge errors.

Those sound errors aren't a problem, he's just trying to munge sound when he doesn't need too.

Oh, so that's the thing.

Oh yeah, when GTers say Munge errors they mean anything you get right after munging, like those sound errors. When they refer to errors form your error log, we're talking about the BFront2.txt file.

So, if you have any more munge errors (errors, mind you; not warnings, warnings we can ignore) then post those munge errors here.

If you have no further munge errors, then you can open up the BFront2.txt and post any Severity 3's or higher.

Fiodis wrote:Oh, so that's the thing.

Oh yeah, when GTers say Munge errors they mean anything you get right after munging, like those sound errors. When they refer to errors form your error log, we're talking about the BFront2.txt file.

So, if you have any more munge errors (errors, mind you; not warnings, warnings we can ignore) then post those munge errors here.

If you have no further munge errors, then you can open up the BFront2.txt and post any Severity 3's or higher.

It is better to post the whole log, sev 3's aren't the only thing that crash a map.

...
I went into game and waited. After 5 seconds the game crashed.
I went and open my BF2log or whatever it was called. Nothing at all was in there. Except:
Opened logfile BFront2.log 2009-06-14 1602

That's all that was there.

?

Par3210 wrote:...
I went into game and waited. After 5 seconds the game crashed.
I went and open my BF2log or whatever it was called. Nothing at all was in there. Except:
Opened logfile BFront2.log 2009-06-14 1602

That's all that was there.

?

you have to run the game through the modtools, not the actual game.

Are you sure it's OK to post all my MungeLog? OK...

EDIT
Ah, but.... I can't get into game. I have the disk in my drive, and I double click on the ModTools icon in my GameData, and it says Insert Disk 1 to continue....

Does THIS mean... I have to get the DVD VERSION!?!


EDIT2
OK i got my debug log to work... its a long one tho so i think i should shorten it



That's the first part of my debug log...

Par3210 wrote:OK i got my debug log to work... its a long one tho so i think i should shorten it

Bad choice. It's long, but so are instruction manuals and you need the whole thing to make sense of it all. (As a side note, the first part is usually the least useful part, what you've posted doesn't even really pertain to your map specifically). Post the whole thing; use "hide" tags to make your post viewable.

And don't doublepost.

OK.. I'm sorry.

DarthRogueKnight wrote:

Fiodis wrote:Oh, so that's the thing.

Oh yeah, when GTers say Munge errors they mean anything you get right after munging, like those sound errors. When they refer to errors form your error log, we're talking about the BFront2.txt file.

So, if you have any more munge errors (errors, mind you; not warnings, warnings we can ignore) then post those munge errors here.

If you have no further munge errors, then you can open up the BFront2.txt and post any Severity 3's or higher.

It is better to post the whole log, sev 3's aren't the only thing that crash a map.

No; but often they are. If he didn't have any, then I'd ask for the others. But eh, it all comes to the same thing: posting the log.

Speaking of that, how about it? Whole debug log, then, in hide tags.

How do I do hide tags? The debug log is as follows...