Page MenuHome

Unsaved baked image cannot be used in node editors.
Closed, ResolvedPublic

Description

System Information
Win8.1 64bit | GTX680

Blender Version
Broken: 2.72.2 409043c

Short description of error
When trying to use the baked image within Blender, say, using it in Node editor, it just turns back to the initial look.

Exact steps for others to reproduce the error

  1. Create a blank image;
  2. Bake the default cube using this image;
  3. After baking, try using it in Node editor.

PS: Perhaps similar issue to this one? https://developer.blender.org/T42008 FYI. Thanks.

Event Timeline

Leon Cheung (leon_cheung) set Type to Bug.
Leon Cheung (leon_cheung) created this task.
Leon Cheung (leon_cheung) raised the priority of this task from to Needs Triage by Developer.

I can't reproduce this. Please attach a test file, this could well depend on specifics such as which node type you use, which render engine etc.

Have you tried this with a recent build from https://builder.blender.org ? Although i can't reproduce it with 2.72 either ...

I don't think a test file would help, because if I make a test file, the image has to be saved, but the problem only occurs for UNSAVED image... I think I may try to make a screencast to show it better. asap.

Julian Eisel (Severin) triaged this task as Confirmed, Medium priority.

Mhh, seems to me the issue appears after using drag & drop. Looks like it's using the original image which causes the generated one to be overwritten :/

This issue is very similar to other issues such as T41598 or T41762. Basically any operation that clears the caches of an image will cause regeneration from a file or in the case of a generated image, flood filling with the generated value.

I do have a patch that explicitly creates a file when we generate an image instead, but it might be a bit of a controversial change.

@Antony Riakiotakis (psy-fi), why not save it in /temp/ by default?
Anyway, not sure if it's worth having two reports open that have the same root (event though the symptom is different)?

@Antony Riakiotakis (psy-fi), i'm not really a fan of that patch. The existing pipeline is to be revisited and cleaned up where needed. The patch just adds extra confusion.