Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.23f1, 2023.2.16f1, 6000.0.0b12
Votes
4
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
6000.0.0b1
Issue ID
UUM-63803
Regression
No
Serialization of Animator Parameters m_Controller fileID switches between "9100000" and "0" when changing the order of Layers or the Parameters
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/AnimatorController“ Animator Controller with a text editor application
3. Search for “m_Controller“
4. Observe the “m_Controller“ values under the “m_AnimatorParameters“
5. Open the “Assets/AnimatorController“ Animator Controller
6. Change the order of Layers by dragging the “Layer1” Layer under the “Layer2“ Layer in the Animator window
7. Change the order of Layers back by dragging the “Layer1“ Layer above the “Layer2“ Layer in the Animator window
8. Save the project (File > Save)
9. Repeat steps 2, 3, 4
Expected result: The “m_Controller” values for “Parameter1“ and “Parameter2“ are “fileID: 0”
Actual result: The “m_Controller” values for “Parameter1“ and “Parameter2“ are changed to “fileID: 9100000”
Reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Note:
If steps 6 and 7 are done with Parameters instead of Layers, the “m_Controller” values for “Parameter1“ and “Parameter2“ are “fileID: 0”. The “fileID“ seems to change depending on whether the Layers order is changed or the Parameters order is changed.
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 6000.0.0b12):
Changing the order of layers or parameters will now make sure both point to a valid controller, instead of resetting to null in certain case