Hello all,
I'm new to modding SWBF2 and I have been trying to create my own skin pack for a little while now. I've been using Fierfek's modding tutorial to start and believe that to be very good, but I've encountered a problem. I have edited the .tga files like I was supposed to and edited the .lua to have a "dc:" (without quotes). I'm not making any weapon changes, so I never modified any of the .odf files. After I munge and start the game to load the map, the game crashes when the map is about 50% done loading. My guess is that I've just been negligent and have made a dumb mistake somewhere down the road. Perhaps I missed a step? If anyone can help, thanks- I appreciate it more than you'd think.

P.S. I'm sorry if I created a useless topic, I went through all of the mod tools documentation and the other topics listed, and found nothing can lead me to my mistake(s).

Question #4 - I have the CD version of SWBF2 and I get a binkw32.dll error when trying to launch the BF2_modtools.exe, what's wrong?
Answer - The BF2_modtools.exe is the debug executable, copy it from C:\BF2_ModTools and paste it in the same folder as your BattlefrontII.exe, usually:
C:\Program Files\LucasArts\Star Wars Battlefront II\GameData
you can launch BF2_modtools.exe and play your map then exit or let it crash to generate a BFront2.log located in that same folder.
If you encounter a "Please insert CD 1" dialog or have the DVD or digital download version of SWBF2 use https://dl.dropbox.com/u/38430663/SWBF2 ... _NoDVD.exe modified BF2_modtools.exe

If you "installed" it post your Error Log please

Question #4 - I have the CD version of SWBF2 and I get a binkw32.dll error when trying to launch the BF2_modtools.exe, what's wrong?
Answer - The BF2_modtools.exe is the debug executable, copy it from C:\BF2_ModTools and paste it in the same folder as your BattlefrontII.exe, usually:
C:\Program Files\LucasArts\Star Wars Battlefront II\GameData
you can launch BF2_modtools.exe and play your map then exit or let it crash to generate a BFront2.log located in that same folder.
If you encounter a "Please insert CD 1" dialog or have the DVD or digital download version of SWBF2 use https://dl.dropbox.com/u/38430663/SWBF2 ... _NoDVD.exe modified BF2_modtools.exe

If you "installed" it post your Error Log please

Is that relevant? That seems unrelated to my question, but I suppose I could be wrong...

It's mostly unrelated. He's - in a roundabout way - asking you to post the BFront2.log file generated when you run your mission (using the BF2_modtools.exe game build). That helps assess errors with a mod.

Okay here's the log. Thanks for your time & help!

That's the munge log. You need the error log described in Mav's post.

I'm sorry, I'm lost. Where exactly should I go and what should I show? I'm not sure what other log there would be in my _BUILD folder of my map, without going into another folder. I'm confused and couldn't be more apologetic.

there is a bf2_modtools.exe that came with the mod tools. find that and move it to you game's gamedata folder. run your game with that .exe and replicate the crash. it will generate a Bfront2.log. that contains the info you need. if it doesn't show up in gamedata then it might be in C:\Users\yourusername\AppData\Local\VirtualStore\Program Files (x86)\LucasArts\Star Wars Battlefront II\GameData

no worries, everyone starts somewhere

also, make sure to save without RLE compression when editing tga files

Thanks so much for your help. Unfortunately I won't be able to post until this Saturday, but I wanted to thank you for your help and consideration. I'll try to do so as soon as I can.


EDIT
Ok, thanks again for help and patience. I hope this it.

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\Weapon.cpp(1604)
Weapon base class "com_weap_inf_lightsaber" not found

Severity 3's are usually the cause of crashes. This is most likely it. did you remember to copy the common side from the assets and munge it along with you custom side?

Are you sure you copied the common folder in assets/ sides too to your side folder?

You guys were right- I hadn't copied the common folder in, thanks! It's working fine and I really appreciate your help! I guess I was right, it was just a dumb mistake.