Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
1
Found in
6000.0.0b14
Issue ID
UUM-69482
Regression
No
[SerializedObject] Undo does not update objectVersion or hasMultipleDifferentValues when changed values is the same as main asset value.
Reproduction steps:
1. Open the attached "ReproProj" project
2. Open the Test Runner ("Window" -> "General" -> "Test Runner")
3. Go to PlayMode tests and click Run All
4. Observe the results
Expected results: Both tests pass
Actual results: Only the second test passes
Reproducible with: 2021.3.37f1, 2022.3.25f1, 2023.2.19f1, 6000.3.0b15
Reproducible on: Windows 11 Pro, macOS 13.6.4 (M1)
Not reproducible on: No other environments tested
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
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
- Meshes created via InstantiateAsync render at the spawn position when GPU Resident Drawer is enabled
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.
Resolution Note (6000.0.X):
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.