[BUG] Drivers: References to an element of a CollectionProperty are not persistent #103915
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#103915
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
driver_issue.blend
Added subscriber: @hlorus
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @mano-wii
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.
Any updates on this issue? i ran into this problem while developing an addon for version 3.4 on Windows.