Edit Linked Library error, not using correct relative path #69446
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#69446
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?
System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70
Blender Version
Broken: version: 2.81 (sub 1), branch: master, commit date: 2019-08-13 11:31, hash:
blender/blender@6f9cbbc8ec
Worked: (optional)
Addon Information
Name: Edit Linked Library (0, 9, 1)
Author: Jason van Gumster (Fweeb), Bassam Kurdali, Pablo Vazquez, Rainer Trummer
Short description of error
When you open a library from the addon and then load a texture, it uses a relative path to the initial scene and not the one we intend to modify.
The relative addressing of textures does not seem to work well, because the addon seems to use the path of the "parent" file that contains the linked object and not the object we are modifying.
Added subscriber: @ideasfijas
Added subscriber: @Harvester
This issue seems related to #67111. Perhaps they could be merged.
Added subscriber: @lichtwerk
@Harvester: thx for pointing out, will merge...
Closed as duplicate of #67111