IDProps mismatch (pyRNA-defined vs. custom props) can confuse liboverride system in Collection property case #92518
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
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#92518
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.36
Blender Version
Broken: version: 2.93.5, branch: master, commit date: 2021-10-05 12:04, hash:
a791bdabd0
Short description of error
Override libraries linking seem to have an issue when linking collection property registered by an addon or a script.
If I add items to a collection property of an object in the source file, and then link the object using override libraries in a new file. I can't delete this item in the collection property, that's ok. The problem is when I go back to the source file and clear the collection property, so it doesn't have items anymore, then going back again to the linked file,the object still has this property item, even if it was deleted in the source file, and it still can't be removed.
Exact steps for others to reproduce the error
The rar file includes a source file, a file with the linked collection, and a test addon which just register a property, you can also just run the script from the source file, but better to test with the addon.
How to repeat the error?
Override_property_Bug.rar
Added subscriber: @TalHershkovich
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @mont29
I think the issue here is when you mix blenders with and without your addon.
IDProps can be define from python, and as regular custom properties. When you open a file with some py-defined idprops, which do not exist in current blender (because e.g. addon defining those is not enabled or active), they get 'converted' to regular IDProps... Think the issue comes from that.
Not really something we can easily work on currently, that duality of IDProps types is a nightmare to deal with anyway, would consider this more as a known issue caused by internal limitations.
Collection property item can't be removed with library overrides after being cleared from source file.to IDProps mismatch (pyRNA-defined vs. custom props) can confuse liboverride system in Collection property caseNote that I cannot reproduce that issue from scratch if I keep using a blender with your addon enabled all the time.
That's strange because it actually happens to me when I do keep the addon turned on all the time. When I turn the addon off and restart Blender then it's actually solving the problem and the "ghost" property is removed.
Did you
When you use the addon and load the linked file that I've attached, can you actually see the "ghost" item of the property in the console ?
Added subscriber: @timodriaan