Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0b4
Issue ID
994822
Regression
No
[FBX] Position Constraint is not converted correctly when exporting FBX from Maya
To reproduce:
1. Open user's project
2. Find game object joint3 in Hierarchy window
3. In Inspector window, expand Constraint settings
4. Observe Position Offset fields
Expected: constraint parameters are imported correctly (same values as in Maya)
Actual: constraint parameters are imported with 10^-2 difference (value not converted correctly)
Reproduced in: 2017.2.1p3, 2017.3.0p4, 2018.1.0b6
Note: check user's attached pictures for comparison between Maya and Unity constraint values
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
Add comment