Log In
New Account
Home My Page Projects Blender 2.x BF release
Summary Activity Tracker SCM Files

Blender 2.6 Bug Tracker: Browse

[#25170] The 3d view properties panel median values use Blender units when set to use imperial.

Date:
2010-12-10 20:07
Priority:
3
State:
Closed
Submitted by:
Ian Starrie (xcausex)
Assigned to:
Campbell Barton (campbellbarton)
Category:
Mesh Modeling
Status:
Fixed / Closed
Relates to:
Duplicates:
Patches:
 
Summary:
The 3d view properties panel median values use Blender units when set to use imperial.
Detailed description
Steps:
1) In the properties window, go to the scene tab and choose Imperial from the units section.
2) Create a new mesh, or use the default cube, tab into edit mode and select any mesh component.
3) Hit N on your keyboard to pull up the properties panel.
4) At this point you should notice that x y & z median values in the Transform section of the properties panel are using the default Blender units and don't recognize the addition of Imperial specifiers like single and double quotes for feet and inches, despite most of the rest of Blender using Imperial values.

This is an issue when it comes to creating accurately scaled models using Imperial units, as it leaves no way to manually enter in values for individual mesh components without first doing metric conversions.

A related issue is that default mesh shapes also use Blender (metric) values for initial size when added to a scene that's using Imperial units. This is less important than having median behave correctly, but it would still be nice if new meshes added while using Imperial would also use default sizes that fit the grid (such as say 2 yards x 2 yards faces for a cube rather than the default 2 meter by 2 meter size used currently regardless of units specified.


My specs:
OS: Linux Mint (32 bit)
3d Card: NVIDIA GeForce 6200 (128MB)
Blender: 2.55.0 Beta, Linux 32 bit (downloaded from the http://www.blender.org website)

Followup

Message
 

Attached Files:

No Files Currently Attached

Changes:

Field Old Value Date By
status_idOpen2010-12-11 00:31campbellbarton
close_dateNone2010-12-11 00:31campbellbarton
assigned_tonone2010-12-11 00:31campbellbarton
StatusNew2010-12-11 00:31campbellbarton