Cycles motion blur does not interpolate correctly #107482

Open
opened 2023-04-30 17:28:41 +02:00 by Max Mustermann · 7 comments

System Information
Operating system: Fedora Linux (Wayland)
Graphics card: AMD GPU (but Cycles renders on AMD CPU)

Blender Version
Broken: 3.5.0
Worked: never? (same results till 2.83)

Cycles motion blur interpolation is strange.
It's very noticeable when an object or the camera is bound to a constraint and the motion blur shutter is set very high (like 60 frames). Cycles motion blur will interpolate it wrong. I will include pictures and .blend files

Exact steps for others to reproduce the error

  • Open attached .blend file
  • Render the first frame with EEVEE and Cycles and compare the motion blur.
**System Information** Operating system: Fedora Linux (Wayland) Graphics card: AMD GPU (but Cycles renders on AMD CPU) **Blender Version** Broken: 3.5.0 Worked: never? (same results till 2.83) Cycles motion blur interpolation is strange. It's very noticeable when an object or the camera is bound to a constraint and the motion blur shutter is set very high (like 60 frames). Cycles motion blur will interpolate it wrong. I will include pictures and .blend files **Exact steps for others to reproduce the error** - Open attached .blend file - Render the first frame with EEVEE and Cycles and compare the motion blur.
Max Mustermann added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-04-30 17:28:42 +02:00
Iliya Katushenock added the
Interest
Cycles
label 2023-04-30 17:37:29 +02:00
Member

Thanks for the report. Can confirm.

Thanks for the report. Can confirm.
Pratik Borhade added
Module
Render & Cycles
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-05-01 12:43:33 +02:00

That's because you increased the sub-stepping for Eevee but not Cycles.

That's because you increased the sub-stepping for Eevee but not Cycles.
Author

That's right. If you can show me where I can do that for Cycles I will change the title of this bug report, but the motion blur in my example has a range of 60 frames.
If Cycles really operates with a sub-step system like Evee does, shouldn't Cycles have at least one step for every frame by default?

That's right. If you can show me where I can do that for Cycles I will change the title of this bug report, but the motion blur in my example has a range of 60 frames. If Cycles really operates with a sub-step system like Evee does, shouldn't Cycles have at least one step for every frame by default?
https://docs.blender.org/manual/en/latest/render/cycles/object_settings/object_data.html#bpy-types-cyclesobjectsettings-use-motion-blur
Author

Thank You!

I'm unsure what to do with this issue.
On the one hand it seems like user error, but it's also unexpected of both Evee and Cycles to not have a step for every frame in the shutter range by default.
I assume a global setting for motion blur like in Evee is not possible for Cycles?
Should cameras (and objects?) have a higher step value by default? The difference seems to be 0.01MB in memory usage during rendering when using 7 steps instead of 1 step.

l will leave the decision to someone else.

Thank You! I'm unsure what to do with this issue. On the one hand it seems like user error, but it's also unexpected of both Evee and Cycles to not have a step for every frame in the shutter range by default. I assume a global setting for motion blur like in Evee is not possible for Cycles? Should cameras (and objects?) have a higher step value by default? The difference seems to be 0.01MB in memory usage during rendering when using 7 steps instead of 1 step. l will leave the decision to someone else.
Author

To be fair with 10 000 individual objects (cubes) at 7 steps, the extra memory usage is 94MB.

To be fair with 10 000 individual objects (cubes) at 7 steps, the extra memory usage is 94MB.
Author

I can imagine a default value of 3 steps or more for new objects delivering a much more seamless experience with minimal impact on memory usage.

I can imagine a default value of 3 steps or more for new objects delivering a much more seamless experience with minimal impact on memory usage.
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#107482
No description provided.