NodeGroup Drivers Move to Wrong Property After Change #120724

New Issue

Kevin C. Burke · 2024-04-17T00:22:38+02:00

Kevin C. Burke commented

2024-04-17 00:22:38 +02:00

System Information
Operating system: macOS-14.4-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Max 1.2

Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270
Worked: N/A

Short description of error
When deleting a property that changes a NodeGroup's properties' indices, drivers get reassigned to the incorrect properties

Exact steps for others to reproduce the error

Create a NodeGroup in the Shader Editor with three input properties.
Create a driver on the second Property
Delete the first property
The driver will get reassigned to the new second property (it's happening by index, I'm assuming?)

In this video, the driver is on the second NodeGroup's Input property "Brightness". When a property previous to "Brightness" is removed, the driver is now on the next property "Contrast":
Screen Recording

I have attached an example .blend file.

**System Information** Operating system: macOS-14.4-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Max 1.2 **Blender Version** Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270` Worked: N/A **Short description of error** When deleting a property that changes a NodeGroup's properties' indices, drivers get reassigned to the incorrect properties **Exact steps for others to reproduce the error** 1. Create a NodeGroup in the Shader Editor with three input properties. 2. Create a driver on the second Property 2. Delete the first property 3. The driver will get reassigned to the new second property (it's happening by index, I'm assuming?) In this video, the driver is on the second NodeGroup's Input property "Brightness". When a property previous to "Brightness" is removed, the driver is now on the next property "Contrast": **[Screen Recording](https://youtu.be/o4JQHvQNJZw)** I have attached an example .blend file. ![Before](/attachments/f4dc2aa4-6c34-4c6c-8684-acfd2c80e5ba)

image.png

182 KiB

Group_Driver_Bug.blend

841 KiB

Kevin C. Burke added the

labels 2024-04-17 00:22:39 +02:00

YimingWu commented

2024-04-17 10:47:37 +02:00

Yes, the path of that property is accessed with index.

Does this pose a significant usability problem on your side? Since this is how the property is recorded in the driver system, so not likely we could change this, and manually updating all the drivers when socket changed in a custom group will also involve other systems like the animation. Usually node groups are static throughout the usage, so you might want to expect this behaviour until the design of your node group has solidified.

Yes, the path of that property is accessed with index. Does this pose a significant usability problem on your side? Since this is how the property is recorded in the driver system, so not likely we could change this, and manually updating all the drivers when socket changed in a custom group will also involve other systems like the animation. Usually node groups are static throughout the usage, so you might want to expect this behaviour until the design of your node group has solidified.

Philipp Oeser referenced this issue

2024-04-17 12:31:36 +02:00

Nodes: Animation (e.g. driver) jumps to another socket when the socket order changes (socket move up/down or when a socket gets removed) #101339

Philipp Oeser commented

2024-04-17 12:34:19 +02:00

Same as #101339, will close as a duplicate.

Please subscribe in #101339 if you want further updates.

Same as #101339, will close as a duplicate. Please subscribe in #101339 if you want further updates.

👍 1

Philipp Oeser closed this issue

2024-04-17 12:34:22 +02:00

Blender Bot added