Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.1.0b6
Issue ID
695637
Regression
Yes
MotionBuilder 2016 binary FBX import Errors
MotionBuilder 2016 binary FBX import Errors
1. What happened
MotionBuilder 2015 FBX files import properly, both in binary and ascii
MotionBuilder 2016 Ascii FBX files import properly
MotionBuilder 2016 Binary FBX files do not import and gives an error...
ImportFBX Errors:
Couldn't import file /Users/eakes/Unity/FBXimport/Assets/Gremlin_2016_binary.fbx.
File is corrupted (or invalid)
Attached project contains the above 3 file examples.
2. How we can reproduce it using the example you attached
Open the project
Look at the error in the Consol for the Gremlin_2016_binary fbx file
The other two files imported properly
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
robstardotstar
Jan 20, 2016 13:34
This has not been fixed for Mac. Works OK on Windows.
robstardotstar
Jan 20, 2016 13:22
This is broken again in Unity 5.3.1f1
bruno-martelli
Sep 12, 2015 19:44
worked for me
00christian00
Aug 07, 2015 07:34
Motionbuilder 2016 use a new 64 bit format, you should use the export fbx under "Python tools" to use the old format.