Geo Nodes Random Value node odd behavior on changing Type #101479

New Issue

Gavin Scott · 2022-09-29T19:18:38+02:00

Gavin Scott commented

2022-09-29 19:18:38 +02:00

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.98

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce

Short description of error
When the Type field of the Random Value node is changed, any existing output connections remain but are inactive and invisible.

Exact steps for others to reproduce the error
New scene, Cube Selected, Geometry Nodes tab, Create a new GeometryNodes.

In the node editor, create a Utility-Random Value node.

Create a couple of nodes to receive the random values. I made two Instance on Points nodes.

With the Random Value node left in its default state with the Type set to Float, drag the Value output to an input on one of the Instance on Points nodes, say the Rotation input on the first one.

Now change the Type in the Random Value node from Float to anything else, say Vector.

Note that the noodle has vanished, the output no longer affects the Rotation on the Instance on Points node, but it is still connected as the fields are not shown under Rotation as would be the case if it had been disconnected.

Now drag the output Value of the Random Value node to some other input, say the Scale input on the other Instance on Points node. That behaves as expected.

Now change the Type in the Random Value node back to Float. The Vector output noodle disappears and the Scale input it was connected to behaves as the Rotation field did before (invisible input, non-active but still connected), but the old Float connection noodle has now magically reappeared and is actively connected to the original Rotation input.

You can have four different sets of persistent output connections, one for each Type value. Only one will be visible and active at any moment based on the Type field setting, but the others will exist even though they are invisible and pass no data. There is no indication on their invisibly connected inputs that there is anything there, though the input will no longer have its "default" behavior.

I looked at the documentation for the node and Geo Nodes in general, but can't find anything suggesting this is intended behavior, and it seems like crazy UI behavior, so I respectfully submit it as a potential bug.

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.98 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: `0759f671ce` **Short description of error** When the Type field of the Random Value node is changed, any existing output connections remain but are inactive and invisible. **Exact steps for others to reproduce the error** New scene, Cube Selected, Geometry Nodes tab, Create a new GeometryNodes. In the node editor, create a Utility-Random Value node. Create a couple of nodes to receive the random values. I made two Instance on Points nodes. With the Random Value node left in its default state with the Type set to Float, drag the Value output to an input on one of the Instance on Points nodes, say the Rotation input on the first one. Now change the Type in the Random Value node from Float to anything else, say Vector. Note that the noodle has vanished, the output no longer affects the Rotation on the Instance on Points node, but it is still connected as the fields are not shown under Rotation as would be the case if it had been disconnected. Now drag the output Value of the Random Value node to some other input, say the Scale input on the other Instance on Points node. That behaves as expected. Now change the Type in the Random Value node back to Float. The Vector output noodle disappears and the Scale input it was connected to behaves as the Rotation field did before (invisible input, non-active but still connected), but the old Float connection noodle has now magically reappeared and is actively connected to the original Rotation input. You can have four different sets of persistent output connections, one for each Type value. Only one will be visible and active at any moment based on the Type field setting, but the others will exist even though they are invisible and pass no data. There is no indication on their invisibly connected inputs that there is anything there, though the input will no longer have its "default" behavior. I looked at the documentation for the node and Geo Nodes in general, but can't find anything suggesting this is intended behavior, and it seems like crazy UI behavior, so I respectfully submit it as a potential bug.

Gavin Scott commented

2022-09-29 19:18:38 +02:00

Added subscriber: @GavinScott

Richard Antalik commented

2022-09-29 21:35:54 +02:00

Closed as duplicate of #89387

Richard Antalik closed this issue

2022-09-29 21:35:54 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Geo Nodes Random Value node odd behavior on changing Type #101479