Setting filepath of an image reloads it, which breaks all kind of generated content (including baking). #43985

New Issue

Vilem Duha · 2015-03-13T15:39:50+01:00

Vilem Duha commented

2015-03-13 15:39:50 +01:00

System Information
Operating system and graphics card

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional): not sure if ever.

Short description of error
I tried to make some advanced baking script.
I hit this error, where setting the file path AFTER baking erases the image pixels to black. interesting is, that when I set the filepath before, it works.

Exact steps for others to reproduce the error
open file, run first script on upper left - that simply bakes into the image.
run the second script, which tries to set name and save. see the blackness!

bakebug.blend

**System Information** Operating system and graphics card **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional): not sure if ever. **Short description of error** I tried to make some advanced baking script. I hit this error, where setting the file path AFTER baking erases the image pixels to black. interesting is, that when I set the filepath before, it works. **Exact steps for others to reproduce the error** open file, run first script on upper left - that simply bakes into the image. run the second script, which tries to set name and save. see the blackness! [bakebug.blend](https://archive.blender.org/developer/F150571/bakebug.blend)

Vilem Duha commented

2015-03-13 15:39:50 +01:00

Changed status to: 'Open'

Dalai Felinto was assigned by Vilem Duha

2015-03-13 15:39:50 +01:00

Vilem Duha commented

2015-03-13 15:39:50 +01:00

Added subscriber: @VilemDuha

Bastien Montagne commented

2015-03-13 16:10:14 +01:00

Added subscribers: @ideasman42, @Sergey, @mont29

Bastien Montagne commented

2015-03-13 16:10:14 +01:00

Setting the name of an image through RNA (i.e. python) forces reloading of that image (and since it does not yet exists on disc, it becomes black).

Campbell or Sergey, what do you think about adding an option to 'save' image func to specify a path?

Setting the name of an image through RNA (i.e. python) forces reloading of that image (and since it does not yet exists on disc, it becomes black). Campbell or Sergey, what do you think about adding an option to 'save' image func to specify a path?

Bastien Montagne changed title from ~~Script-baked image gets erased when attempting to set filepath~~ to Setting filepath of an image reloads it, which breaks all kind of generated content (including baking).

2015-03-13 16:13:00 +01:00

Dalai Felinto was unassigned by Bastien Montagne

2015-03-13 16:13:00 +01:00

Bastien Montagne commented

2015-03-13 16:13:00 +01:00

Added subscriber: @dfelinto

Vilem Duha commented

2015-03-15 17:43:14 +01:00

Just to reply to your comment, not sure if it's a typo, but we talk about setting filepath, not name... although I didn't test if renaming does the same.

Bastien Montagne commented

2015-03-15 18:13:23 +01:00

Yeah, sure (issue being, 'filepath' var in C struct is actually called 'name' - talking about confusing naming :/ ).

Sergey Sharybin commented

2015-03-15 22:12:43 +01:00

Modifying filepath will re-load the image because you might have point it to an existing file. In order to modify file path to save the image after the bake you need to use filepath_raw.

Modifying filepath will re-load the image because you might have point it to an existing file. In order to modify file path to save the image after the bake you need to use `filepath_raw`.

Campbell Barton commented

2015-03-16 03:45:00 +01:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2015-03-16 03:45:00 +01:00

Campbell Barton self-assigned this 2015-03-16 03:45:00 +01:00

Campbell Barton commented

2015-03-16 03:45:00 +01:00

closing since this is known/intended behavior. Scripts can use filepath_raw.

closing since this is known/intended behavior. Scripts can use `filepath_raw`.

Vilem Duha commented

2015-03-18 17:16:39 +01:00

This could be called at least misleading, or very confusing behavior. The reloading is really not clear at all because it's not in documentation of the filepath prop, only mentioned in filepath_raw.... Also, what sense does it have to load an image which does not exist as a black image? shouldn't it try to load the image and when the file does not exist, then not do anything? Or, when the image path was same before, and I set the path 'to be sure' in the script, then this also has no logic at all..
But at least It's now clear to me...

This could be called at least misleading, or very confusing behavior. The reloading is really not clear at all because it's not in documentation of the filepath prop, only mentioned in filepath_raw.... Also, what sense does it have to load an image which does not exist as a black image? shouldn't it try to load the image and when the file does not exist, then not do anything? Or, when the image path was same before, and I set the path 'to be sure' in the script, then this also has no logic at all.. But at least It's now clear to me...

Vilem Duha commented

2015-03-18 18:23:29 +01:00

Ok, so I did more tests. And, filepath_raw actually doesn't work either. It doesn't erase the image changes, but the image doesn't get saved WITH the changes... at least in the testfile I sent. I totally understand it's good to lower the number of bugs before the release, but doing it this way isn't nice to users who spend time reporting the bugs....
should I report a new one?

Ok, so I did more tests. And, filepath_raw actually doesn't work either. It doesn't erase the image changes, but the image doesn't get saved WITH the changes... at least in the testfile I sent. I totally understand it's good to lower the number of bugs before the release, but doing it this way isn't nice to users who spend time reporting the bugs.... should I report a new one?

Campbell Barton commented

2015-03-19 02:27:38 +01:00

@VilemDuha - report a new bug is best,
However we've used both filepath(_raw) quite a lot, I would imagine if they were buggy we would have found before?.

This is how filepath_raw is intended to work:

Create new image
Edit pixels
Set filepath_raw (which wont reload)
Save the image Image.save

Nevertheless if you think you found a bug it would be really good to investigate before 2.74 release.

@VilemDuha - report a new bug is best, However we've used both filepath(_raw) quite a lot, I would imagine if they were buggy we would have found before?. This is how filepath_raw is intended to work: - Create new image - Edit pixels - Set `filepath_raw` (which wont reload) - Save the image `Image.save` Nevertheless if you think you found a bug it would be really good to investigate before 2.74 release.

Vilem Duha commented

2015-03-19 09:43:22 +01:00

well, I just replaced filepath with filepath_raw command in the example file. i will probably test a bit more and report then.

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

Setting filepath of an image reloads it, which breaks all kind of generated content (including baking). #43985