Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2021.2.0a17
2021.2.0b4
2022.1
Issue ID
1351800
Regression
Yes
Increment Snapping lock gets disabled when the X value is changed
Steps to reproduce:
1. Open the attached project "SnappingIssue.zip"
2. Open Scenes/SampleScene in the Project window
3. Open the Increment Snapping menu on the Scene window
4. Lock the Move values to X axis
5. Hold Command/Control key and move the Cube on any axis
6. Open the Increment Snapping menu on the Scene window
7. Change the Move value on the X to 2
8. Hold Command/Control key and move the Cube on any axis
9. Open the Increment Snapping menu on the Scene window
10. Observe the Move values and lock state
Expected result: The Move values are the same on every axis and the lock is still enabled
Actual result: The Move values are not the same on every axis and the lock is disabled
Reproducible with: 2021.2.0a17, 2021.2.0b5, 2022.1.0a3
Not reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.16f1, 2021.2.0a16
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
- Memory leaks occur when Shader with more than 128 keywords is compiled
- Player built for Windows silently crashes when UI Prefab is instantiated and Render Feature "Render Objects" is active in PC_Renderer Asset
- Crash on CollectUsedSceneObjects when making any modifications and saving in a Scene with a specific GameObject Component enabled
- VFX Graph Properties Transform has a click animation when clicked on the “Transform” text but the drop down does not open
- "Cascade Shadow atlasing has failed" errors are spammed when two Directional Lights with the Shadow Map are enabled and there is a 3D GameObject in the scene
Resolution Note (fix version 2021.2):
https://github.cds.internal.unity3d.com/unity/unity/pull/5165
Resolution Note (fix version 2021.2):
https://ono.unity3d.com/unity/unity/pull-request/134389