Page MenuHome

Blender 2.80 strange behaviour of the move and rotate tool
Closed, ArchivedPublic

Description

System Information
Operating system: Windows 10
Graphics card: see system-info.txt attached

Blender Version
Broken:
2.80, ff108aac632, blender2.8, 2018-12-11 23:04
Worked: last three I used past week had the same problem. I just started to test it about a week ago

Short description of error

Exact steps for others to reproduce the error
I had on default start up as well as my own file.


Activating an object and trying to move or rotate it does not work as expected. Clicking on any of the arrows and drag move produces a move in 2 axis instead of locking to one axis move. See attached video

Is this a bug or a setting issue? I was searching for it but could not find any related info. The videos I found showed the move and rotate tool work correctly on the 2.80 but not on mine. Very frustrating because I cannot move an object quickly and precisely.

Kind regards,
Andrew

Event Timeline

blender-2.80-16fc62e15f0-win64
I can't reproduce this issue.
Maybe because of your custom mouse thingy?

Try to go File > Load Factory Defaults and see if you still have the issue.

Also make sure you aren't holding Shift, which locks to the opposite axes.

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 30.Dec 12 2018, 2:15 PM

I can't reproduce this either...

It seems like you are not able to select the gizmo handels. They should highlight when you hover over them to indicate which one you will get when you click. However in the video, none of them changes color when you hover over them.
Are you able to select verts/edges etc with out a problem in edit mode?

Andrew Sprok (sprad001) changed the task status from Unknown Status to Resolved.EditedDec 12 2018, 10:22 PM
Andrew Sprok (sprad001) claimed this task.

I did the Load Factory Defaults suggested by billreynish and that solved the problem. Thank you but not sure why this happened in the first place. I do not recall changing anything. Interestingly every time I downloaded a new daily build this problem was carried over.
Thanks again.

Andrew Sprok (sprad001) changed the task status from Resolved to Unknown Status.Dec 13 2018, 2:10 AM

Unfortunately with current files that had that problem it still exist. It works only if I start from scratch with the suggested Factory Defaults.
What controls this behavior?
I work on files that I created in V2.79 and is about 2GB in size so no way I can recreate it in 2.80. I put a lot of work in it already.

Does it work if you untick "Load UI" ?

If you can post your blend file, probably with all the objects deleted, it should be possible to test and confirm this bug.

Philipp Oeser (lichtwerk) changed the task status from Unknown Status to Unknown Status.Jan 15 2019, 11:41 AM

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.