Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a11
6000.0.37f1
Issue ID
UUM-82500
Regression
No
SerializedReference is not saved when restarting Unity Editor
Reproduction steps:
1. Open the user’s attached project
2. Open the “Assets/DancingInvaders/Prefabs/Ships/EnemyShipActor/EnemyShipActor.prefab”
3. In the Hierarchy, select “StateControlTrack” GameObject, which is a child of “Timelines” GameObject
4. In the Timeline, select “ActiveState”
5. In the Inspector, select any condition under “Transition Setups”
6. Save the Project
7. Repeat steps 1-4
8. In the Inspector, observe the conditions under “Transition Setups”
Expected result: Previously selected condition is saved
Actual result: The selected condition is not saved
Reproducible with: 2021.3.10f1, 2022.1.17f1. 2022.2.0b8. 2023.1.0a11
Couldn't test with: 2020.3.39f1 (couldn’t downgrade because C# 9.0 and above is not supported)
Reproducible on: Windows 11 Pro 21H2
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.