Linking path problem #39949
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#39949
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
OS: windows7 64bit
GPU: nvidia quadro k4000
Blender Version
Broken: 2.70a offical release
Worked: 2.69 official release
Short description of error
some weired stuff happening with the linked path
Exact steps for others to reproduce the error
i don't know exactly in which situation this happens but sometimes the linking messes up the path and it assumes that the blend file is in c:\ instead of the correct path.
heres the error i get with 2.7+
all i do is link a object from one scene into a other and then try to reload the scene.
if you need more information please let me know so i can allocate some time to for reproducing this problem.
Changed status to: 'Open'
Added subscriber: @DanielGrauer
Added subscriber: @Sergey
Ofcourse we do need more information, in particular exact steps reproducing the issue, or at least .blend files which worked in 2.69 and doesn't work in 2.70.
Changed status from 'Open' to: 'Archived'
No answer since one week…
finally got time to take the scenes apart so i can submit them here. you will find 2 blend files in the packed file with the same folder structure that i use.
so how to reproduce this issue:
if you manually saved the wire.blend file then either manually reload it or use the "revert"(which should be renamed to reload) option in the file menu to reload the wire.blend file and notice that the skin is not linked anymore and you will find some similar output like i posted in the first post.
linking.zip
Changed status from 'Archived' to: 'Open'
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
The path in Wire.blend is simply broken. it reads library "............\Leg.blend" which is totally outside from your project folder. It should be "........\Leg.blend". Saving files with broken links would lead to data loss for sure.
i dont know how blender refers to such a path, thats why im creating this report.
my savings are exactly in the same file structure as in the files i attached.
if you make such a claim, maybe you can explain to me how i would save a file with a so called "broken" path. because i dont know how to save a file with a path i can not define and doesnt even exist...
"//" means the path is measured relative to the current .blend file. ".." means going to the parent directory. Relative path might become incorrect when you move files around in a file browser or so.
If you didn't change location of the .blend files and run into an issue with wrong paths, that'd be an issue and we'll need to know how to reproduce such situation from scratch.
im pretty sure i did not move any files around because im fully aware that this messes up the relative paths. i will have a look today if maybe a coworker did something which could cause such an issue but i was the only one working on these projects so its unlikely...
i replaced a drive recently but the drive letter and the location of the files is the same again so i dont see how this would break the relative paths.
Well, the thing is. Something breaks relative path for you and we can'r really guess what exactly. We need your collaboration here :)
If we know which step exactly breaks the relative path then we can totally fix the issue.
i understand and i will see if i can allocate some more time or give time to my intern to try and reproduce this somehow.
Added subscriber: @kaspwe2
i did some further testing and the problem happens when i link an object in with a relative path. with absolute path it works fine but as soon as the path is relative i get these funky paths.
i also tested in a old version 2.60.0 and there it works without any problems. i will do some more testing to narrow down the search for the issue.
i also found a old report that sound very similar to my problem, i believe the fix that was done there did not really fix the issue.
old report about same issue:
https://developer.blender.org/T37240
It might be related, maybe not. Really difficult to tell for sure without having exact steps reoproducing the issue.
Also, just for the record, all open movies production files always uses relative path. And the fact that we didn't have issues with paths there means that we REALLY need exact steps which moves linked files from consistent state to a broken one.
we are working on it but its hard to tell what is reproducable on your machines when the issue can be reproduced every time on the file we provide but you tell us you can not reproduce it....
i wrote the exact steps with the attached file structure and i can reproduce it every time so i dont know why this would not happen on any other (windows) system.
Added subscriber: @JasonvanGumster
It seems this issue rises as a result of having .blend files that link to assets in one another. That is, A.blend has an object, "1" that is linked from B.blend. And B.blend has an object, "2" that is linked from A.blend. It's kind of a circular linking scenario.
Assuming that is the culprit, a few follow-up questions (mostly related to the Edit Linked Library addon you're using):
The bug occurs in all three cases under the following circumstances:
Switching blend files with the "Edit linked library" addon.
How to reproduce:
Blender version. 2.70a Hash:
f93bc76
You can do it within the same blender instance. Happens with linked, dupligroup and proxies.
Added subscriber: @lukaszfito
Added subscriber: @Sparazza
Same problem in 2.78a using "Edit Linked Libraries" addon
The problem to me occurs only into Windows OS, not in linux because of the different slash-backslash I think
If you have some issues please submit them as a new report with proper steps reproducing the error.
I saw now that this is closed... really sorry about that, I will open a new one