Geometry Nodes: Map Range Node documentation needs update #95179
Labels
No Label
Meta
Good First Issue
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 & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information 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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#95179
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Added subscriber: @Izak-van-Langevelde
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @PratikPB2123
Added subscriber: @wannes.malfait
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.
Added subscriber: @Blendify
Changed status from 'Confirmed' to: 'Resolved'
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