Append already linked Data #55629

Closed
opened 2018-06-26 12:26:44 +02:00 by Julien Kaspar · 25 comments
Member

Blender Version
Broken: 2.8 e17285a381

Short description of error
When appending data that is already linked into the file, it will also be linked instead of being made local.

**Blender Version** Broken: 2.8 e17285a3816 **Short description of error** When appending data that is already linked into the file, it will also be linked instead of being made local.
Author
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar

#92688 was marked as duplicate of this issue

#92688 was marked as duplicate of this issue

#86691 was marked as duplicate of this issue

#86691 was marked as duplicate of this issue

#84900 was marked as duplicate of this issue

#84900 was marked as duplicate of this issue

#79903 was marked as duplicate of this issue

#79903 was marked as duplicate of this issue

#67740 was marked as duplicate of this issue

#67740 was marked as duplicate of this issue
Bastien Montagne was assigned by Julien Kaspar 2018-06-26 12:28:36 +02:00

Added subscriber: @Alex_Rom

Added subscriber: @Alex_Rom

Added subscriber: @Alex3

Added subscriber: @Alex3

Have been working on this today, have it partially working (crashes still a lot, the append part of the code is very complicated :( ), but am hitting some design issues actually.

Thing is, in append, after linked data has been made local, we remap all its local usages to the local data-block. It means that if e.g. you have assigned a linked material to some local object, then decide to append that same material, currently your already existing local object will be also remapped to use the new local copy (appended version) of the material. I kind of have the feeling that this is not the desired behavior?

Have been working on this today, have it partially working (crashes still a lot, the append part of the code is very complicated :( ), but am hitting some design issues actually. Thing is, in append, after linked data has been made local, we remap all its local usages to the local data-block. It means that if e.g. you have assigned a linked material to some local object, then decide to append that same material, currently your already existing local object will be also remapped to use the new local copy (appended version) of the material. I kind of have the feeling that this is not the desired behavior?

Added subscriber: @dfelinto

Added subscriber: @dfelinto

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
(@mont29 is this still even an issue? if not maybe even the patch can be archived)

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided. (@mont29 is this still even an issue? if not maybe even the patch can be archived)

@dfelinto

  • you did not archive this
  • this is a TODO, not a bug! We do not archive those until we actually address them or decide to fully drop them.
  • yes, issue is still here, and needs to be addressed… some day.
@dfelinto - you did not archive this - this is a TODO, not a bug! We do not archive those until we actually address them or decide to fully drop them. - yes, issue is still here, and needs to be addressed… some day.
Member

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

Added subscribers: @ZachHixson, @lichtwerk, @mont29

Added subscribers: @ZachHixson, @lichtwerk, @mont29

Added subscriber: @importsjc

Added subscriber: @importsjc

Hi all,

Just wanted to provide a workaround for this issue. I found that if you save the blender file, that you are appending data from, with a new name (eg "Model_V1.blend" -> "Model_V2.blend") the data will be appended without any linking!

Hope this helps someone and that I provided this feedback in the correct manner.

Hi all, Just wanted to provide a **workaround** for this issue. I found that if you save the blender file, that you are appending data from, with a new name (eg "Model_V1.blend" -> "Model_V2.blend") the data will be appended without any linking! Hope this helps someone and that I provided this feedback in the correct manner.

Added subscriber: @Masterheavy

Added subscriber: @Masterheavy

Thanx Stephen for this workaround - but it actually don't work in the 2.90.1 version I have here - saving the library file with a new name or renaming a copy of the file does not change anything on the append behavior.

Only renaming the collection, before saving a different file seems to work.

Thanx Stephen for this workaround - but it actually don't work in the 2.90.1 version I have here - saving the library file with a new name or renaming a copy of the file does not change anything on the append behavior. Only renaming the collection, before saving a different file seems to work.

Good to know! I'm using 2.90.0. I'll holdoff upgrading until there's a fix/workaround in a newer version.

Good to know! I'm using 2.90.0. I'll holdoff upgrading until there's a fix/workaround in a newer version.

Added subscribers: @Vyach, @TheCharacterhero-4

Added subscribers: @Vyach, @TheCharacterhero-4

Added subscriber: @YegorSmirnov

Added subscriber: @YegorSmirnov
Member

Added subscriber: @craigievar

Added subscriber: @craigievar

This issue was referenced by 3be5ce4aad

This issue was referenced by 3be5ce4aad5e4bbc25474511e56036d6980e1cea

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Member

Added subscriber: @Rawalanche

Added subscriber: @Rawalanche
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
10 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#55629
No description provided.