-= Gametoast.com =-

I have a bit of speculation behind the not updating of the tool. Basically, i was working with my fully functional weapon odf. Not sure what i did, but basically it caused my tool to stop updating. So like always, i went down the list of remedies, but no luck. That's when i tested it on two other mods, which it corrupted their munge as well. It makes me wonder about all of the other munges i did in the past, the ones that wouldn't update. Was it just because of some glitch in the tool, or a corrupted odf or texture?

On a side note, i remember when working with the swbf1 munge, it would create a "program#" in my C drive for every munge, and i never had any problems with updating.

Anyone else have any thoughts on this?

I've had a similiar problme myself. I started up a new map specifically for testing and editing sides, which would later be put into the real maps. I made the new sides, and started eiting them. Later on once i had set the base cis side up i started to go back and edit the common side so changes would be universal for both sides. Basically what the problem is that when i munge the common side, whether i make changes or not it behaves ok in the visualmunge, but the changes are not applied. Anything i change in the cis odfs works but the commons just don't work. Thats my problem, and as you said i myself tried to start a new map, and simply copied the odfs and the problem continued.

Hmm, tried another test. I took the regular clone trooper and switched out his rifle with my new weapon. The match failed to start, sending me back to desktop. So i try to reverse the effect by giving the clone trooper his old rifle back, but it still sends me back to desktop. It's as if the one odf has corrupted the entire munging process.