Project to tag bugs that are release blockers and other tasks that are planned to be included in the Blender 2.70 release.
Fri, Dec 7
Seems like a duplicate of T57655
Wed, Dec 5
Not sure if other software is comparable 1:1 here (I assume they all have different implementations).
Tue, Dec 4
Sep 16 2018
Aug 23 2018
Am sorry, but we cannot do anything here really, this is a problem with your GPU/OS/Driver setup… You can try a different driver version (newer and/or older), or try to tweak your drivers' settings, and/or Blender's OpenGL settings…
Apr 6 2016
Please avoid creating empty tasks.
Jun 11 2015
May 18 2015
Feb 19 2015
@Sebastian Koenig (sebastian_k), it is awkward.
Feb 18 2015
I still find this a bit fuzzy.
The checkbox for relative/absolute is available still, so as a user I would expect that it works. Especially because in all image related buttons in Cycles the textbox to change the source path is not available, only from inside the image editor.
Feb 17 2015
Closed by commit rB5115e8624602.
The logic for exists is:
I found it.
The cause of the problem is in image_ops.c line 1090:
Hmm, it seems there are some strange things going on. If I open your test file, I indeed have the error. But if I open another image, it does have a relative path. Also with other files. If I completely remove the image (shift + click on the X), save the file and re-open, I can also open the image with relative path.
It seems this error came back somehow.
I am getting the exact same broken behavior in 2.73.8 (86a2e9d).
Here's a sample folder with image and blendfile. Notice the image is loaded with relative path. However, if i open the same image with alt+o or the open image button, it gets an absolut path, even though the relative path checkbox is activated.