Boolean - Animation - Viewport works correctly render view doesnt #55672

Open
opened 2018-06-29 05:56:08 +02:00 by Carlo Andreacchio · 20 comments

System Information
Ubuntu 18.04, Win 7 x64

Blender Version
Broken: d53093953f

Short description of error
Booleans dont match between Viewport and Render

Exact steps for others to reproduce the error

  1. Open attached blend file
  2. Preview render (shift z)
  3. Notice the green on top
  4. F12 Render
  5. Notice how the green is no longer there

booleansBug.blend

**System Information** Ubuntu 18.04, Win 7 x64 **Blender Version** Broken: d53093953f8 **Short description of error** Booleans dont match between Viewport and Render **Exact steps for others to reproduce the error** 1. Open attached blend file 2. Preview render (shift z) 3. Notice the green on top 4. F12 Render 5. Notice how the green is no longer there [booleansBug.blend](https://archive.blender.org/developer/F3824329/booleansBug.blend)

Added subscriber: @candreacchio

Added subscriber: @candreacchio

Seems like it has something to do with the animation on the Boolean. Clearing the animation makes the boolean work correctly.

Seems like it has something to do with the animation on the Boolean. Clearing the animation makes the boolean work correctly.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

It has to do with cycles motion blur, 2.79b seems to render fine.
Disabeling motion blur or setting it to Center on Frame seems to render the boolean OK.

It has to do with cycles motion blur, 2.79b seems to render fine. Disabeling motion blur or setting it to `Center on Frame` seems to render the boolean OK.
Member

Added subscriber: @brecht

Added subscriber: @brecht
Member

Sorry about the regression tag, 2.79b with bmesh boolean was also bad...
So, seems to be limitation with bmesh booleans not supporting cycles motion blur in certain scenarios... (e..g. frame 462 in example file is bad, 461 is good, 463 also is...)

Confirming, digging deeper later... maybe @brecht knows right away?

Sorry about the regression tag, 2.79b with bmesh boolean was also bad... So, seems to be limitation with bmesh booleans not supporting cycles motion blur in certain scenarios... (e..g. frame 462 in example file is bad, 461 is good, 463 also is...) Confirming, digging deeper later... maybe @brecht knows right away?

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2018-06-29 14:05:53 +02:00

It's a documented limitation, animated booleans don't work well with motion blur.
https://docs.blender.org/manual/en/dev/render/cycles/settings/scene/render/motion_blur.html

The only solution for now is to disable motion blur for such objects.

It's a documented limitation, animated booleans don't work well with motion blur. https://docs.blender.org/manual/en/dev/render/cycles/settings/scene/render/motion_blur.html The only solution for now is to disable motion blur for such objects.

@brecht disabling the motion blur for both objects does not fix the issue. I have reuploaded the file, with both objects having disabled motionblur yet the bug persists

booleansBug2.blend

@brecht disabling the motion blur for both objects does not fix the issue. I have reuploaded the file, with both objects having disabled motionblur yet the bug persists [booleansBug2.blend](https://archive.blender.org/developer/F3831629/booleansBug2.blend)

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Added subscriber: @mont29

Added subscriber: @mont29

Can confirm that even though mblur is disabled for both operand objects, result in render is wrong. You have to disable mblur for whole Cycles (in its render settings) to get correct render.

Can confirm that even though mblur is disabled for both operand objects, result in render is wrong. You have to disable mblur for whole Cycles (in its render settings) to get correct render.

Added subscriber: @Darksunrise

Added subscriber: @Darksunrise
Brecht Van Lommel was unassigned by Dalai Felinto 2019-12-23 16:36:08 +01:00

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Sybren A. Stüvel self-assigned this 2020-02-04 16:13:27 +01:00

Given the comments by @brecht and @mont29 above, I'm closing this as a known limitation.

Given the comments by @brecht and @mont29 above, I'm closing this as a known limitation.

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'

To me it seems a bug, given that my comment was mistaken.

To me it seems a bug, given that my comment was mistaken.
Sybren A. Stüvel removed their assignment 2020-02-11 17:32:47 +01:00
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

With the Exact boolean method, the render has the same green area as the viewport render, so maybe we can call this issue resolved?

However, I do get correct results with EEVEE even with the "Fast" boolean method, so this probably points to an issue with Cycles.

With the [Exact ](https://wiki.blender.org/wiki/Reference/Release_Notes/2.91/Modeling#Boolean) boolean method, the render has the same green area as the viewport render, so maybe we can call this issue resolved? However, I do get correct results with EEVEE even with the "Fast" boolean method, so this probably points to an issue with Cycles.
Philipp Oeser removed the
Interest
Render & Cycles
label 2023-02-09 13:58:31 +01:00
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
7 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#55672
No description provided.