Page MenuHome

Manipulator lag
Closed, DuplicatePublic

Description

System Information
Operating system: win10
Graphics card: geforce 1070

Blender Version
Broken: 2019-05-31, f87bba0368ea
Worked: 2019-04-17, 'b4625470f79

Short description of error
My friend who uses mostly manipulators showed me that there is noticeable lag of a few pixels before an object starts moving and it impedes precision.
Here is an showcase of the issue (Please enlarge gif to clearly see the issue):

Working (expected behvaiour):

Broken (Manipulator works only after the mouse has been moving a little):

Along with this issue I was told that sometimes blender doesn't detect the click and instead places the 3d curson at the manipulator. This can also be seen in my gif.

Exact steps for others to reproduce the error
WYSIWYG gif, with any new scene.

Details

Type
Bug

Event Timeline

Karlo (kpavicic) updated the task description. (Show Details)
Karlo (kpavicic) updated the task description. (Show Details)
Brecht Van Lommel (brecht) renamed this task from 2.8 | Manipulator lag to Manipulator lag.Jun 2 2019, 2:59 PM

This change needs to be combined with the change of default drag distance value. Current default of 10px will be indeed uncomfortable for most people. 3px feels reasonable.

Well, what makes them feel sluggish atm, is also the fact that it often uses the wrong threshold, which is too large.

See this bug report: T65391

@Ludvik Koutny (rawalanche) The default drag distance *is* already 3px for mouse input, but there's a bug that means it sometimes uses the wrong threshold value, which is why it's currently inconsistent.

@Ludvik Koutny (rawalanche) The default drag distance *is* already 3px for mouse input, but there's a bug that means it sometimes uses the wrong threshold value, which is why it's currently inconsistent.

Good, happy to see it's being tackled.