Search Issue Tracker
Won't Fix
Won't Fix in 2019.4.X
Votes
0
Found in
2019.4.34f1
Issue ID
UUM-1177
Regression
No
Handles.RotationHandle and Handles.PositionHandle trigger prefab override when updating current values with the same values
Steps to reproduce:
1. Open the attached project
2. Open "empty scene"
3. Notice that the "Shotgun" prefab already has an override (if it doesn't, just hover over scene view)
4. Select the "Shotgun" prefab instance
5. In the Inspector window click on Overrides dropdown
Expected result: No overrides
Actual result: Prefab child GO has updated rotation
Reproducible with: 2019.4.34f1, 2020.3.28f1, 2021.2.10f1, 2022.1.0b6, 2022.2.0a4
Notes:
- The updated rotation comes from the randomReference.cs script which just calls Handles.Rotation in OnDrawGizmos(). This shouldn't alter rotation as the call returns the same value as the current one
- Tried reproducing with built in GameObjects, but couldn't
- More info and an alternate scenario can be found in the edits
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
This is regrettably the expected behavior currently. Due to the way we serialize floating point values in Unity there are minor floating point precision problems for certain situations and this is one of these cases.
In this situation one can solve the problem by changing the rotation in the editor and the rotation should then no longer be marked as an override.
Resolution Note (2019.4.X):
This is regrettably the expected behavior currently. Due to the way we serialize floating point values in Unity there are minor floating point precision problems for certain situations and this is one of these cases.
In this situation one can solve the problem by changing the rotation in the editor and the rotation should then no longer be marked as an override.