Motion blur acting up. #46404

Closed
opened 2015-10-07 10:05:12 +02:00 by Braeden · 12 comments

System Information
Windows8 x64 and Dual GTX 670s (but the problem still exists on CPU rendering - i7-3930k)

Blender Version
Broken: (example: 2.76 RC3 fb78f6d
Worked: Not sure, using most recent version of Blender RC3

Strange artifacts/displaced vertices in mesh when motion blur is enabled (images attached). The clean one is without MB.

2015-10-07 03_57_17-.png

2015-10-07 03_56_44-.png

I have animated a paper airplane being folded (armatures and shape keys), it randomly seems to happen in random spots. Only happens with motion blur enabled.

**System Information** Windows8 x64 and Dual GTX 670s (but the problem still exists on CPU rendering - i7-3930k) **Blender Version** Broken: (example: 2.76 RC3 fb78f6d Worked: Not sure, using most recent version of Blender RC3 Strange artifacts/displaced vertices in mesh when motion blur is enabled (images attached). The clean one is without MB. ![2015-10-07 03_57_17-.png](https://archive.blender.org/developer/F243050/2015-10-07_03_57_17-.png) ![2015-10-07 03_56_44-.png](https://archive.blender.org/developer/F243051/2015-10-07_03_56_44-.png) I have animated a paper airplane being folded (armatures and shape keys), it randomly seems to happen in random spots. Only happens with motion blur enabled.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @BraedenLaverty

Added subscriber: @BraedenLaverty
Author

I am using a mirror modifier and I found that by disabling the "merge" checkbox, this problem doesn't happen anymore... odd either way. Luckily I didnt need to use the merge setting for this, but hopefully this can be sorted out some how.

I am using a mirror modifier and I found that by disabling the "merge" checkbox, this problem doesn't happen anymore... odd either way. Luckily I didnt need to use the merge setting for this, but hopefully this can be sorted out some how.

Added subscriber: @Sergey

Added subscriber: @Sergey

It's really hard to tell what's going on there without having .blend file which demonstrates the issue.

Current guess is that with merge option either topology of the mesh change s cross the frames or order of output is not determenistic in certain cicrumstances which will surely confuse deformation motion blur.

In order to give any more definitive answer here we need .blend file.

It's really hard to tell what's going on there without having .blend file which demonstrates the issue. Current guess is that with merge option either topology of the mesh change s cross the frames or order of output is not determenistic in certain cicrumstances which will surely confuse deformation motion blur. In order to give any more definitive answer here we need .blend file.
Author

Attached is the blend file. Frame 14 seems to be the only one that this happens to. To be fair to blender, the mesh is not great, I was just doing a test for something and wasn't super careful with it... but it just seemed odd that it would suddenly just do that during motion blur, seems like a bug.

paper_test.blend

Hope this helps. Let me know if I can do anything else.

Thanks!

Attached is the blend file. Frame 14 seems to be the only one that this happens to. To be fair to blender, the mesh is not great, I was just doing a test for something and wasn't super careful with it... but it just seemed odd that it would suddenly just do that during motion blur, seems like a bug. [paper_test.blend](https://archive.blender.org/developer/F243578/paper_test.blend) Hope this helps. Let me know if I can do anything else. Thanks!

Added subscriber: @brecht

Added subscriber: @brecht

The problem is indeed that the topology changes during motion blur, which is not supported. Cycles only checks that the number of vertices is the same, so it doesn't detect that the topology changes. But if it would have detected that you'd still have the problem that motion blur is disabled for this frame.

Perhaps the Mirror modifier could use undeformed coordinates to determine which vertices to merge, so that the topology stays the same. But this is a bit of an unusual setup in that typically the mirror modifier comes before the armature modifier, so that both sides can be animated independently.

The problem is indeed that the topology changes during motion blur, which is not supported. Cycles only checks that the number of vertices is the same, so it doesn't detect that the topology changes. But if it would have detected that you'd still have the problem that motion blur is disabled for this frame. Perhaps the Mirror modifier could use undeformed coordinates to determine which vertices to merge, so that the topology stays the same. But this is a bit of an unusual setup in that typically the mirror modifier comes before the armature modifier, so that both sides can be animated independently.
Author

Makes sense, as I mentioned, this was created in a hurry just for reference. I created a second version with cleaner topology and I used the same modifiers in the same order in the stack and it worked fine. As I am not a developer, I had no clue how the motion blur is calculated, knowing now that verts are checked, it makes complete sense that there was an error. Thanks for the reply, it is much appreciated. Oh, and thanks for all the awesomeness you have brought to Blender.

Makes sense, as I mentioned, this was created in a hurry just for reference. I created a second version with cleaner topology and I used the same modifiers in the same order in the stack and it worked fine. As I am not a developer, I had no clue how the motion blur is calculated, knowing now that verts are checked, it makes complete sense that there was an error. Thanks for the reply, it is much appreciated. Oh, and thanks for all the awesomeness you have brought to Blender.

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2015-10-21 08:23:21 +02:00

So, not a bug in the end, we can close it. ;)

So, not a bug in the end, we can close it. ;)
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
4 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#46404
No description provided.