Cycles Ray Visibility trick for motion blur on objects with animated render-ability is no longer working #65978

Open
opened 2019-06-21 00:37:46 +02:00 by Conrad Dueck · 4 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-19 13:04, hash: 11c9702dd4
Worked: 2.79b, date: 2018-03-22 14:10, hash: f4dc9f9d68b

Short description of error
Cycles motion blur artifacting is a known issue with objects that become renderable while the shutter is open.
A workaround is to transfer the Restrict Render animation to all the Cycles Ray Visibility options at the object level.
This solution worked for us in production on Next Gen using 2.78, but appears to no longer work in 2.80.

Exact steps for others to reproduce the error
The attached file contains 4 planes linked to an animated camera. The 2 on the right are just static. The one on the upper left has animated Restrict Render to reveal the plane on frame 6. The plane on the lower left has Cycles Ray Visibility revealing it on frame 6.
Since all planes are linked to the camera and have no transformation animation, none of them should show any motion blur at all.

Open the attached file in 2.79b and render frame 6 to see that the top left plane appears blurred (it shouldn't) and the lower left plane appears correct.
Open the attached file in 2.80 and render frame 6 to see that both left side planes are now showing the blur artifact.rnd.motion_blur_bug.v0003.blend

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-19 13:04, hash: `11c9702dd4` Worked: 2.79b, date: 2018-03-22 14:10, hash: `f4dc9f9d68b` **Short description of error** Cycles motion blur artifacting is a known issue with objects that become renderable while the shutter is open. A workaround is to transfer the Restrict Render animation to all the Cycles Ray Visibility options at the object level. This solution worked for us in production on Next Gen using 2.78, but appears to no longer work in 2.80. **Exact steps for others to reproduce the error** The attached file contains 4 planes linked to an animated camera. The 2 on the right are just static. The one on the upper left has animated Restrict Render to reveal the plane on frame 6. The plane on the lower left has Cycles Ray Visibility revealing it on frame 6. Since all planes are linked to the camera and have no transformation animation, none of them should show any motion blur at all. Open the attached file in 2.79b and render frame 6 to see that the top left plane appears blurred (it shouldn't) and the lower left plane appears correct. Open the attached file in 2.80 and render frame 6 to see that both left side planes are now showing the blur artifact.[rnd.motion_blur_bug.v0003.blend](https://archive.blender.org/developer/F7396652/rnd.motion_blur_bug.v0003.blend)
Author

Added subscriber: @ConradDueck

Added subscriber: @ConradDueck
Brecht Van Lommel was assigned by Sebastian Parborg 2019-06-21 16:32:20 +02:00
Brecht Van Lommel was unassigned by Dalai Felinto 2019-12-23 16:34:04 +01:00

Added subscriber: @brecht

Added subscriber: @brecht

Added subscriber: @mano-wii

Added subscriber: @mano-wii

I can confirm.
Here is the result in 2.79b:
montion_2.79.exr

Here is the result in 2.82:
montion_2.82.exr

Neither is correct, but 2.82 has one more incorrect case.
It is as if, before being displayed, the object is in the position of the previous frame.

I can confirm. Here is the result in 2.79b: ![montion_2.79.exr](https://archive.blender.org/developer/F8325987/montion_2.79.exr) Here is the result in 2.82: ![montion_2.82.exr](https://archive.blender.org/developer/F8325988/montion_2.82.exr) Neither is correct, but 2.82 has one more incorrect case. It is as if, before being displayed, the object is in the position of the previous frame.
Philipp Oeser removed the
Interest
Render & Cycles
label 2023-02-09 14:00:29 +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
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#65978
No description provided.