Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.2
2019.3
2019.3.0b6
2020.1
Issue ID
1205373
Regression
No
Aim Constraint vectors not converted when imported from FBX
How to reproduce:
1. Import attached "mayaUpVector2.fbx" into a project
2. In Animation section of import settings check "Import Constraints"
3. Add imported model to a scene
4. Inspect Aim Constraints "World Up Vector" on object "Axes" of the model
5. Inspect orientation of the model
Expected result: "World Up Vector" is (0,1,0), blue part is pointing along y axis, green along x axis, red along z axis
Actual result: "World Up Vector" is (0,0,1) blue part is pointing along z axis, green along x axis, red along y axis
Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Could not test with: 2017.4 - constraints not supported
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
Resolution Note (2020.1.X):
We have decided to close out this bug as a "Won't Fix".
Because our analytics suggest that aim constraints are a very rarely used feature, and because they aren't necessary to import a model, we believe it is in our users best-interests to focus on higher priority issues.