Code: Select all
Message Severity: 3
.\Source\EntityGeometry.cpp(619)
Entity "sea_inf_seanthedestroyer" missing geometry "ewk_inf"A Nonsensical Error [Solved]
Moderator: Moderators
-
bokkenblader56
- Private First Class
- Posts: 85
- Joined: Mon Aug 04, 2008 7:20 pm
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
- Location: South Carolina
- Contact:
A Nonsensical Error [Solved]
I was messing around with adding cloth to units. Just so you all know, I did not modify the original MSH file. After I MUNGED the side and tried to run my map, it closed out with the following error in BFront2.log:
I quickly replaced the MSH file I had just modified with the original from the assets side and MUNGED again. No joy. I can positively state that the MSH file is in there. I've tried moving it to msh\PC and back again, and even having it in both folders. Still no luck. Any help is appreciated.
-
FragMe!
- Gametoast Staff
- Posts: 2244
- Joined: Sat May 13, 2006 12:34 am
- Projects :: Not sure keep changing my mind.
- xbox live or psn: No gamertag set
- Location: Origin name GT_FragMe
- Contact:
Re: A Nonsensical Error
If you replace a changed msh with an original you must do a clean and remunge, VM checks date/time stamps and only munges newer stuff. So since an orignal msh has an earlier creation date than does a modified one it is ignored.
-
bokkenblader56
- Private First Class
- Posts: 85
- Joined: Mon Aug 04, 2008 7:20 pm
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
- Location: South Carolina
- Contact:
Re: A Nonsensical Error
Yep, that worked; thanks. I forgot the rule about always trying a manual clean before asking for help 
-
RepSharpshooter
- Gametoast Staff
- Posts: 1351
- Joined: Tue Jul 10, 2007 4:10 pm
Re: A Nonsensical Error [Solved]
An alternative to cleaning is opening the msh file in a hex editor, then just pressing save. This will update the date modified to the present time, so it will be munged. This will save you the extra time of cleaning and remunging everything else.
Or if you want to be crafty, you can delete the .model file (located in _BUILD/sides/munged/pc) associated with the .msh file (they have the same name). Deleting the .model file will make the munger go and munge the msh again.
Or if you want to be crafty, you can delete the .model file (located in _BUILD/sides/munged/pc) associated with the .msh file (they have the same name). Deleting the .model file will make the munger go and munge the msh again.