Cycles destroys an existing texture image while baking to a new image #106146

New Issue

kursad k · 2023-03-26T06:03:27+02:00

kursad k commented

2023-03-26 06:03:27 +02:00

System Information
Operating system: Windows 11
Graphics card: rtx 2070

Blender Version
Broken: 51bc44420b

Short description of error

Blender seems to destroy or empty an existing texture in a multi material setup while baking to a new image.

Exact steps for others to reproduce the error
load the attached file

select the BAKE material

select the BAKE image node

Render Props -> Bake ( it is already setup)

Pay attention to the viewport to see that one of the textures turn black, and the BAKE texture is still black

You can try variations as in putting the BAKE node in other materials however the result seems to be the same failed bake.

**System Information** Operating system: Windows 11 Graphics card: rtx 2070 **Blender Version** Broken: 51bc44420b89 **Short description of error** Blender seems to destroy or empty an existing texture in a multi material setup while baking to a new image. **Exact steps for others to reproduce the error** load the attached file select the BAKE material select the BAKE image node Render Props -> Bake ( it is already setup) Pay attention to the viewport to see that one of the textures turn black, and the BAKE texture is still black You can try variations as in putting the BAKE node in other materials however the result seems to be the same failed bake.

_25032023_2250_19.zip

19 MiB

blender_Imrg6rmblT.jpg

1.8 MiB

kursad k added the

labels 2023-03-26 06:03:27 +02:00

Daniel Bystedt commented

2023-03-26 09:39:21 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18

Blender Version
Broken: version: 3.6.0 Alpha, branch: main, commit date: 2023-03-24 22:22, hash: 51bc44420b89
Worked: None as far as I know.

I can confirm that this bug shows up on my computer as well.

The model has multiple materials assigned to it (assigned to different faces). It seems that cycles is not understanding that the target bake image is the selected image in the active material. Instead, cycles is also baking to the SOURCE images

The issue is fixed by copy pasting the target image (BAKE) into all materials and making sure that image node is the active node in each material.

I get this issue on Blender 3.2 so it seems to be an old bug that hasn't been discovered yet.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18 **Blender Version** Broken: version: 3.6.0 Alpha, branch: main, commit date: 2023-03-24 22:22, hash: `51bc44420b89` Worked: None as far as I know. I can confirm that this bug shows up on my computer as well. The model has multiple materials assigned to it (assigned to different faces). It seems that cycles is not understanding that the target bake image is the selected image in the active material. Instead, cycles is also baking to the SOURCE images The issue is fixed by copy pasting the target image (BAKE) into all materials and making sure that image node is the active node in each material. I get this issue on Blender 3.2 so it seems to be an old bug that hasn't been discovered yet.

❤️ 1

Daniel Bystedt added

and removed

labels 2023-03-26 09:39:59 +02:00

kursad k changed title from ~~Cycles destroys and existing texture image while baking to a new image~~ to Cycles destroys an existing texture image while baking to a new image

2023-03-26 09:42:52 +02:00

kursad k commented

2023-03-26 09:46:30 +02:00

@DanielBystedt thanks for testing it out. I actually hit this bug long time ago but I kept going around it and using object to object bake to get what I need. I just ran out of patience this time and I felt like this needed real attention. Like you pointed out, Cycles does not seem to understand the multi material structure properly and its internal assumptions about what is what when it comes to the target bake node breaks down.

It is interesting that it destroys one of the source images in the source materials. That is peculiar because no source images are selected in those materials, and it does not seem to destroy all, only one of the images is cleared out during bake.

@DanielBystedt thanks for testing it out. I actually hit this bug long time ago but I kept going around it and using object to object bake to get what I need. I just ran out of patience this time and I felt like this needed real attention. Like you pointed out, Cycles does not seem to understand the multi material structure properly and its internal assumptions about what is what when it comes to the target bake node breaks down. It is interesting that it destroys one of the source images in the source materials. That is peculiar because no source images are selected in those materials, and it does not seem to destroy all, only one of the images is cleared out during bake.

Pratik Borhade added the

Module

Render & Cycles

label 2023-03-26 11:27:13 +02:00

Philipp Oeser commented

2023-06-06 13:38:44 +02:00

The model has multiple materials assigned to it (assigned to different faces). It seems that cycles is not understanding that the target bake image is the selected image in the active material. Instead, cycles is also baking to the SOURCE images

Cycles does not seem to understand the multi material structure properly and its internal assumptions about what is what when it comes to the target bake node breaks down.

Stopping by here and asking myself: "there are situations where you want to bake to multiple images in multiple materials, no?" I think if we restrict baking to just the active image in the active material, we loose the ability to quickly do this?
The code clearly goes over all materials and gets the respective active image from that.

Now, how can we exclude a particular image from being baked to? How can it not be the active image? As you already noticed, there needs to be another image that was made active, you cannot just deselect the node and expect it to not be active anymore.
This is truly an issue, this is also true for syncing between the node editor and the image editor.
One way to improve this situation is to make "changing the active image canvas in the node editor" an explicit obvious action, see proposal in #103636. This way, it would be more clear which image is baked to (and hopefully we can have a way to not have any active image -- will ask about this again in #103636).

Do you think this would solve the issue here?

>The model has multiple materials assigned to it (assigned to different faces). It seems that cycles is not understanding that the target bake image is the selected image in the active material. Instead, cycles is also baking to the SOURCE images >Cycles does not seem to understand the multi material structure properly and its internal assumptions about what is what when it comes to the target bake node breaks down. Stopping by here and asking myself: "there are situations where you want to bake to multiple images in multiple materials, no?" I think if we restrict baking to just the active image in the **active** material, we loose the ability to quickly do this? The code clearly goes over all materials and gets the respective active image from that. Now, how can we exclude a particular image from being baked to? How can it **not** be the active image? As you already noticed, there needs to be **another** image that was made active, you cannot just deselect the node and expect it to not be active anymore. This is truly an issue, this is also true for syncing between the node editor and the image editor. One way to improve this situation is to make "changing the active image canvas in the node editor" an explicit obvious action, see proposal in #103636. This way, it would be more clear which image is baked to (and hopefully we can have a way to not have any active image -- will ask about this again in #103636). Do you think this would solve the issue here?

Philipp Oeser referenced this issue

2023-06-06 13:43:10 +02:00

Image syncing between Editors via active image canvas #103636

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

Cycles destroys an existing texture image while baking to a new image #106146