Broken models aren't broken!!! [message #51485] |
Fri, 29 May 2009 13:15 |
|
JohnDoe
Messages: 3007 Registered: October 2007
|
Retired
|
|
|
Okay, so anyone who has ever toyed with models to any moderate extent knows that they can't do anything with the longsword models, Thunder's sword, and a few other things. I know why, and I have tested and proved this theory.
It's the name of the submesh. It's so damned crazy that such a little thing has had people stumped for so long.
Anything with the terms word, dword, or sword will appear to be borked. This is because these terms are used in data interpretation, so it misinterprets the label and breaks!
The fix is easy too. In FE, before exporting the model, switch over to the appropriate tab, click the appropriate submesh that is labeled as sword, and change the name! Apply changes, then export.
This happens to more than swords because LH devs have found it worthwhile to mislabel submeshes in other models in the graphics.big. The crossbow bolts, for example, are labeled as "mouth" if I remember correctly. So when a model fails to load in something, check the submesh names for any technical terms that might be screwing up the program you're using.
[Updated on: Tue, 16 June 2009 03:33] Report message to a moderator
|
|
|
|
|
Re: Broken models aren't broken!!! [message #52081 is a reply to message #52079] |
Mon, 15 June 2009 20:12 |
|
JohnDoe
Messages: 3007 Registered: October 2007
|
Retired
|
|
|
James Butts wrote on Mon, 15 June 2009 21:35 | ummmmmmmmmmmmmm wtf, I think that's dumb!!!!! and it doesn't make too much sense.....
| Yea it does. If you check out the top of any model, you'll see how it tells whatever program using it how to read the file. So if a data type is mentioned somewhere where it isn't supposed to be, such as sword, dword, word, int, sint, or any symbols like -, +, &, ^, =, *, etc., in such a way that it misinterprets is and doesn't recognize it as part of the name of the mesh, it gets all confuzzled and breaks.
|
|
|
|
|