-= Gametoast.com =-

Hello Community,

I recently worked on my Clone Wars Era Mod again, and I approached a weird error.
When I edit something in my sides folder and munge it, during the munge a window pops up saying
"LevelPack.exe" stopped working, searching for solutions
After a while it stopped searching and then I have to close the popup window. The munge process finishes then.
When I look into my game the changes on the sides don't show up.

I never had that problem before and I didn't change anything on any munge.bat.
I'm running windows 10 and have all the patches/vistamugnefix/extraweapon-code installed/added.
I always executed the munge.exe with no compatibility patches. But when I executed it with XP Service Pack 2/3 the error still resisted.
All earlier munges worked fine. I also get this error now: I didn't change anything on Captain Fordo, I just did a total clean.
I also double checked all .odf and .req files of Fordo, but I couldn't see anything wrong.
The .lvl file of Captain Fordo is the only .lvl file in REP\munged\pc\ that windows recommends me to open with notepad.
here's the content: there's nothing more.
I hope somebody can help me since I need to munge properly again.
Thank you in advance and sorry for the bad english

-The66Order66

You should check all the req files carefully. Some times I forget an { or an } somewhere and it goes nuts with those kinds of errors.

I double checked every req, lua, odf and even msh file, but they're all correct. I don't know what else to do.

EDIT
Ok I found out now that the "Levelpack.exe stopped running" thing comes from the rep_inf_captain_fordo.req file.
Here's captain fordos req file: I double-checked every other custom made .req file and there's nothing wrong.
I really don't know what to do anymore.

I also found this on the internet: http://swbf-custom.forumactif.com/t185- ... ed-working
But there is no solution...
If it helps, here's my MungeLog (it's in german though): Please could somebody go over this and help me.

Perform a Clean then munge with only Common ticked, if you see no errors go ahead and munge only the fordo side. If you see errors there, you just narrowed it down to that side, at this point you could rebuild the side from scratch or try to debug the current one and undo one change at a time to see where the source of this error is coming from. If this isn't a top secret side project you could upload the side files and we'll take a look.

It would take far too long to rebuild all since I implemented it all in the rep side that has already 493 MB now...
The thing with the full Clean is a good idea though I already munged without any side ticket and got no error.
So the error has to come from the custom side. Thanks for the help so far.

EDIT: I solved the problem now!
It was caused by a weapon thats ordanace reference was the same as the weapon itself.