Object color is set to white when inside a linked collection #73059

Closed
opened 2020-01-12 08:46:14 +01:00 by Paul Szajner · 7 comments

System Information
Operating system: Linux-4.19.0-6-amd64-x86_64-with-debian-10.2 64 Bits
Graphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74

Blender Version
Broken: version: 2.83 (sub 0), branch: master, commit date: 2020-01-10 17:32, hash: 01d9a2f71b
Worked: (optional)

Short description of error
When I link a collection (instance collection) in a scene , colors of object ( object.color ) appear white.
This is the case either by switching the viewport to solid mode and use Object shading color type , or in rendered mode by using a shader that get the color with the object info node.

Some extra infos :

  • If I link the object it's working, it's only when they are inside a collection instance that the color is set to white.
  • If I get object color with python console the color is set correctly but it doesn't show up in Workbench, Eevee or Cycles.

Exact steps for others to reproduce the error
Here are two files :
bug.blend
lib.blend
One is lib.blend (the data to link into the other scene) it contains a cube that is red either in workbench set to Object shading color, or in eevee/cycles render mode.
The other one is bug.blend where the collection containing the cube is linked, Cube appear white. We can still access the right color with the python console but it doesn't follow to the render.

**System Information** Operating system: Linux-4.19.0-6-amd64-x86_64-with-debian-10.2 64 Bits Graphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74 **Blender Version** Broken: version: 2.83 (sub 0), branch: master, commit date: 2020-01-10 17:32, hash: `01d9a2f71b` Worked: (optional) **Short description of error** When I link a collection (instance collection) in a scene , colors of object ( object.color ) appear white. This is the case either by switching the viewport to solid mode and use Object shading color type , or in rendered mode by using a shader that get the color with the object info node. Some extra infos : - If I link the object it's working, it's only when they are inside a collection instance that the color is set to white. - If I get object color with python console the color is set correctly but it doesn't show up in Workbench, Eevee or Cycles. **Exact steps for others to reproduce the error** Here are two files : [bug.blend](https://archive.blender.org/developer/F8271998/bug.blend) [lib.blend](https://archive.blender.org/developer/F8271999/lib.blend) One is lib.blend (the data to link into the other scene) it contains a cube that is red either in workbench set to Object shading color, or in eevee/cycles render mode. The other one is bug.blend where the collection containing the cube is linked, Cube appear white. We can still access the right color with the python console but it doesn't follow to the render.
Author

Added subscriber: @sozap

Added subscriber: @sozap
Author

I found that the issue occur even if the instance is local :

This file may be simpler to debug :
bug2.blend

It's a red cube and a collection instance of the same cube, the instance is white.

I found that the issue occur even if the instance is local : This file may be simpler to debug : [bug2.blend](https://archive.blender.org/developer/F8272028/bug2.blend) It's a red cube and a collection instance of the same cube, the instance is white.
Author

I finally find why this is happening , objects inside the instance collection inherit the color of the empty instead of keeping their.
So in a way it's working correctly , in another it's a weird behavior because objects doesn't react the same way once instancied. Here it's how it looks in my scene, first image is the library file, second it's how it looks once instancied and linked in another file :
obcolor_and_instances.jpg

I finally find why this is happening , objects inside the instance collection inherit the color of the empty instead of keeping their. So in a way it's working correctly , in another it's a weird behavior because objects doesn't react the same way once instancied. Here it's how it looks in my scene, first image is the library file, second it's how it looks once instancied and linked in another file : ![obcolor_and_instances.jpg](https://archive.blender.org/developer/F8272971/obcolor_and_instances.jpg)

Added subscriber: @ideasman42

Added subscriber: @ideasman42

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

Changed status from 'Needs Triage' to: 'Archived'
Campbell Barton self-assigned this 2020-01-13 07:18:14 +01:00

Closing since this is working as intended.

Although we could have the option to use some object attributes from the object instead of the instancing object, I don't think we would want this for every setting - need to see if this is worth supporting and for which properties.

Closing since this is working as intended. Although we could have the option to use some object attributes from the object instead of the instancing object, I don't think we would want this for every setting - need to see if this is worth supporting and for which properties.
Author

Ok ! Objects ID are preserved which is a good thing, Object color could be quite helpful for shading, but I understand !

Ok ! Objects ID are preserved which is a good thing, Object color could be quite helpful for shading, but I understand !
Sign in to join this conversation.
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
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#73059
No description provided.