Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.6.0b17
Issue ID
631788
Regression
No
Gameobjects don't move smoothly
How to reproduce:
1. Open the attached project
2. Open the scene "bug test" (it has a terrain, a cube placed at or near the center of the terrain, and close to its surface)
3. In the hierarchy, double click on the cube so you zoom in on it
4. Select the handles to move the cube
5. Then move it in the x and z axis and there will be a slight snapping effect only noticable when zoomed in on a GameObject as if to position it close to another GameObject.
Comments (3)
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
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
- OS Notification Documentation is missing when following hyperlink in Notifications Settings in Hub
The_Mad_Orc
Sep 16, 2014 18:15
Yeah I just checked and it still does it when I hit the f key once. Though I did just notice that it only does this on large terrains. I have the default terrain which is 2000 * 2000 and a smaller one 500 * 500 and on the smaller one I don't notice the snapping. Also the closer the gameobject is to the center of the terrain the more noticeable the snapping is.
ColdPluto
Sep 16, 2014 00:01
Double clicking an object in inspector or double pressing the F key with an object selected will make the scene camera follow that object so it stays at the center of the screen. Press F once if you only want to zoom in to the object. Does pressing F once still cause that problem?