Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a14
2019.1.0b2
2019.2.0a1
Issue ID
1123956
Regression
Yes
Maya Model's Rig Configuration breaks after upgrading project from 2018.3 to 2019.1 or 2019.2
How to reproduce:
1. Open the attached "cyber18.zip" project
2. Click on the Models > Hoodie > "RigHoodie.ma" in the Project WIndow
3. Observe Import Settings > Rig > Import Messages in the Inspector
4. Open the Import Settings > Rig > Configuration
5. Observe the Scene View
Expected behavior: The Rig does not change after upgrading a project
Actual behavior: The Rig Configuration brakes, bone positions are altered
Reproducible with: 2019.1.0a14, 2019.1.0b4, 2019.2.0a6
Not reproducible with: 2018.3.7f1, 2019.1.0a13
Note: .fbx files are not affected. The behavior is also reproducible when Importing .ma files from project saved in 2018.3 manually. The workaround would be to set Import Settings > Animation > "None" (or any other) and then set it back to "Humanoid".
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.2.X):
Unfortunately, we won't be able to solve this issue. The problem is that the avatar scale value was not saved before 2019.1. Therefore when changing the importer scale factor, the importer cannot take the previous scale value into account and assumes the previous scale is equal to the current scale factor. The only way to solve this situation is to reset the avatar ( by setting rig type to 'none' then back to 'humanoid').
Note that the issue only occurs when upgrading to 2019.1 and does not occur when upgrading from 2019.1 to a later version.