Reversed order on multi-input sockets when duplicating node while keeping it's inputs #97002

New Issue

D0ppelgaenger · 2022-04-03T15:43:12+02:00

D0ppelgaenger commented

2022-04-03 15:43:12 +02:00

System Information
Operating system: Win11 pro
Graphics card: NVIDIA RTX 3070

Blender Version
Broken: 3.2.0 Alpha 79ff65d07b, master, 2022-04-02 21:46
Worked: -

Short description of error
Sometimes the order of Multi-input sockets gets messed up when duplicating a node, while keeping its inputs (Ctrl+Shift+D). This bug is visual as well as in function. It, from what I can tell, affects all nodes with multi-input sockets, however the 'Join Strings' and 'Geometry to Instances' nodes are most important and the easiest to replicate, since the order of their inputs is crucial to their functionality. Sometimes the output-order is correct, and the bug is only visual in nature
Exact steps for others to reproduce the error
Connect multiple inputs to a 'Join Strings' node and preview it with a 'String to Curves' node. Select the 'Join Strings' node and duplicate it while keeping its inputs (Ctrl+Shift+D). If this new 'Join Strings' is now connected to the 'String to Curves' node, the order of the strings is reversed.
Alternatively, plug multiple meshes into the 'Geometry to Instances' node use it with a 'Instances on Points' node, with pick instances checked and something plugged into the 'points' socket. When duplicating the 'Geometry to Instances' node, and using this one in the 'Instances on Points' node, the order in which the instances are picked is reversed.

**System Information** Operating system: Win11 pro Graphics card: NVIDIA RTX 3070 **Blender Version** Broken: 3.2.0 Alpha 79ff65d07bac, master, 2022-04-02 21:46 Worked: - **Short description of error** Sometimes the order of Multi-input sockets gets messed up when duplicating a node, while keeping its inputs (Ctrl+Shift+D). This bug is visual as well as in function. It, from what I can tell, affects all nodes with multi-input sockets, however the 'Join Strings' and 'Geometry to Instances' nodes are most important and the easiest to replicate, since the order of their inputs is crucial to their functionality. Sometimes the output-order is correct, and the bug is only visual in nature **Exact steps for others to reproduce the error** Connect multiple inputs to a 'Join Strings' node and preview it with a 'String to Curves' node. Select the 'Join Strings' node and duplicate it while keeping its inputs (Ctrl+Shift+D). If this new 'Join Strings' is now connected to the 'String to Curves' node, the order of the strings is reversed.![Join-strings.gif](https://archive.blender.org/developer/F12966471/Join-strings.gif) Alternatively, plug multiple meshes into the 'Geometry to Instances' node use it with a 'Instances on Points' node, with pick instances checked and something plugged into the 'points' socket. When duplicating the 'Geometry to Instances' node, and using this one in the 'Instances on Points' node, the order in which the instances are picked is reversed.![geo-to-inst.gif](https://archive.blender.org/developer/F12966473/geo-to-inst.gif)

D0ppelgaenger commented

2022-04-03 15:43:12 +02:00

Added subscriber: @Leo-Luther

D0ppelgaenger changed title from ~~Reversed order on multi-input sockets when duplicating while keeping it's inputs~~ to Reversed order on multi-input sockets when duplicating node while keeping it's inputs

2022-04-03 15:45:08 +02:00

Leon Schittek commented

2022-04-03 23:45:43 +02:00

Added subscriber: @lone_noel

Leon Schittek commented

2022-04-03 23:45:43 +02:00

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

Leon Schittek self-assigned this 2022-04-03 23:45:43 +02:00

Leon Schittek commented

2022-04-03 23:45:43 +02:00

Hey, @Leo-Luther, thanks for the report and the clear demonstration of the issue. I can confirm this.

It seems like there are a few cases where we need to make sure to preserve the multi_input_socket_index when copying links.

Hey, @Leo-Luther, thanks for the report and the clear demonstration of the issue. I can confirm this. It seems like there are a few cases where we need to make sure to preserve the `multi_input_socket_index` when copying links.

blender-admin commented

2022-04-18 22:28:03 +02:00

This issue was referenced by 03d39a04a3

This issue was referenced by 03d39a04a3a29b7eb464ca2ae39c69757ee9f6c2

Leon Schittek commented

2022-04-18 22:33:11 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Leon Schittek closed this issue

2022-04-18 22:33:11 +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

Reversed order on multi-input sockets when duplicating node while keeping it's inputs #97002