Units Feet and Inches #49960

Closed
opened 2016-11-08 01:12:16 +01:00 by Aaron Smithey · 17 comments

Blender 2.78a x64, windows 7 pro, x64, gtx760

  1. Open Blender go to scene tab in properties panel select feet from units preset tab.

  2. Click default cube go to edit mode.

  3. on the (n) panel under mesh display check the length check box to enable.

  4. Move a vert 1 in the Z direction notice the length, it shows 2.305 ft not 3ft.

Do that same with inches and you will see that it is not correct as well.

Aaron

Blender 2.78a x64, windows 7 pro, x64, gtx760 1. Open Blender go to scene tab in properties panel select feet from units preset tab. 2. Click default cube go to edit mode. 3. on the (n) panel under mesh display check the length check box to enable. 4. Move a vert 1 in the Z direction notice the length, it shows 2.305 ft not 3ft. Do that same with inches and you will see that it is not correct as well. Aaron
Aaron Smithey self-assigned this 2016-11-08 01:12:17 +01:00
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @AaronSmithey

Added subscriber: @AaronSmithey

Added subscriber: @Sergey

Added subscriber: @Sergey
Aaron Smithey was unassigned by Sergey Sharybin 2016-11-08 09:55:00 +01:00

@AaronSmithey, please do not assign reports to yourself unless you want to fix the issue :)

The reason of the issue here is that "feet" preset will use scene scale set to 0.3048. When you type 1 during transform it gets scaled by the scene scale. IMO, the whole unit system and unit presets is to be reconsidered.

@AaronSmithey, please do not assign reports to yourself unless you want to fix the issue :) The reason of the issue here is that "feet" preset will use scene scale set to `0.3048`. When you type `1` during transform it gets scaled by the scene scale. IMO, the whole unit system and unit presets is to be reconsidered.

Added subscriber: @AnthonyEdlin

Added subscriber: @AnthonyEdlin

I can confirm this. It seems blender does not take into account Unit Scale in some transform ops.

Of note, when I type Z and 1 it doesn't work.
Snapping a vertex up 1 unit with mouse works.
When I type Z then "=" and type "1ft" it works.

version: 2.78 (sub 1), branch: master, commit date: 2016-11-07 13:47, hash: e74e622, type: Debug
build date: 2016-11-07, 10:25:21
platform: Linux

I can confirm this. It seems blender does not take into account Unit Scale in some transform ops. Of note, when I type Z and 1 it doesn't work. Snapping a vertex up 1 unit with mouse works. When I type Z then "=" and type "1ft" it works. version: 2.78 (sub 1), branch: master, commit date: 2016-11-07 13:47, hash: e74e622, type: Debug build date: 2016-11-07, 10:25:21 platform: Linux
Author

It just seems like unit scale should always be 1, for any unit of measure, and any unit conversion should just be behind the scenes so to speak. So when I am in inches, typing 1 would move and element 1 inch. When in feet, typing 1 should move an element 1 foot.

Thanks for the confirmation.

Maybe someday the USA will convert to metrics but until then, all my client here use Imperial units. I am glad Blender offers imperial units.

Aaron

It just seems like unit scale should always be 1, for any unit of measure, and any unit conversion should just be behind the scenes so to speak. So when I am in inches, typing 1 would move and element 1 inch. When in feet, typing 1 should move an element 1 foot. Thanks for the confirmation. Maybe someday the USA will convert to metrics but until then, all my client here use Imperial units. I am glad Blender offers imperial units. Aaron

Added subscriber: @mont29

Added subscriber: @mont29
Bastien Montagne self-assigned this 2016-11-13 18:09:11 +01:00

Whole unit system may need a rework, but this is a plain stupid bug, still not sure exactly what’s wrong, but the 'typing value' handles unit stuff badly here (like applying twice the unit conversion factor or something).

Will check.

Whole unit system may need a rework, but this is a plain stupid bug, still not sure exactly what’s wrong, but the 'typing value' handles unit stuff badly here (like applying twice the unit conversion factor or something). Will check.

Added subscriber: @XenWildman

Added subscriber: @XenWildman

I found that if you have your scene set to inches, tap E,X,1 it extrudes on X axis by a fraction of an inch.

Instead, if you have your units set to inches and just under that, set Length to metric. Now you tap E,X,1 and it will extrude by the correct amount and display 2.54cm.

Set the Length back to imperial to verify that it indeed extruded by an inch.

I don't think there is anything wrong with the unit system, just the way it is being displayed/handled.

I found that if you have your scene set to inches, tap E,X,1 it extrudes on X axis by a fraction of an inch. Instead, if you have your units set to inches and just under that, set Length to metric. Now you tap E,X,1 and it will extrude by the correct amount and display 2.54cm. Set the Length back to imperial to verify that it indeed extruded by an inch. I don't think there is anything wrong with the unit system, just the way it is being displayed/handled.

Also getting good readouts from choosing Meters as the unit preset and Length set to imperial, Unit Scale 1 for feet and 0.0833 for inches.

Also getting good readouts from choosing Meters as the unit preset and Length set to imperial, Unit Scale 1 for feet and 0.0833 for inches.

Added subscriber: @Hector-Castillo

Added subscriber: @Hector-Castillo

I'm using v2.79b and this issue is still there. After an hour of hair pulling i realized this peculiar behavior (bug).

I'm using v2.79b and this issue is still there. After an hour of hair pulling i realized this peculiar behavior (bug).

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This should be resolved with the new unit settings in 2.8.

This should be resolved with the new unit settings in 2.8.
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
7 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#49960
No description provided.