Combined Bake uses the wrong target image when there are multiple materials with image textures. #50836

Closed
opened 2017-03-02 18:19:46 +01:00 by Bill Hails · 6 comments

System Information
macOS 10.12.3 NVIDIA GeForce GT 755M 1024 MB

Blender Version
Broken: 2.78b 2017-02-03 16:54 hash 9cb21a1
Worked: ?

Short description of error
Blender does not seem to find the correct target image for a bake if there are multiple materials with image textures.

Exact steps for others to reproduce the error
A mesh with several materials assigned, one per face.
Each material has an image texture.
An additional blank bake target image
Each material also has a second, unconnected image texture for that target bake, and that image texture is selected in each material.

Going to the render tab and clicking "Bake" (a combined bake) produces a circular dependency error from one of the image textures to the object, and the image texture in question is overwritten by the bake, even though each material has a second image texture for the bake, and that second target image texture is selected in each material.

Bug.blend

**System Information** macOS 10.12.3 NVIDIA GeForce GT 755M 1024 MB **Blender Version** Broken: 2.78b 2017-02-03 16:54 hash 9cb21a1 Worked: ? **Short description of error** Blender does not seem to find the correct target image for a bake if there are multiple materials with image textures. **Exact steps for others to reproduce the error** A mesh with several materials assigned, one per face. Each material has an image texture. An additional blank bake target image Each material also has a second, unconnected image texture for that target bake, and that image texture is selected in each material. Going to the render tab and clicking "Bake" (a combined bake) produces a circular dependency error from one of the image textures to the object, and the image texture in question is overwritten by the bake, even though each material has a second image texture for the bake, and that second target image texture is selected in each material. [Bug.blend](https://archive.blender.org/developer/F500411/Bug.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @billh-3

Added subscriber: @billh-3
Author

I dug a little deeper, although the target images appeared to be the only thing selected in each material, when I went through each material and deselected everything with 'a' then selected the target, it works now.

So I think there may still be a bug in what blender is showing as selected within a material, but it's not quite the bug I reported.

I dug a little deeper, although the target images appeared to be the only thing selected in each material, when I went through each material and deselected everything with 'a' then selected the target, it works now. So I think there may still be a bug in what blender is showing as selected within a material, but it's not quite the bug I reported.

Added subscriber: @dfelinto

Added subscriber: @dfelinto

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Dalai Felinto self-assigned this 2017-05-15 14:53:42 +02:00

The problem is that the active node of the materials is not the "Bake" image texture. You can see that if you look at the "properties" panel in the nodetree and see which node is shown there.

What I believe happened is that you were not "click" selecting the bake not but using a different selection method (e.g., border select). Which in turn doesn't change the active node, just the selection.

I'll close now. If you manage to reproduce this from scratch while using click select to pick the active node, feel free to re-report it (though as a nodetree bug, not as cycles bake).

Thanks for the report.

The problem is that the active node of the materials is not the "Bake" image texture. You can see that if you look at the "properties" panel in the nodetree and see which node is shown there. What I believe happened is that you were not "click" selecting the bake not but using a different selection method (e.g., border select). Which in turn doesn't change the active node, just the selection. I'll close now. If you manage to reproduce this from scratch while using click select to pick the active node, feel free to re-report it (though as a nodetree bug, not as cycles bake). Thanks for the report.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#50836
No description provided.