Modeling > Geometry Nodes > Utilities Nodes > Map Range Node - Corrections #90506
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#90506
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Pagename:
modeling/geometry_nodes/utilities/map_range
Blender Version:
2.93
Documentation Language:
en
Permanent link
Short description of error
"By default, values outside the specified input range will be proportionally mapped as well."
should be:
"By default, Result is clamped to the target range [To Min, To Max]."
(By default "Clamp" is checked.)
Properties
"Interpolation Type" is undocumented.
It is documented in Attribute Map Range .
It implies documenting the "Steps" input too.
Maybe the following paragraph should be removed, as it relates to Compositing nodes rather than Geometry nodes:
"Usage
One important use case is to easily map the original range of the Z-depth channel to a more usable range (i.e: 0.0 - 1.0) for use as a matte for colorization or filtering operations."
Added subscriber: @Denis_NICOLAS
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm.
Not sure if this is required.
This issue was referenced by 8441
Changed status from 'Confirmed' to: 'Resolved'