UX issue - Unit transformations do not follow default scale #40312

Closed
opened 2014-05-22 11:55:54 +02:00 by Vlad Mafteiu Scai · 7 comments

System Information
win 8 64, 2x msi lightning 780

Blender Version
Broken: (example: 2.70.5 ba1acec, see splash screen)
Worked: (optional)

This is a serious UX issue which causes confusion among new users since what they expect is not what they get.

Exact steps for others to reproduce the error

  1. Make sure default in Properties panel/Scene units are set to a scale of 1 which is 1 meter(could be any other but easier to see it this way)
  2. Now set it to 0.01 which make the default unit in cm
  3. Make a new circle(or cube or whatever). Press N in viewport, go to transform section and for dimension, type: 1. Now since the default scene scale is 0.01 which is in cm, typing 1 should set the dimmension to 1 cm, but now is still 1 meter forcing the user to manually convert each time and try to guess the result they will get.

So how this should be working properly is whatever is default scale in scene should also apply to transformations.

Having a dropdown as well with some default units like km,m,cm,mm etc like in other apps will make things even more clear.

**System Information** win 8 64, 2x msi lightning 780 **Blender Version** Broken: (example: 2.70.5 ba1acec, see splash screen) Worked: (optional) **This is a serious UX issue which causes confusion among new users since what they expect is not what they get.** **Exact steps for others to reproduce the error** 1. Make sure default in Properties panel/Scene units are set to a scale of 1 which is 1 meter(could be any other but easier to see it this way) 2. Now set it to 0.01 which make the default unit in cm 3. Make a new circle(or cube or whatever). Press N in viewport, go to transform section and for dimension, type: 1. Now since the default scene scale is 0.01 which is in cm, typing 1 should set the dimmension to 1 cm, but now is still 1 meter forcing the user to manually convert each time and try to guess the result they will get. So how this should be working properly is whatever is default scale in scene should also apply to transformations. Having a dropdown as well with some default units like km,m,cm,mm etc like in other apps will make things even more clear.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @00Ghz

Added subscriber: @00Ghz

Added subscriber: @willi-2

Added subscriber: @willi-2

I think this is a misunderstanding. What if you enter 0.3 as the scale? It's not meant to be the "default unit if you enter no unit in an edit box". It's just the scale helping with creating smaller (or bigger) models.

I think this is a misunderstanding. What if you enter 0.3 as the scale? It's not meant to be the "default unit if you enter no unit in an edit box". It's just the scale helping with creating smaller (or bigger) models.

If you enter 0.3 it will be 30 cm I think ;)

So when typing some value for transforms then you get 30 cm increments for 1 unit.

And that's why I said a proper dropdown for standard units will help.

If you enter 0.3 it will be 30 cm I think ;) So when typing some value for transforms then you get 30 cm increments for 1 unit. And that's why I said a proper dropdown for standard units will help.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sergey Sharybin self-assigned this 2014-05-23 12:08:27 +02:00

This is more like a design discussion. The thing is that units doesn't follow units, they're decoupled from each others. Improvements are possible for sure, but it's being handled outside of the bug tracker. Made sure the issue is listed in our TODO list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/UserInterface#Properties_Editor

Thanks for the report, but closing it now.

This is more like a design discussion. The thing is that units doesn't follow units, they're decoupled from each others. Improvements are possible for sure, but it's being handled outside of the bug tracker. Made sure the issue is listed in our TODO list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/UserInterface#Properties_Editor Thanks for the report, but closing it now.
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#40312
No description provided.