Industry Compatible Mode for Scale (unusable) #63655

Closed
opened 2019-04-16 10:48:23 +02:00 by Alex · 12 comments

System Information
Operating system: Windows 10
Graphics card:

Blender Version
Broken: (example: 2.80, edbf15d3c0, master, 2018-11-28, as found on the splash screen)

The new Industry compatible Keymap is great! Everything is very intuitive. But the current implementation of the scale operation is completely unusable. It feels like it was meant to behave similar to Maya but the process of scaling remained Blender-like which means that the closer the mouse cursor is to the center of the object, the more sensitive the scaling is. Which in case of the current implementation means that when you want to scale the object uniformly, you click right in its center of it and the scaling is thus so rapid and sensitive that it is impossible to use. It should not react to the proximity of the cursor to the center of the object in the Industry Mode.

The direction in which the input is developed is right but it needs to be tweaked. For example, box-select should not be disabled when you use move/rotate/scale tools. Now you have to press Q every single time you need to select a few objects after you've done rotating or scaling them. It's like the move back to using the old B-key for box-selecting things every time...

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Windows 10 Graphics card: **Blender Version** Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) The new Industry compatible Keymap is great! Everything is very intuitive. But the current implementation of the **scale operation** is completely unusable. It feels like it was meant to behave similar to Maya but the process of scaling remained Blender-like which means that the closer the mouse cursor is to the center of the object, the more sensitive the scaling is. Which in case of the current implementation means that when you want to scale the object uniformly, you click right in its center of it and the scaling is thus so rapid and sensitive that it is impossible to use. **It should not react to the proximity of the cursor to the center of the object in the Industry Mode**. The direction in which the input is developed is right but it needs to be tweaked. For example, **box-select should not be disabled** when you use move/rotate/scale tools. Now you have to press Q every single time you need to select a few objects after you've done rotating or scaling them. It's like the move back to using the old B-key for box-selecting things every time... **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).
Author

Added subscriber: @AlexPetrov

Added subscriber: @AlexPetrov

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
William Reynish self-assigned this 2019-04-16 11:16:53 +02:00

Thanks for the feedback, but it's not a bug.

The scale issue I don't think can be changed by the keymap. Blender's way also has some nice benefits, in that you can adjust the precision of the operation based on where you start the scale operation from.

Box selecting while the active tools are enabled I agree would be nice to support, at least in addition to the current way. The trouble is that the other developers did not agree to add this capability to the active tools. I might be able to work around it by using left click for box selection and middle drag to activate the tool, but that only really works for tools that have gizmos, so it's not a very nice all-round solution. We cannot use this for things like Knife, Inset or Bevel, so it would introduce inconsistency.

Thanks for the feedback, but it's not a bug. # The scale issue I don't think can be changed by the keymap. Blender's way also has some nice benefits, in that you can adjust the precision of the operation based on where you start the scale operation from. # Box selecting while the active tools are enabled I agree would be nice to support, at least in addition to the current way. The trouble is that the other developers did not agree to add this capability to the active tools. I might be able to work around it by using left click for box selection and middle drag to activate the tool, but that only really works for tools that have gizmos, so it's not a very nice all-round solution. We cannot use this for things like Knife, Inset or Bevel, so it would introduce inconsistency.

Added subscriber: @brecht

Added subscriber: @brecht

Box selecting while the active tools are enabled I agree would be nice to support, at least in addition to the current way. The trouble is that the other developers did not agree to add this capability to the active tools. I might be able to work around it by using left click for box selection and middle drag to activate the tool, but that only really works for tools that have gizmos, so it's not a very nice all-round solution. We cannot use this for things like Knife, Inset or Bevel, so it would introduce inconsistency.

I don't remember this particular discussion, but I don't see a fundamental reason why it should not be done. This could be added to the left-click select tweaks tasks, at least to make it possible to configure setups like this. It's related to allowing to selected items behind a gizmo.

> Box selecting while the active tools are enabled I agree would be nice to support, at least in addition to the current way. The trouble is that the other developers did not agree to add this capability to the active tools. I might be able to work around it by using left click for box selection and middle drag to activate the tool, but that only really works for tools that have gizmos, so it's not a very nice all-round solution. We cannot use this for things like Knife, Inset or Bevel, so it would introduce inconsistency. I don't remember this particular discussion, but I don't see a fundamental reason why it should not be done. This could be added to the left-click select tweaks tasks, at least to make it possible to configure setups like this. It's related to allowing to selected items behind a gizmo.

@brecht: Ok, great, I will do that. It was my impression that adding box select to the Drag Action was not a way we wanted to go?

But if it is, what is then the point of the persistent gizmo popover?

Anyway, I will add it to the left click task if it's not already there.

@brecht: Ok, great, I will do that. It was my impression that adding box select to the Drag Action was not a way we wanted to go? But if it is, what is then the point of the persistent gizmo popover? Anyway, I will add it to the left click task if it's not already there.

I would not expect it to be a specific drag action, just an operator that is always on like click select. And then it's up to the active tools to define if they consume all drag events, or only when over the gizmo.

I would not expect it to be a specific drag action, just an operator that is always on like click select. And then it's up to the active tools to define if they consume all drag events, or only when over the gizmo.

@brecht That is already possible to do in the keymap afaik - it's relatively easy to set up.

The trouble is that:

  • It only works for tools that have gizmos. If there is no gizmo, then there is then no way to actually use the tool. Box select could be set up for the gizmo tools only, but what if you switch to the Inset tool, for example? Then you suddenly cannot box select.
  • The current way is actually rather nice sometimes, esp for things like scaling where you don't need to drag from the little fiddly circle, but you can drag from anywhere on the screen.
@brecht That is already possible to do in the keymap afaik - it's relatively easy to set up. The trouble is that: - It only works for tools that have gizmos. If there is no gizmo, then there is then no way to actually use the tool. Box select could be set up for the gizmo tools only, but what if you switch to the Inset tool, for example? Then you suddenly cannot box select. - The current way is actually rather nice sometimes, esp for things like scaling where you don't need to drag from the little fiddly circle, but you can drag from anywhere on the screen.
Author

Thanks for such a quick response, guys!

My bad, I didn't try to scale the object uniformly outside of it (far from the center), I thought it's gonna work only from the center like it is in Maya etc. But as far as box-selecting while using move/rotate/scale tools is still desirable then you have to decide whether:

  1. move/rotate/scale tools can be operated by click-draging outside the object (which makes sense for scaling, and very little sense for moving and rotating) and no simultaneous box-select possible, which is not cool

  2. move/rotate/scale tools operate only by interacting with their gizmos (Maya etc) and left click-drag outside the object can be used for simulteneous box-selecting. Which is COOL. But in this case, the scale issue comes again which would not need the proximity sensitivity.

Thanks for such a quick response, guys! My bad, I didn't try to scale the object uniformly outside of it (far from the center), I thought it's gonna work only from the center like it is in Maya etc. But as far as box-selecting while using move/rotate/scale tools is still desirable then you have to decide whether: 1) move/rotate/scale tools can be operated by click-draging outside the object (which makes sense for scaling, and very little sense for moving and rotating) and no simultaneous box-select possible, which is not cool 2) move/rotate/scale tools operate only by interacting with their gizmos (Maya etc) and left click-drag outside the object can be used for simulteneous box-selecting. Which is COOL. But in this case, the scale issue comes again which would not need the proximity sensitivity.

I'm not personally arguing that select box is better than drag anywhere for transform tools. There are definitely pros and cons to this, not having to put your mouse in a specific location for transform is a feature that I really like in Blender. Just if we want to support it I think it can fit fine in the current system.

Mainly what I think would be nice is if there was an optional tweak mode for tools, where if you drag on an item it immediately selects it and starts the tool. And if we do that, then some more control over the drag action can fit in too. You could have an enum with the following choices:

  • Transform: drag anywhere to transform
  • Tweak: drag on item to immediately select and transform it
  • Select: fall through to selection operators outside the active tool (which could include box select)

I don't consider this high priority, but to me it seems like a good fit to extend the existing design in the future.

I'm not personally arguing that select box is better than drag anywhere for transform tools. There are definitely pros and cons to this, not having to put your mouse in a specific location for transform is a feature that I really like in Blender. Just if we want to support it I think it can fit fine in the current system. Mainly what I think would be nice is if there was an optional tweak mode for tools, where if you drag on an item it immediately selects it and starts the tool. And if we do that, then some more control over the drag action can fit in too. You could have an enum with the following choices: * Transform: drag anywhere to transform * Tweak: drag on item to immediately select and transform it * Select: fall through to selection operators outside the active tool (which could include box select) I don't consider this high priority, but to me it seems like a good fit to extend the existing design in the future.

@brecht yes I agree that sounds like a really nice improvement that could be added.

@brecht yes I agree that sounds like a really nice improvement that could be added.
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#63655
No description provided.