Node values for sizing remains in metric even with imperial selected #97203

New Issue

Andrew Turner · 2022-04-09T20:59:45+02:00

Andrew Turner commented

2022-04-09 20:59:45 +02:00

System Information
Operating system: Win 10
Graphics card: 3080

Blender Version
3.0.0

I’m trying to create a grid at a specific size with a specific number of divisions in each direction.

However, I’m not sure how Blender is calculating sizes, since what I thought would work as numeric inputs (values, to allow fractional input) is translating to a setting of 1/3 of what it should be.

In the picture below, the cube in the center is 1’. I thought I could use 1.0 in the value input and arrive at the same size, but it’s… weird.

FWIW it appears the input remains in Blender default metric units. Here is a view with a setting of “1” which appears to be 1 meter (39.4 inches)

If the input is removed, the units are correct:

Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Win 10 Graphics card: 3080 **Blender Version** 3.0.0 I’m trying to create a grid at a specific size with a specific number of divisions in each direction. However, I’m not sure how Blender is calculating sizes, since what I thought would work as numeric inputs (values, to allow fractional input) is translating to a setting of 1/3 of what it should be. In the picture below, the cube in the center is 1’. I thought I could use 1.0 in the value input and arrive at the same size, but it’s… weird. ![e436137db498f327f6c07a0b94078431db452d0b.jpeg](https://archive.blender.org/developer/F12986470/e436137db498f327f6c07a0b94078431db452d0b.jpeg) FWIW it appears the input remains in Blender default metric units. Here is a view with a setting of “1” which appears to be 1 meter (39.4 inches) ![aedfcd7f72896a7c57df876640aaf7c554c77a4c.jpeg](https://archive.blender.org/developer/F12986478/aedfcd7f72896a7c57df876640aaf7c554c77a4c.jpeg) If the input is removed, the units are correct: ![737e6080f40034da389defc2a139493359b39298.jpeg](https://archive.blender.org/developer/F12986481/737e6080f40034da389defc2a139493359b39298.jpeg) Based on the default startup or an attached .blend file (as simple as possible).

Andrew Turner commented

2022-04-09 20:59:45 +02:00

Added subscriber: @turner410

blender-admin commented

2022-04-09 20:59:45 +02:00

#99863 was marked as duplicate of this issue

blender-admin commented

2022-04-09 20:59:45 +02:00

#98034 was marked as duplicate of this issue

blender-admin commented

2022-04-09 20:59:45 +02:00

#97439 was marked as duplicate of this issue

Philipp Oeser commented

2022-04-12 15:25:59 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-04-12 15:25:59 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2022-04-12 15:25:59 +02:00

Inputs/Values tagged with PROP_DISTANCE will take scene units into account (and will allow for the special input like ft, m '' etc.
The Value / Integer nodes however dont support this since they are very general.
Possibly, a good solution would be to make them aware of units as well?
Other than that, passing along values between unit aware and non-unit aware nodes feels like a bug (not sure it will be considered one though), will confirm for now.

(could have sworn this came up in another report before, but cannot find it atm)

Inputs/Values tagged with `PROP_DISTANCE` will take scene units into account (and will allow for the special input like `ft`, `m` `''` etc. The `Value` / `Integer` nodes however dont support this since they are very general. Possibly, a good solution would be to make them aware of units as well? Other than that, passing along values between unit aware and non-unit aware nodes feels like a bug (not sure it will be considered one though), will confirm for now. (could have sworn this came up in another report before, but cannot find it atm)

Hans Goudey commented

2022-04-15 23:15:54 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2022-04-15 23:15:54 +02:00

Changed status from 'Confirmed' to: 'Archived'

Hans Goudey closed this issue

2022-04-15 23:15:54 +02:00

Hans Goudey commented

2022-04-15 23:15:54 +02:00

The data that is passed between nodes is always in "Blender Units", so Meters by default if you don't adjust the unit scale.
The units are just a UI feature so you can see/enter values in different unit systems, more of a tag for displaying values in a button.

In the future we want to propagate these unit tags between nodes in the node editor, but this is a large project with larger design ramifications, so it wouldn't be handled here.

Thanks for the report anyway.

The data that is passed between nodes is always in "Blender Units", so Meters by default if you don't adjust the unit scale. The units are just a UI feature so you can see/enter values in different unit systems, more of a tag for displaying values in a button. In the future we want to propagate these unit tags between nodes in the node editor, but this is a large project with larger design ramifications, so it wouldn't be handled here. Thanks for the report anyway.

Philipp Oeser commented

2022-04-19 14:45:56 +02:00

Added subscriber: @baoyu