File Linking Issues #118845

New Issue

AlbertoZimino · 2024-02-28T11:41:39+01:00

AlbertoZimino commented

2024-02-28 11:41:39 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.20

Blender Version
Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a
Worked: (newest version of Blender that worked as expected)

I recently had some issues working with external linked files.
Our company is working on a game that will be issued for the Oculus Quest 2.0 and 3.0
Leading a team composed of professionals working on different aspects of the main environment, it became really useful to split each scene into smaller files and link them in another file.
We are doing that also for all the common objects to be placed over the main scene as well for every geometry node tree.

Someone didn't follow accurately the production document, relevant to the scene setup, its configuration and the version to be used (which is 3.6 + some different number) for that project.
Also, the folder paths and names have changed over time.
We are using different devices: PC workstations, Laptops, and Macs.

I'm now having problems relocating the files, especially the ones containing the geometry nodes tools. Sometimes they are getting duplicated instead of replaced, leaving a corrupted icon next to the older one. In the worst cases, this is also messing around with the exposed parameter, making things look different since the last save.

I don't get what is causing the issue, this is why I call it a "bug" and the outcome is sometimes different in other devices.

Inspecting all the objects and inputting all the right parameters is a waste of time and I don't want to relate to a pipeline that has issues or it's unreliable.

Can you please have some suggestions on how to completely avoid the issue?
We are now doing some tests to see if having the same Blender ver. and Folder Path would be a solution, but this will not be completely safe in the future.

Thank you

How to reproduce the issue: create an external file with a node tree, link it to a new scene, use it then resave the scene in another location, HDD, pc.

switch to a slightly different Blender version 3.6.2, 3.6.6, 3.6.8, 3.6 LTS

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.20 **Blender Version** Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: `e53e55951e7a` Worked: (newest version of Blender that worked as expected) I recently had some issues working with external linked files. Our company is working on a game that will be issued for the Oculus Quest 2.0 and 3.0 Leading a team composed of professionals working on different aspects of the main environment, it became really useful to split each scene into smaller files and link them in another file. We are doing that also for all the common objects to be placed over the main scene as well for every geometry node tree. Someone didn't follow accurately the production document, relevant to the scene setup, its configuration and the version to be used (which is 3.6 + some different number) for that project. Also, the folder paths and names have changed over time. We are using different devices: PC workstations, Laptops, and Macs. I'm now having problems relocating the files, especially the ones containing the geometry nodes tools. Sometimes they are getting duplicated instead of replaced, leaving a corrupted icon next to the older one. In the worst cases, this is also messing around with the exposed parameter, making things look different since the last save. I don't get what is causing the issue, this is why I call it a "bug" and the outcome is sometimes different in other devices. Inspecting all the objects and inputting all the right parameters is a waste of time and I don't want to relate to a pipeline that has issues or it's unreliable. Can you please have some suggestions on how to completely avoid the issue? We are now doing some tests to see if having the same Blender ver. and Folder Path would be a solution, but this will not be completely safe in the future. Thank you How to reproduce the issue: create an external file with a node tree, link it to a new scene, use it then resave the scene in another location, HDD, pc. switch to a slightly different Blender version 3.6.2, 3.6.6, 3.6.8, 3.6 LTS

Link Issue.PNG

31 KiB