no motion blur with autosmooth - cycles #42315

Closed
opened 2014-10-20 17:02:49 +02:00 by pixl · 8 comments
pixl commented 2014-10-20 17:02:49 +02:00 (Migrated from localhost:3001)

System Information
WIndows 7 / geforce 780ti

Blender Version

2.72a 73f5a41

Exact steps for others to reproduce the error
No motion blur on deformable mesh (armature modifier) when autosmooth is on, rendering with cycle. When autosmooth is Off, all is fine.

Based on a (as simple as possible) attached .blend file with minimum amount of steps

**System Information** WIndows 7 / geforce 780ti **Blender Version** 2.72a 73f5a41 **Exact steps for others to reproduce the error** No motion blur on deformable mesh (armature modifier) when autosmooth is on, rendering with cycle. When autosmooth is Off, all is fine. Based on a (as simple as possible) attached .blend file with minimum amount of steps
pixl commented 2014-10-20 17:02:49 +02:00 (Migrated from localhost:3001)
Author

Changed status to: 'Open'

Changed status to: 'Open'
pixl commented 2014-10-20 17:02:49 +02:00 (Migrated from localhost:3001)
Author

Added subscriber: @pixl

Added subscriber: @pixl
pixl commented 2014-10-20 17:10:58 +02:00 (Migrated from localhost:3001)
Author

you can test with this link :

wing.blend

you can test with this link : [wing.blend ](http://www.pautot.net/blender/wing.blend)
Sergey Sharybin was assigned by Bastien Montagne 2014-10-20 19:30:13 +02:00

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

The thing here is Cycles splits the triangles which crosses the autosplit angle threshold. This could easily lead to topology changes which would make motion blur work incorrect.

Proper solution is to not do geometry split but store decoupled normals,making the render kernel aware of this. This would be handled as a general Cycles improvement TODO. I've linked this report from there http://wiki.blender.org/index.php/Dev:2.6/Source/Render/Cycles/ToDo

Thanks for the report, but i'd consider this a TODO.

The thing here is Cycles splits the triangles which crosses the autosplit angle threshold. This could easily lead to topology changes which would make motion blur work incorrect. Proper solution is to not do geometry split but store decoupled normals,making the render kernel aware of this. This would be handled as a general Cycles improvement TODO. I've linked this report from there http://wiki.blender.org/index.php/Dev:2.6/Source/Render/Cycles/ToDo Thanks for the report, but i'd consider this a TODO.
pixl commented 2014-10-21 19:10:45 +02:00 (Migrated from localhost:3001)
Author

By using a edge split I can have the same result and the motion blur works!
Thank you!

By using a edge split I can have the same result and the motion blur works! Thank you!

Added subscriber: @Lapineige

Added subscriber: @Lapineige

Added subscriber: @stilobique

Added subscriber: @stilobique
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
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#42315
No description provided.