Pages: 1 2 [3] 
|
 |
|
 Author
|
Topic: X file export corrupted (Read 4851 times)
|
|
|
|
fragmo
|
I don't think I can fix the problem you're having. I would recommend that you just keep using v1.1.0.
sorry
|
|
|
|
|
Logged
|
|
|
|
|
JMass
|
I don't think I can fix the problem you're having. I would recommend that you just keep using v1.1.0.
sorry
Ok, thanks. |
|
|
|
|
Logged
|
|
|
|
|
fergus
|
I'm not sure if this is related to the problem JMass is having, but I'm working on parsing x-files and when I got to a file that contains two separate frames (a warrior and his weapon) my parser crashed when I was reading MeshMaterialList. I noticed after exporting the file from fragMOTION 1.13 that the number of materials counter equaled the number of globally defined materials (two) when actually the frame only used one and outputted only one material reference. The orignal file had one for the counter. If I disable the global materials both materials are defined in the MeshMaterialList (though only one is used).
Malcolm
|
|
|
|
|
Logged
|
|
|
|
|
LS5
|
I've noticed a bug in the .B3D export, also. This happened in 1.1.5, I have not tested the newest version on this, but when I tried to export to this format, Blitz3D could not find the model. My theory is that FragMotion did not parent the bone structure to the "Skeleton" bone given on export (I tried again, it turns out the Skeleton bone was not being given). I would imagine Making one manually would fix it, but just a tip. Thanks.
I'll try again, it's been a while since this happened.
|
|
|
|
« Last Edit: January 10, 2012, 06:14:44 PM by LS5 »
|
Logged
|
|
|
|
|
Pages: 1 2 [3] 
|
|
|
 |
