Library overrides get reset when the linked file changes #110742

Open
opened 2023-08-03 08:56:06 +02:00 by Robert S · 10 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67

Blender Version
Broken: version: 3.6.1 Release Candidate, branch: blender-v3.6-release, commit date: 2023-07-16 02:43, hash: edc1a09966a7
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error

  1. Link a collection from a different file
  2. Override everything (selection & content & data etc down to the materials, so that materials have an O in front of them)
  3. Replace a few materials on some objects with new materials
  4. Go into the originally linked different file and make some changes to a mesh (and perhaps move some meshes to a different collection that's not linked)
  5. Open the files with the link in it

Result:

All material changes have now been reset

Expected:

The overriden materials should of course stay the same!

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67 **Blender Version** Broken: version: 3.6.1 Release Candidate, branch: blender-v3.6-release, commit date: 2023-07-16 02:43, hash: `edc1a09966a7` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** 1. Link a collection from a different file 2. Override everything (selection & content & data etc down to the materials, so that materials have an O in front of them) 3. Replace a few materials on some objects with new materials 4. Go into the originally linked different file and make some changes to a mesh (and perhaps move some meshes to a different collection that's not linked) 5. Open the files with the link in it Result: All material changes have now been reset Expected: The overriden materials should of course stay the same!
Robert S added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-03 08:56:07 +02:00
Member

Hi, thanks for the report.

Replace a few materials on some objects with new materials

I'm not sure how you could replace material on overridden object. Can you expand on that?
Is it possible actually on overridden data-blocks? Like add or remove the material.

Attaching the reference file which I'm using.

Hi, thanks for the report. > Replace a few materials on some objects with new materials I'm not sure how you could replace material on overridden object. Can you expand on that? Is it possible actually on overridden data-blocks? Like add or remove the material. Attaching the reference file which I'm using.
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-08-03 11:53:03 +02:00
Author

Please see the attached video and example files.

Please see the attached video and example files.
Member

Thanks, unable to confirm as demonstrated in video, will check again later.
Looks like override resyncing happened when linked collection is changed in source file.

Thanks, unable to confirm as demonstrated in video, will check again later. Looks like override resyncing happened when linked collection is changed in source file.
Pratik Borhade added
Status
Needs Triage
Interest
Overrides
and removed
Status
Needs Information from User
labels 2023-08-03 12:55:48 +02:00
Author

There's a lot of weird things happening when working with material overrides... I don't even know what to say about this one:

There's a lot of weird things happening when working with material overrides... I don't even know what to say about this one:
Author

Great, after thinking that what could be seen above in the video could be "fixed" manually, by deleting the extra objects which appear, but after saving and re-loading the hierarchy of many unrelated objects in the file is messed up (similar to this but not as severe). I'll say this again, linked library overrides is not ready for production! ☹

Great, after thinking that what could be seen above in the video could be "fixed" manually, by deleting the extra objects which appear, but after saving and re-loading the hierarchy of many unrelated objects in the file is messed up (similar to [this ](https://projects.blender.org/blender/blender/issues/110744)but not as severe). I'll say this again, linked library overrides is not ready for production! ☹
Member

#110742 (comment) I do think this one should keep overridden since the hierarchy of the object/material isn't changed.

  • In 3.6.1, the changed material slot isn't kept.
  • However, in 4.0, I am able to keep the modified material after changing material in the source file, so unable to confirm this:
3.6.1 4.0
图片 图片

Not sure about the second video about those BREP objects tho...

@RobertS Could you try using 4.0 and see if it works as expected? Thanks!

https://projects.blender.org/blender/blender/issues/110742#issuecomment-991842 I do think this one should keep overridden since the hierarchy of the object/material isn't changed. - In 3.6.1, the changed material slot isn't kept. - However, in 4.0, I am able to keep the modified material after changing material in the source file, so unable to confirm this: | 3.6.1 | 4.0 | |---|---| | ![图片](/attachments/1e3bd0d1-ca24-4829-9747-e2c1f06f91bc) | ![图片](/attachments/a0ba870a-55bc-4023-a878-70802e14bf14) | Not sure about the second video about those `BREP` objects tho... @RobertS Could you try using 4.0 and see if it works as expected? Thanks!
YimingWu added
Module
Pipeline, Assets & IO
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-08-04 03:52:36 +02:00
Author

Yes, testing the example file does seem as if it's fixed in 4.0 alpha.

Yes, testing the example file does seem as if it's fixed in 4.0 alpha.
Member

Yes, testing the example file does seem as if it's fixed in 4.0 alpha.

Thanks. In that case we need to identify the resolving commit for backporting. (I'll check)
Perhaps same commits has fixed this?: #109993 (comment)

> Yes, testing the example file does seem as if it's fixed in 4.0 alpha. Thanks. In that case we need to identify the resolving commit for backporting. (I'll check) Perhaps same commits has fixed this?: https://projects.blender.org/blender/blender/issues/109993#issuecomment-977722
Pratik Borhade added this to the 3.6 LTS milestone 2023-08-04 10:44:05 +02:00
Member

Seems to be #109993 . Can't find other relevant commits that does the job.

Seems to be #109993 . Can't find other relevant commits that does the job.
Author

Just a FYI, I still see it in other places in 4.0 and I get a crash on top of it.

Unfortunately, it's in a large and sensitive project at work, so I can't share the file and attempts to remove everything but the affected objects have failed to reproduce it.

In this new variant, it seems to be restricted to objects with more than one material, and what happens is that the overriden material in the first slot actually gets applied to the second slot as well (although, for the green object in the screenshot, it's actually a third slot material that got put in the first slot instead of my override). And as mentioned in that other issue, if I delete everything except those two objects from my files, I can no longer replicate the problem.

Just a FYI, I still see it in other places in 4.0 and [I get a crash on top of it](https://projects.blender.org/blender/blender/issues/110749#issuecomment-995434). Unfortunately, it's in a large and sensitive project at work, so I can't share the file and attempts to remove everything but the affected objects have failed to reproduce it. In this new variant, it seems to be restricted to objects with more than one material, and what happens is that the overriden material in the first slot actually gets applied to the second slot as well (although, for the green object in the screenshot, it's actually a third slot material that got put in the first slot instead of my override). And as mentioned in that other issue, if I delete everything except those two objects from my files, I can no longer replicate the problem.
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
3 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#110742
No description provided.