Munge really going out of way to ignore this file
Posted: Tue Dec 21, 2010 3:10 am
I have already seen numerous warnings about how you have to make sure the "modified" date on the file is current before you munge. Unfortunately, this does not help. The munge still ignores the file.
Specifics: I recently replaced an old msh file in my side folder with a slightly different one just to see if I liked it. So I replaced the old one with the new one, and now get this: I get the error message stating that the geometry referenced in the odf file can't be found (and naturally the crash that goes along with that). And of course, paying careful attention to the mungelog, I see that the msh file is not being munged, despite the fact that the modify date is current. First off, why in blazes can't the program find the old file? It should still be there, right? Second, why is the munge program ignoring the file despite me even trying to add in extra white space and saving?
So I made a new msh file, renamed it, and changed the odf to reference this one. This also didn't work, as the new msh file was not munged either! I tried a clean and a manual clean (twice) to no avail. This makes zero sense to me. Does anyone have any idea what this absurd munge bug is, and is there any way I can (if not fix) bypass it manually?
EDIT: Fixed. A word to the wise for all beginning modders out there: DO NOT REPLACE A MSH FILE. Instead, just call it something new and tell your odf to reference that new msh. If you replace that msh file, you may end up having to do this:
I backed up my world and common folders, as well as my addme.lua and ONLY the side files I knew I needed. I then deleted my *** folder in both addon and BF2_Modtools, re-built the world, copy-pasted those directories into that world file, and munged. That was the ONLY way I could fix this, cause the manual clean did nothing.
EDIT2: Perhaps this should be stickied, because I've apparently found a super manual clean method. On my honor, the manual clean did not work.
Specifics: I recently replaced an old msh file in my side folder with a slightly different one just to see if I liked it. So I replaced the old one with the new one, and now get this: I get the error message stating that the geometry referenced in the odf file can't be found (and naturally the crash that goes along with that). And of course, paying careful attention to the mungelog, I see that the msh file is not being munged, despite the fact that the modify date is current. First off, why in blazes can't the program find the old file? It should still be there, right? Second, why is the munge program ignoring the file despite me even trying to add in extra white space and saving?
So I made a new msh file, renamed it, and changed the odf to reference this one. This also didn't work, as the new msh file was not munged either! I tried a clean and a manual clean (twice) to no avail. This makes zero sense to me. Does anyone have any idea what this absurd munge bug is, and is there any way I can (if not fix) bypass it manually?
EDIT: Fixed. A word to the wise for all beginning modders out there: DO NOT REPLACE A MSH FILE. Instead, just call it something new and tell your odf to reference that new msh. If you replace that msh file, you may end up having to do this:
I backed up my world and common folders, as well as my addme.lua and ONLY the side files I knew I needed. I then deleted my *** folder in both addon and BF2_Modtools, re-built the world, copy-pasted those directories into that world file, and munged. That was the ONLY way I could fix this, cause the manual clean did nothing.
EDIT2: Perhaps this should be stickied, because I've apparently found a super manual clean method. On my honor, the manual clean did not work.