Geometry Nodes: Utilities Map Range only works in 'Linear' interpolation mode #87117

New Issue

Wannes Malfait · 2021-04-01T14:01:44+02:00

Wannes Malfait commented

2021-04-01 14:01:44 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89

Blender Version
Broken: Hasn't worked in any version

Short description of error
Changing the interpolation to a mode other than linear makes the node only output zero.

Exact steps for others to reproduce the error

Default blend file
Add a geometry node tree to the default cube
Add a Geometry -> Transform node between the group input and output.
Add a Utilities -> Map Range node and plug the output socket into the Translation input socket of the Transform node.
Changing the value socket of the Map Range node changes the position of the cube.
Set the interpolation mode to Smoothstep (or another one). Changing the value socket does nothing to the translation of the cube.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89 **Blender Version** Broken: Hasn't worked in any version **Short description of error** Changing the interpolation to a mode other than `linear` makes the node only output zero. **Exact steps for others to reproduce the error** - Default blend file - Add a geometry node tree to the default cube - Add a `Geometry -> Transform` node between the group input and output. - Add a `Utilities -> Map Range` node and plug the output socket into the `Translation` input socket of the `Transform` node. - Changing the value socket of the `Map Range` node changes the position of the cube. - Set the interpolation mode to `Smoothstep` (or another one). Changing the value socket does nothing to the translation of the cube. ![image.png](https://archive.blender.org/developer/F9916859/image.png)

Wannes Malfait commented

2021-04-01 14:01:44 +02:00

Added subscriber: @wannes.malfait

Jacques Lucke commented

2021-04-01 14:13:33 +02:00

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

Victor-Louis De Gusseme commented

2021-04-01 21:33:07 +02:00

Added subscriber: @victorlouis

Victor-Louis De Gusseme commented

2021-04-01 21:33:07 +02:00

I'm not sure whether this is a bug. I believe the Utilities Map Range node uses the code from node_shader_map_range.cc. In that file you can find this:

  if (interpolation_type == NODE_MAP_RANGE_LINEAR) {
     ...
  else {
    builder.set_not_implemented();
  }

So I think the other modes were just never implemented for the CPU code path of the shader node.

I'm not sure whether this is a bug. I believe the Utilities Map Range node uses the code from `node_shader_map_range.cc`. In that file you can find this: ``` if (interpolation_type == NODE_MAP_RANGE_LINEAR) { ... else { builder.set_not_implemented(); } ``` So I think the other modes were just never implemented for the CPU code path of the shader node.

Wannes Malfait self-assigned this 2021-04-02 09:13:53 +02:00

Wannes Malfait commented

2021-04-02 09:13:53 +02:00

Yes, but then the user shouldn't be able to select the other modes. I'll try implementing the other functions, since they are really useful.

Wannes Malfait removed their assignment 2021-04-03 10:42:03 +02:00

Charlie Jolly commented

2021-04-03 17:13:36 +02:00

Added subscriber: @CharlieJolly

Charlie Jolly self-assigned this 2021-04-03 17:13:36 +02:00

Charlie Jolly commented

2021-04-03 17:13:36 +02:00

Patch added here: D10885: Geometry Nodes: Add missing Map Range modes to shader node