Overriding materials is not working as expected in 2.91 beta #82033

Closed
opened 2020-10-24 18:25:28 +02:00 by Juan Gea · 8 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71

Blender Version
Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-10-23 17:33, hash: 70cc0d7121

Tested also with today's buildbot 2.92 (24/10/2020) and it has the same problem.

Worked: never

Short description of error
@mont29 wrote a description on how materials could be overriden for the time being, but this is not working as expected, here is the description:

@mont29
With current master, if you override the object and assign material to the object and select a new material for an existing slot, it should work.
Same if you also override the obdata and assign material to obdata and select a new material for an existing slot there.

Adding new slots won’t work though, and material properties themselves are mostly non-overridable currently.

I've prepared some simple files that show the problem:

Monkey_Base.blend
Monkey_Collection_Mat_Override.blend
Monkey_Object_Mat_Override.blend

Basically in Monkey_Collection_Mat_Override.blend and Monkey_Object_Mat_Override.blend the overrides are already done, the original object is in the Monkey_Base.blend file.

Just follow this steps:

1.- Open one of the "Mat_Override" blends, no matter what of them, or test both.

2.- Select the monkey head, it should be there if you don't have problem with the link paths, I think you should not have any problem, in case you have just relocate the linked .blend to the Monkey_Base.blend

3.- You will see there is also a sphere in the scene, that sphere has another material, in this case is a local one

4.- be sure to create the override in the outliner for the material, with the Add Library Override Hierarchy option, by the way this is not done already because it's not being saved with the file.
image.png

5.- Assign the sphere material to the override monkey, you will see that will work so far, you will see the material being override in the scene.

6.- Save the scene with whatever name you want

7.- Close blender or go to a new file

8.- Re-Open the file you just saved

9.- the override was not saved and the monkey is still red with the original material

Here is also a video to show the problem in case you prefer to watch it:

Overrides_Not_Working_As_Expected.mp4

I hope this can be fixed for 2.91 release, since it was something expected to work by @mont29 and he considered it a possible bug of the current status.

Thanks!

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71 **Blender Version** Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-10-23 17:33, hash: `70cc0d7121` Tested also with today's buildbot 2.92 (24/10/2020) and it has the same problem. Worked: never **Short description of error** @mont29 wrote a description on how materials could be overriden for the time being, but this is not working as expected, here is the description: > @mont29 >With current master, if you override the object and assign material to the object and select a new material for an existing slot, it should work. >Same if you also override the obdata and assign material to obdata and select a new material for an existing slot there. >Adding new slots won’t work though, and material properties themselves are mostly non-overridable currently. I've prepared some simple files that show the problem: [Monkey_Base.blend](https://archive.blender.org/developer/F9071611/Monkey_Base.blend) [Monkey_Collection_Mat_Override.blend](https://archive.blender.org/developer/F9071616/Monkey_Collection_Mat_Override.blend) [Monkey_Object_Mat_Override.blend](https://archive.blender.org/developer/F9071617/Monkey_Object_Mat_Override.blend) Basically in *Monkey_Collection_Mat_Override.blend* and *Monkey_Object_Mat_Override.blend* the overrides are already done, the original object is in the *Monkey_Base.blend* file. Just follow this steps: 1.- Open one of the "Mat_Override" blends, no matter what of them, or test both. 2.- Select the monkey head, it should be there if you don't have problem with the link paths, I think you should not have any problem, in case you have just relocate the linked .blend to the *Monkey_Base.blend* 3.- You will see there is also a sphere in the scene, that sphere has another material, in this case is a local one 4.- be sure to create the override in the outliner for the material, with the *Add Library Override Hierarchy* option, by the way this is not done already because it's not being saved with the file. ![image.png](https://archive.blender.org/developer/F9071669/image.png) 5.- Assign the sphere material to the override monkey, you will see that will work so far, you will see the material being override in the scene. 6.- Save the scene with whatever name you want 7.- Close blender or go to a new file 8.- Re-Open the file you just saved 9.- the override was not saved and the monkey is still red with the original material Here is also a video to show the problem in case you prefer to watch it: [Overrides_Not_Working_As_Expected.mp4](https://archive.blender.org/developer/F9071687/Overrides_Not_Working_As_Expected.mp4) I hope this can be fixed for 2.91 release, since it was something expected to work by @mont29 and he considered it a possible bug of the current status. Thanks!
Author

Added subscribers: @mont29, @juang3d

Added subscribers: @mont29, @juang3d

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

Changed status from 'Needs Triage' to: 'Archived'
Bastien Montagne self-assigned this 2020-10-26 13:59:35 +01:00

It works if in the original library file the obdata does not have an assigned material (i.e. if the material is linked to the object only in the lib file).

Not much to do beyond that, fixing this nightmare is on the todo list at some point.

It works if in the original library file the obdata does not have an assigned material (i.e. if the material is linked to the object only in the lib file). Not much to do beyond that, fixing this nightmare is on the todo list at some point.
Author

Ok, but I don’t understand what you mean, can you explain a bit how to make it work?

Thanks :)

Ok, but I don’t understand what you mean, can you explain a bit how to make it work? Thanks :)

Your .blend library file should not have material assigned to mesh, only to object.

Your .blend library file should not have material assigned to mesh, only to object.

Added subscriber: @VupliDerts-2

Added subscriber: @VupliDerts-2

As somebody mentioned in the comments of this video: https://www.youtube.com/watch?v=8vmVGUnnOIs

It is possible to persistently override materials if the original material is linked to the object, however it does appear not to work if the original material is linked to the data.
Not sure if this is a feature or a bug or just something I am misunderstanding about the way my object is linked

I am using Blender 3.0.

Hope that helps somebody, cheers!

As somebody mentioned in the comments of this video: https://www.youtube.com/watch?v=8vmVGUnnOIs It is possible to persistently override materials ***if*** the original material is linked to the object, however it does appear not to work if the original material is linked to the data. Not sure if this is a feature or a bug or just something I am misunderstanding about the way my object is linked I am using Blender 3.0. Hope that helps somebody, cheers!

Added subscriber: @Emi_Martinez

Added subscriber: @Emi_Martinez
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
4 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#82033
No description provided.