wrong relative path when saving to startup file #80370

New Issue

MACHIN3 · 2020-09-02T11:24:25+02:00

MACHIN3 commented

2020-09-02 11:24:25 +02:00

System Information
Operating system: Linux-4.15.0-112-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29
Worked: (newest version of Blender that worked as expected)

Short description of error
If you start Blender, add an image texture (with an absolute path) to a material, then save that to the start up file, the path will be wrong and the image won't load when restarting Blender.
This seems to have to do with the save ops Relative Remap, because if you first save somewhere else with Relative Remap disabled, then save to the startup file it works.

So maybe wm.save_homefile shouldn't have Relative Remap enabled?

You can also reproduce this(or similar?) behavior when saving the attached blend file as the startup file.

wrong_relative_path_startup_file.zip

Exact steps for others to reproduce the error

start Blender
add a material and image texture to some object
save as the startup file and restart blender or create a new blend

alternatively:

load the attached blend
save that as your startup file

**System Information** Operating system: Linux-4.15.0-112-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` Worked: (newest version of Blender that worked as expected) **Short description of error** If you start Blender, add an image texture (with an absolute path) to a material, then save that to the start up file, the path will be wrong and the image won't load when restarting Blender. This seems to have to do with the save ops Relative Remap, because if you first save somewhere else with Relative Remap disabled, then save to the startup file it works. So maybe `wm.save_homefile` shouldn't have Relative Remap enabled? You can also reproduce this(or similar?) behavior when saving the attached blend file as the startup file. [wrong_relative_path_startup_file.zip](https://archive.blender.org/developer/F8832062/wrong_relative_path_startup_file.zip) **Exact steps for others to reproduce the error** * start Blender * add a material and image texture to some object * save as the startup file and restart blender or create a new blend alternatively: * load the attached blend * save that as your startup file

MACHIN3 commented

2020-09-02 11:24:25 +02:00

Added subscriber: @MACHIN3

blender-admin commented

2020-09-02 11:24:25 +02:00

#84136 was marked as duplicate of this issue

blender-admin commented

2020-09-02 11:24:25 +02:00

#82737 was marked as duplicate of this issue

blender-admin commented

2020-09-02 11:24:25 +02:00

#80103 was marked as duplicate of this issue

blender-admin commented

2020-09-02 11:24:25 +02:00

#80772 was marked as duplicate of this issue

Richard Antalik commented

2020-09-08 03:41:43 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Johnny Pettersson commented

2020-09-25 20:24:36 +02:00

Added subscriber: @JPO

Richard Antalik commented

2020-09-28 08:14:59 +02:00

Added subscribers: @Pringlez91, @iss

Richard Antalik commented

2020-09-29 14:33:44 +02:00

Added subscriber: @hitprady

Hamed Ghadirian commented

2020-10-02 18:56:10 +02:00

Added subscriber: @Hgh_Phixer

Richard Antalik commented

2020-11-24 19:20:43 +01:00

Added subscribers: @Shiv0r, @StephenSwaney, @nacioss

Hamed Ghadirian commented

2020-11-26 11:54:24 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Hamed Ghadirian closed this issue

2020-11-26 11:54:24 +01:00

Hamed Ghadirian self-assigned this 2020-11-26 11:54:24 +01:00

Hamed Ghadirian commented

2020-11-26 11:54:24 +01:00

I think it's not a bug or something , it just needs a tweak to fix , you need to open blender and append brushes then save over startup.blend (here is the address AppData\Roaming\Blender Foundation\Blender\2.91\config)
now go to file>external data>make all path absolute save again and also do file>defaults>save startup file
now it must be done
you can check it's ok or not by checking address of textures or icon , it must has real address of them not something like "*icon" or "*texture"

I think it's not a bug or something , it just needs a tweak to fix , you need to open blender and append brushes then **save over startup.blend** (here is the address AppData\Roaming\Blender Foundation\Blender\2.91\config) now go to **file>external data>make all path absolute** save again and also do file>defaults>save startup file now it must be done you can check it's ok or not by checking address of textures or icon , it must has real address of them not something like "**icon*" or "**texture*"

Edward Agwi commented

2020-11-26 12:11:22 +01:00

@Hgh_Phixer Dosen't work on the World Node Enviorment Texture Node:

2020-11-26 12-04-33.mp4
It worked just fine in Blender 2.83 and older Versions with open the Texture and than save it as startup file.

@Hgh_Phixer Dosen't work on the World Node Enviorment Texture Node: [2020-11-26 12-04-33.mp4](https://archive.blender.org/developer/F9380114/2020-11-26_12-04-33.mp4) It worked just fine in Blender 2.83 and older Versions with open the Texture and than save it as startup file.

Hamed Ghadirian commented

2020-11-26 12:23:36 +01:00

@Shiv0r
Hi
From my experience, 2 things are so important

Check fake user for your data (I remember I had to do this before in 2.83)
Save your new opened blender not only by save startup from file menu but also save it manually over startup.blend file to make it possible for doing "make all path absolute" (this one is something that I didn't have to do before , Idk it's a bug or just a change in the structure of data information)

Hope this helps

@Shiv0r Hi From my experience, 2 things are so important 1. Check fake user for your data (I remember I had to do this before in 2.83) 2. Save your new opened blender not only by save startup from file menu but also save it manually over startup.blend file to make it possible for doing "make all path absolute" (this one is something that I didn't have to do before , Idk it's a bug or just a change in the structure of data information) Hope this helps

Edward Agwi commented

2020-11-26 12:32:43 +01:00

In #80370#1061909, @Hgh_Phixer wrote:
@Shiv0r
Hi
From my experience, 2 things are so important

Check fake user for your data (I remember I had to do this before in 2.83)

Save your new opened blender not only by save startup from file menu but also save it manually over startup.blend file to make it possible for doing "make all path absolute" (this one is something that I didn't have to do before , Idk it's a bug or just a change in the structure of data information)

Hope this helps

Yes it workes now! I never checked fake user before and it worked just fine. But anyway thanks for the help!

> In #80370#1061909, @Hgh_Phixer wrote: > @Shiv0r > Hi > From my experience, 2 things are so important > 1. Check fake user for your data (I remember I had to do this before in 2.83) > 2. Save your new opened blender not only by save startup from file menu but also save it manually over startup.blend file to make it possible for doing "make all path absolute" (this one is something that I didn't have to do before , Idk it's a bug or just a change in the structure of data information) > > Hope this helps Yes it workes now! I never checked fake user before and it worked just fine. But anyway thanks for the help!

Hamed Ghadirian commented

2020-11-26 12:42:06 +01:00

In #80370#1061916, @Shiv0r wrote:
Yes it workes now! I never checked fake user before and it worked just fine. But anyway thanks for the help!

Happy to hear that, you're welcome.

> In #80370#1061916, @Shiv0r wrote: > Yes it workes now! I never checked fake user before and it worked just fine. But anyway thanks for the help! Happy to hear that, you're welcome.

Richard Antalik commented

2020-11-26 16:54:08 +01:00

Changed status from 'Resolved' to: 'Confirmed'

Richard Antalik reopened this issue

2020-11-26 16:54:08 +01:00

Richard Antalik commented

2020-11-26 16:54:08 +01:00

@Hgh_Phixer The fact that there is workaround doesn't mean that this is not a bug. You also say "it just needs a tweak to fix" sounds like this is valid issue.
I haven't looked at code myself to determine but I will rather let responsible module to check if this is bug or limitation that needs to be documented.

So I am reopening this report, please do not close reports if you are not involved in development or have understanding of underlying code and functionality.

@Hgh_Phixer The fact that there is workaround doesn't mean that this is not a bug. You also say "it just needs a tweak to fix" sounds like this is valid issue. I haven't looked at code myself to determine but I will rather let responsible module to check if this is bug or limitation that needs to be documented. So I am reopening this report, please do not close reports if you are not involved in development or have understanding of underlying code and functionality.

Hamed Ghadirian commented

2020-11-26 17:01:38 +01:00

In #80370#1062205, @iss wrote:
@Hgh_Phixer The fact that there is workaround doesn't mean that this is not a bug. You also say "it just needs a tweak to fix" sounds like this is valid issue.
I haven't looked at code myself to determine but I will rather let responsible module to check if this is bug or limitation that needs to be documented.

So I am reopening this report, please do not close reports if you are not involved in development or have understanding of underlying code and functionality.

Yes, I made a mistake, I wasn't aware of the consequences of what I was doing and I couldn't undo that. Accept my apology and Thanks for your response.

> In #80370#1062205, @iss wrote: > @Hgh_Phixer The fact that there is workaround doesn't mean that this is not a bug. You also say "it just needs a tweak to fix" sounds like this is valid issue. > I haven't looked at code myself to determine but I will rather let responsible module to check if this is bug or limitation that needs to be documented. > > So I am reopening this report, please do not close reports if you are not involved in development or have understanding of underlying code and functionality. Yes, I made a mistake, I wasn't aware of the consequences of what I was doing and I couldn't undo that. Accept my apology and Thanks for your response.

Richard Antalik commented

2020-12-27 20:34:31 +01:00

Added subscriber: @Joany

Hamed Ghadirian was unassigned by Ankit Meel

2021-02-20 11:51:39 +01:00

MACHIN3 commented

2021-06-17 22:26:00 +02:00

Changed status from 'Confirmed' to: 'Resolved'

MACHIN3 closed this issue

2021-06-17 22:26:00 +02:00

MACHIN3 self-assigned this 2021-06-17 22:26:00 +02:00

MACHIN3 commented

2021-06-17 22:26:00 +02:00

I'm closing this as nobody is assigned to it anyway, and as far as I can see it's not an issue in 2.93 anymore.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

wrong relative path when saving to startup file #80370