koobas.hobune.stream
Transform tools appear far out from object and do not work.
Working on a project and everything was going smoothly. I imported a 3d asset from the store and added it to the scene. Now every time I select a game object in the scene the transform tools (translate,rotate, and scale) appear far off in the distance. And when I try to select the handles of the transform tool the game object is deselected.
I thought that perhaps the objects were not centered or parented by another object. But even when I create a new game object centered at 0,0,0 that same things happen.
Lastly when I click around an object where I think the transform tools should be some times it will move. I feel that the handles are are just displayed in the wrong place in the scene.
I have tried adjusting the size the 3d icons.
Setting center,pivot,global, and local.
Turning Gizmos on and off.
Selected default, everything, and nothing in the layers.
Changing the layout.
Deleting the 3d asset.
Restarting.
Searching google.
Thank You for any help.
Same happened to me. Haven't imported any object or anything, nor even updated Unity. Started happening today for no apparent reason.
So for some reason now when I select nothing in the layers drop down the Transform tool gizmos appear in the correct place. But when I choose default or any other option it moves back into the distance.
Well I found some what of a work around to the problem. I discovered that if select one of the object with a collider and make sure the collider component is expanded, the Transform tools will appear in the correct place. But as soon as I un-expand the collider component the Transform tools move back far into the distance. Hopefully someone else has a better solution.
Suddenly happened to me too (Unity 5.3.1p1), found no workaround except adding a custom script to the object. As soon as you remove the script, though, the transform tools go haywire again. It seems like a bug, but I'm not sure how it could have popped up without me updating Unity.
Edit: Just downloaded the latest patch release (5.3.1p3) and the bug is still there.
Edit 2: Creating a whole new scene seems to fix the problem, implying there might be something corrupted in the initial scene data?
