Geometry Nodes: Map Range Node documentation needs update #95179

New Issue

Izak van Langevelde · 2022-01-24T14:00:59+01:00

2022-01-24 14:00:59 +01:00

The Map Range Geometry Node is a field node, which should be reflected in screenshot and description of the documentation
manual link: https://docs.blender.org/manual/en/3.1/modeling/geometry_nodes/utilities/map_range.html

The Map Range Geometry Node is a field node, which should be reflected in screenshot and description of the documentation manual link: https://docs.blender.org/manual/en/3.1/modeling/geometry_nodes/utilities/map_range.html

Izak van Langevelde commented

2022-01-24 14:00:59 +01:00

Added subscriber: @Izak-van-Langevelde

Pratik Borhade commented

2022-01-25 03:04:31 +01:00

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

Pratik Borhade commented

2022-01-25 03:04:36 +01:00

Added subscriber: @PratikPB2123

Wannes Malfait commented

2022-01-26 10:47:10 +01:00

Added subscriber: @wannes.malfait

Wannes Malfait commented

2022-01-26 10:47:10 +01:00

At the moment the documentation just references the shader documentation of the node. This is because there is no real difference in the way the shader and geometry nodes versions work. The same thing is done for other similar nodes like the math node and the noise texture nodes.

At the moment the documentation just references the [shader documentation](https://docs.blender.org/manual/en/3.1/render/shader_nodes/converter/map_range.html?highlight=map%20range) of the node. This is because there is no real difference in the way the shader and geometry nodes versions work. The same thing is done for other similar nodes like the math node and the noise texture nodes.

Aaron Carlisle commented

2022-01-29 20:50:18 +01:00

Added subscriber: @Blendify

Aaron Carlisle commented

2022-01-29 20:50:18 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Aaron Carlisle closed this issue

2022-01-29 20:50:18 +01:00

Aaron Carlisle self-assigned this 2022-01-29 20:50:18 +01:00

Aaron Carlisle commented

2022-01-29 20:50:18 +01:00

Yeah I do not consider this a bug, in the future shader nodes will support fields and this won't be an issue.

In the meantime its more of an inconvenience

Yeah I do not consider this a bug, in the future shader nodes will support fields and this won't be an issue. In the meantime its more of an inconvenience

Sign in to join this conversation.