Uniform scale using Scale 3D manipulator is extremely sensitive #54482

Closed
opened 5 years ago by Rawalanche · 12 comments

System Information
Windows 10, GTX1080Ti

Blender Version
Broken: 2.79 and 2.8
Worked: never

Short description of error
Scaling objects or mesh elements uniformly using a white circle on Scale 3Dmanipulator is extremely sensitive. Blender by design sets scaling sensitivity based on mouse cursor distance from the active pivot point. The problem is that 3D manipulator is always present exactly where the pivot point is, and that the central white circle responsible for uniform scaling is always in the center of the manipulator, in a very close proximity to a pivot point. Therefore, any attempt to use 3D manipulator for uniform scaling of an object or its element will always result in excessively sensitive scaling, as the cursor will always be very close to the pivot point when uniform scale action begins.

A simple, quick fix would be to enforce "precise" mode (what happens when you hold down Shift key) as initial state whenever 3D manipulator uniform scale is triggered.

This issue is also present in Blender 2.8, which already overhauls the 3D manipulator functionality, so it would be appropriate to include this fix as a part of 3D manipulator improvement initiative for 2.8 project.

**System Information** Windows 10, GTX1080Ti **Blender Version** Broken: 2.79 and 2.8 Worked: never **Short description of error** Scaling objects or mesh elements uniformly using a white circle on Scale 3Dmanipulator is extremely sensitive. Blender by design sets scaling sensitivity based on mouse cursor distance from the active pivot point. The problem is that 3D manipulator is always present exactly where the pivot point is, and that the central white circle responsible for uniform scaling is always in the center of the manipulator, in a very close proximity to a pivot point. Therefore, any attempt to use 3D manipulator for uniform scaling of an object or its element will always result in excessively sensitive scaling, as the cursor will always be very close to the pivot point when uniform scale action begins. A simple, quick fix would be to enforce "precise" mode (what happens when you hold down Shift key) as initial state whenever 3D manipulator uniform scale is triggered. This issue is also present in Blender 2.8, which already overhauls the 3D manipulator functionality, so it would be appropriate to include this fix as a part of 3D manipulator improvement initiative for 2.8 project.
Poster

Added subscriber: @Rawalanche

Added subscriber: @Rawalanche
Collaborator

Added subscribers: @JulianEisel, @lichtwerk

Added subscribers: @JulianEisel, @lichtwerk
Collaborator

Guess this wont count as a bug per se (even though this could possibly be improved upon)
@JulianEisel : do you have an idea up your sleeve?

Guess this wont count as a bug per se (even though this could possibly be improved upon) @JulianEisel : do you have an idea up your sleeve?
Poster

Well, the current state is so sensitive that you are literally not able to scale a cube to a desired size (especially when scaling down), because you are limited to a pixel density of your screen. It is so sensitive that moving a mouse cursor just one pixel on a 1920x1200 screen will scale the cube by a quite significant increment. I think that not being able to effectively scale a scene objects using a 3D manipulator fits into a definition of a bug.

Attached video example below:
https://youtu.be/Z162Mb-ST9M

Well, the current state is so sensitive that you are literally not able to scale a cube to a desired size (especially when scaling down), because you are limited to a pixel density of your screen. It is so sensitive that moving a mouse cursor just one pixel on a 1920x1200 screen will scale the cube by a quite significant increment. I think that not being able to effectively scale a scene objects using a 3D manipulator fits into a definition of a bug. Attached video example below: https://youtu.be/Z162Mb-ST9M
JulianEisel was assigned by lichtwerk 5 years ago
Collaborator

Still dont think this is a bug (as this is working as designed), but I feel your pain and leave this open so it doesnt get lost..., assigning @JulianEisel here to have a final word.

Still dont think this is a bug (as this is working as designed), but I feel your pain and leave this open so it doesnt get lost..., assigning @JulianEisel here to have a final word.
Collaborator

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
lichtwerk closed this issue 5 years ago
Collaborator

Just found out that in 2.8 this issue is already adressed (you can click anywhere, not just the circle), see comment in #54661 also.
So I guess this can be closed as "wont fix in 2.79, done in 2.8"

Just found out that in 2.8 this issue is already adressed (you can click anywhere, not just the circle), see comment in #54661 also. So I guess this can be closed as "wont fix in 2.79, done in 2.8"
Poster

In #54482#497399, @lichtwerk wrote:
Just found out that in 2.8 this issue is already adressed (you can click anywhere, not just the circle), see comment in #54661 also.
So I guess this can be closed as "wont fix in 2.79, done in 2.8"

I am honestly not sure about this being a solution. In my custom keymap, dragging anywhere with LMB will trigger box selection, like it does in any other software or OS. If 2.8 reserves dragging primary mouse button anywhere in the viewport for uniform gizmo transform, then that will mean such keyboard mappings won't work anymore, or uniform scaling will stop working when input mapping is customized.

Furthermore, if Blender 2.8 comes with overhaul of input mapping down the road, I'd likely expect that it will be preferable to have box selection on dragging of primary mouse button, which will interfere with this solution.

> In #54482#497399, @lichtwerk wrote: > Just found out that in 2.8 this issue is already adressed (you can click anywhere, not just the circle), see comment in #54661 also. > So I guess this can be closed as "wont fix in 2.79, done in 2.8" I am honestly not sure about this being a solution. In my custom keymap, dragging anywhere with LMB will trigger box selection, like it does in any other software or OS. If 2.8 reserves dragging primary mouse button anywhere in the viewport for uniform gizmo transform, then that will mean such keyboard mappings won't work anymore, or uniform scaling will stop working when input mapping is customized. Furthermore, if Blender 2.8 comes with overhaul of input mapping down the road, I'd likely expect that it will be preferable to have box selection on dragging of primary mouse button, which will interfere with this solution.
Collaborator

@Rawalanche : have a look in #54582, this only comes into play, when you have the scale tool active

@Rawalanche : have a look in #54582, this only comes into play, when you have the scale tool active
Poster

In #54482#497481, @lichtwerk wrote:
@Rawalanche : have a look in #54582, this only comes into play, when you have the scale tool active

I am sorry, but I am still confused. This would mean that to perform selections, I always need to deactivate active transform tool first. This would add one step to do prior every selection user wants to perform after using a transform tool. That is very cumbersome compared to pretty much any other 3D software with manipulators out there.

To clarify:
If i wanted to let's say transform a few objects in the viewport around, either doing uniform scale or screen space translate:

Current state:
1, Select objects
2, Transform
3, Select another set of objects
4, Transform

Proposed state:
1, Select objects
2, Enable transform gizmo
3, Transform
4, Disable transform gizmo
5, Select another set of objects
6, Enable transform gizmo
7, Transform

> In #54482#497481, @lichtwerk wrote: > @Rawalanche : have a look in #54582, this only comes into play, when you have the scale tool active I am sorry, but I am still confused. This would mean that to perform selections, I always need to deactivate active transform tool first. This would add one step to do prior every selection user wants to perform after using a transform tool. That is very cumbersome compared to pretty much any other 3D software with manipulators out there. To clarify: If i wanted to let's say transform a few objects in the viewport around, either doing uniform scale or screen space translate: Current state: 1, Select objects 2, Transform 3, Select another set of objects 4, Transform Proposed state: 1, Select objects 2, Enable transform gizmo 3, Transform 4, Disable transform gizmo 5, Select another set of objects 6, Enable transform gizmo 7, Transform

Added subscriber: @thecooltool

Added subscriber: @thecooltool

Scale speed is dependent on how close you click to the object you want to scale.
I too was having an issue with this until a bit of searching.

Scale speed is dependent on how close you click to the object you want to scale. I too was having an issue with this until a bit of searching.
Sign in to join this conversation.
No Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/ID Management
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
Interest/Python API
Interest/Render & Cycles
Interest/Render Pipeline
Interest/Sculpt, Paint & Texture
Interest/Text Editor
Interest/Translations
Interest/Triaging
Interest/Undo
Interest/USD
Interest/User Interface
Interest/UV Editing
Interest/VFX & Video
Interest/Video Sequencer
Interest/Virtual Reality
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
Module › Animation & Rigging
Module › Core
Module › Development Management
Module › Eevee & Viewport
Module › Grease Pencil
Module › Modeling
Module › Nodes & Physics
Module › Pipeline, Assets & IO
Module › Platforms, Builds, Tests & Devices
Module › Python API
Module › Render & Cycles
Module › Sculpt, Paint & Texture
Module › Triaging
Module › User Interface
Module › VFX & Video
Platform/FreeBSD
Platform/Linux
Platform/macOS
Platform/Windows
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#54482
Loading…
There is no content yet.