LibOverride: How to handle heavy data-blocks (meshes, shape-keys, actions...) #78944
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#78944
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?
Problem
Storing overrides of potentially heavy data-blocks uses a lot of space in .blend files, for data that is not overridable at all (like mesh geometry, existing action FCurves, etc.).
Proposed Solution
Write, store 'empty' versions of those override data-blocks, instead of complete ones.
Pros:
Cons:
Note that technically, this should be fairly easy to implement (although some IDs, like actions or shape keys, may be less trivial since we ultimately want to allow creating or replacing whole shapes/FCurves in those). Also CC'ing the UI team, since this is more of an UX decision to make than anything else?
Identified Affected ID Types
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscribers: @mont29, @brecht, @ideasman42, @dfelinto, @pablovazquez
I don't think files with overrides should aim to be autonomous, relying on the linked data to be available is correct I think, regardless of the datablock type.
Added subscriber: @Mets
I agree. As a user, I don't consider overridden datablocks to be local, I consider them to be linked and overridden. If the link is broken, I can only blame myself when I see that the override is also broken. Of course warnings and foolproofing for these cases is always welcome :)
Yes, that is also my vision of things, just wanted to be sure there is a consensus about it.
Added subscriber: @TakeshiFunahashi
I have many shape key , at same time they are driven by rig (object) custom prop UI controller, which drive mesh shape key values) from add on panell.
Then when I override the Rig and children meshe collection, then mesh set as local, now I can change shape key values, but all shape keys
driver still be driven by library rig props only. But it need to be driven current over-ride rig.
To make all controller work again, after set overridable for all rig.custom props in library by script, then I need to re-assgin all shape key drivers target t, in override scene,
as override rig object, (custom prop) one by one,, with driver editor..
Can I expect, this problem will be solved?
Changed status from 'Confirmed' to: 'Resolved'