Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4
2019.2
2019.3
2019.3.0b6
2020.1
Issue ID
1205357
Regression
No
Aim Constraint Rotation Offset has incorrect values when imported from FBX
How to reproduce:
1. Open scene "AimOffset" from "FBXAimTests.zip"
2. Open "mayaAxesTestXYZ.fbx" in Maya
3. Open Maya Application Preferences and set "World Coordinate system" to 'Y'
4. Visually compare Maya view with Unity scene objects that have names starting with "y_"
5. Set "World Coordinate system" to 'Z' and compare with objects starting with "z_"
Expected result: Model orientations should match in all cases
Actual result: Model orientations do not fully match in any of the cases
Reproducible with: 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
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
This is a duplicate of issue #1205373