Custom Properties missing from Collection Instance #122408

Closed
opened 2024-05-28 23:56:00 +02:00 by Justin-Cameron · 4 comments

System Information
Operating system: macOS Ventura 13.4
Graphics card: Radeon Pro 580 8GB

Blender Version
Broken: 4.2.0 Alpha

Short description of error
Custom properties belonging to a collection appear under the custom properties panel of linked collections but not for collection instances.

Exact steps for others to reproduce the error
Create a collection > add a custom property to the collection > create a new scene > add instance of collection to scene > observe that custom property does not exist for collection instance

imageimage

**System Information** Operating system: macOS Ventura 13.4 Graphics card: Radeon Pro 580 8GB **Blender Version** Broken: 4.2.0 Alpha **Short description of error** Custom properties belonging to a collection appear under the custom properties panel of linked collections but not for collection instances. **Exact steps for others to reproduce the error** Create a collection > add a custom property to the collection > create a new scene > add instance of collection to scene > observe that custom property does not exist for collection instance ![image](/attachments/45bf120f-49a1-482e-beb2-799a2ce4e1eb)![image](/attachments/b78db0cd-073c-4dbc-9e1a-085db0c9c3b9)
267 KiB
301 KiB
Justin-Cameron added the
Status
Needs Triage
Type
Report
Severity
Normal
labels 2024-05-28 23:56:01 +02:00
Author

This issue was mentioned here a year ago, and for whatever reason there seemed to be a communication breakdown and the point did not get across.

This issue was mentioned [here](https://projects.blender.org/blender/blender/issues/105008) a year ago, and for whatever reason there seemed to be a communication breakdown and the point did not get across.
Author

Collection Instances are treated like objects rather than collections so none of the collection-level custom properties carry over. I understand why collection instances are treated like objects, however whatever the appropriate handling ought to be, I think dropping properties into the ether is not it.

Collection Instances are treated like objects rather than collections so none of the collection-level custom properties carry over. I understand why collection instances are treated like objects, however whatever the appropriate handling ought to be, I think dropping properties into the ether is not it.
Member

"Collection instance" is an "Object" , not a "Collection", so the properties from the instanced collection won't show in the instancer.

To make life easier for your purpose, you could try registering a panel yourself which "adjusts the properties of instanced collection from the instance object".

Closing this for now since it's not actually a bug with blender, but feel free to comment

"Collection instance" is an "Object" , not a "Collection", so the properties from the instanced collection won't show in the instancer. To make life easier for your purpose, you could try registering a panel yourself which "adjusts the properties of instanced collection from the instance object". Closing this for now since it's not actually a bug with blender, but feel free to comment
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2024-05-29 05:10:47 +02:00
Author

If a Collection can become an Object then why can't a Custom Property belonging to a Collection become a Custom Property belonging to an Object? If the new Object (Collection Instance) encompasses everything about that Collection (to include all of it's geometry) why would it not also encompass it's custom properties? All I'm hearing is that this isn't the case because it isn't the case without any further justification

If a Collection can become an Object then why can't a Custom Property belonging to a Collection become a Custom Property belonging to an Object? If the new Object (Collection Instance) encompasses everything about that Collection (to include all of it's geometry) why would it not also encompass it's custom properties? All I'm hearing is that this isn't the case because it isn't the case without any further justification
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#122408
No description provided.