[BUG] Drivers: References to an element of a CollectionProperty are not persistent #103915

New Issue

David Friedli · 2023-01-16T11:55:34+01:00

David Friedli commented

2023-01-16 11:55:34 +01:00

System Information
Operating system: Windows
Graphics card: -

Blender Version
Broken: 3.4.1 release
Worked: -

Short description of error
Drivers that are set on properties inside of a CollectionProperty might refer to a different element in that collection when an element is removed.

Enable the official collor rules addon under Edit>Preferences>Addons
Open the attached blend file "driver_issue.blend"
Go to the properties editor under Object>Color Rules and check that there are two rules with drivers on their opacity value
Select the first rule, Rule.001 and remove it with the "-" button
Run the script "Text" in the text editor
Check the opacity value of the Rule.002 which has changed to the value of the deleted color rule "Rule.001"

driver_issue.blend

**System Information** Operating system: Windows Graphics card: - **Blender Version** Broken: 3.4.1 release Worked: - **Short description of error** Drivers that are set on properties inside of a CollectionProperty might refer to a different element in that collection when an element is removed. 1. Enable the official collor rules addon under Edit>Preferences>Addons 2. Open the attached blend file "driver_issue.blend" 3. Go to the properties editor under Object>Color Rules and check that there are two rules with drivers on their opacity value ![Screenshot 2023-01-16 113707.png](https://archive.blender.org/developer/F14152740/Screenshot_2023-01-16_113707.png) 4. Select the first rule, Rule.001 and remove it with the "-" button 5. Run the script "Text" in the text editor 6. Check the opacity value of the Rule.002 which has changed to the value of the deleted color rule "Rule.001" ![Screenshot 2023-01-16 113842.png](https://archive.blender.org/developer/F14152747/Screenshot_2023-01-16_113842.png) [driver_issue.blend](https://archive.blender.org/developer/F14152729/driver_issue.blend)

David Friedli commented

2023-01-16 11:55:34 +01:00

Added subscriber: @hlorus

Germano Cavalcante commented

2023-01-16 15:51:39 +01:00

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

Germano Cavalcante commented

2023-01-16 15:51:39 +01:00

Added subscriber: @mano-wii

sw-tya commented

2024-01-04 23:59:34 +01:00

I have just tried this and confirm the described broken behaviour in:
3.4.0 - released - Linux x86
3.6.3 - released - Linux x86
3.6.7 - local build

My hardware will not run version 4.

Using the supplied blend file. Viewport shading -> Color:Object.
Assign a colour to each filter using the colour wheel.
It is sufficient just to reorder the rules and press the "All" button.
The first press it applies the colours while swapping the Opacity. A second press of "All" then applies the now swapped Opacity values to the cube.

This then leads me to ask what are those Custom Properties?
The Opacity values are getting picked up from there directly.

I have just tried this and confirm the described broken behaviour in: 3.4.0 - released - Linux x86 3.6.3 - released - Linux x86 3.6.7 - local build My hardware will not run version 4. Using the supplied blend file. Viewport shading -> Color:Object. Assign a colour to each filter using the colour wheel. It is sufficient just to reorder the rules and press the "All" button. The first press it applies the colours while swapping the Opacity. A second press of "All" then applies the now swapped Opacity values to the cube. This then leads me to ask what are those Custom Properties? The Opacity values are getting picked up from there directly.

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

[BUG] Drivers: References to an element of a CollectionProperty are not persistent #103915