Bake with Cage fails when target mesh has a modifier and is in a different scene to the Cage #71065

Closed
opened 2019-10-24 09:42:21 +02:00 by Netherby · 7 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449

Short description of error
When a mesh has a modifier on it and is used as a bake target with a Cage object and that Cage object is in a different scene (but has the same modifier), the bake will fail reporting that the objects do not have the same number of sides. When the Cage and target are in the same scene it works as expected.

Also, separate to this issue but connected: The Cage object will have its Render visibility left disabled after bake (regardless of success or failure) when ever its not in the same scene.

Exact steps for others to reproduce the error

  • Add a Cube, add a Mirror modifier to it.
  • Create a new scene.
  • Add a Cube and a Cone to the new scene.
  • Give this Cube a Mirror modifier with the same default settings as the previous Cube.
  • Give the Cube a material with an image texture target for the bake.
  • Set Render to Cycles, open Bake panel and choose 'Selected to active' and then check the 'Cage' option.
  • Pick the original Cube in the first scene as the Cage object.
  • Select the Cone and holding shift select the Cube.
  • Hit Bake.

It will say that the cage is invalid as the objects have different number of sides. If you now check back in the first scene, the Cube there will have had its Render visibility turned off.

Now delete or disable for render the mirror modifier on the target cube and repeat the bake. It will now work, even though the cage still has the modifier (it should NOT work in this configuration). The Cage object will again have its Render visibility disabled regardless of its starting state.

I have attached a simple demo broken_cage_bake.blend with three scenes:
1)base scene - has all objects in it and works as expected.
2)broken - has a Cube with mirror mod and a Cone with the Cube from scene 1 set as cage, shows error.
3)working - same scene as 2, but mirror mod is removed. Look at base scene after bake and see how the cage has been left hidden for render. Note that while this works, it shouldn't be working and should report that the meshs don't match!

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` **Short description of error** When a mesh has a modifier on it and is used as a bake target with a Cage object and that Cage object is in a different scene (but has the same modifier), the bake will fail reporting that the objects do not have the same number of sides. When the Cage and target are in the same scene it works as expected. Also, separate to this issue but connected: The Cage object will have its Render visibility left disabled after bake (regardless of success or failure) when ever its not in the same scene. **Exact steps for others to reproduce the error** - Add a Cube, add a Mirror modifier to it. - Create a new scene. - Add a Cube and a Cone to the new scene. - Give this Cube a Mirror modifier with the same default settings as the previous Cube. - Give the Cube a material with an image texture target for the bake. - Set Render to Cycles, open Bake panel and choose 'Selected to active' and then check the 'Cage' option. - Pick the original Cube in the first scene as the Cage object. - Select the Cone and holding shift select the Cube. - Hit Bake. It will say that the cage is invalid as the objects have different number of sides. If you now check back in the first scene, the Cube there will have had its Render visibility turned off. Now delete or disable for render the mirror modifier on the target cube and repeat the bake. It will now work, even though the cage still has the modifier (it should NOT work in this configuration). The Cage object will again have its Render visibility disabled regardless of its starting state. I have attached a simple demo [broken_cage_bake.blend](https://archive.blender.org/developer/F7852726/broken_cage_bake.blend) with three scenes: 1)base scene - has all objects in it and works as expected. 2)broken - has a Cube with mirror mod and a Cone with the Cube from scene 1 set as cage, shows error. 3)working - same scene as 2, but mirror mod is removed. Look at base scene after bake and see how the cage has been left hidden for render. Note that while this works, it shouldn't be working and should report that the meshs don't match!
Author

Added subscriber: @JerahmyPocott

Added subscriber: @JerahmyPocott

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

Is this still a problem in the latest builds?
https://builder.blender.org/download/

I cannot reproduce the problem.
But I probably misunderstood the steps to reproduce it.

Is this still a problem in the latest builds? https://builder.blender.org/download/ I cannot reproduce the problem. But I probably misunderstood the steps to reproduce it.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Changed status from 'Needs User Info' to: 'Resolved'

Changed status from 'Needs User Info' to: 'Resolved'
Aaron Carlisle self-assigned this 2020-02-18 19:25:19 +01:00
Member

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
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
3 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#71065
No description provided.