Page MenuHome

Cycles motion blur struggles to render quantic vertex
Closed, ArchivedPublic

Description

System Information
windows 7
tested on gtx 460 / gtx 970 /gtx 980 ti / gtx titan

Blender Version
Broken: 2.78

Short description of error
when topology change between frame because of a keyframe with a float time value, cycles is slow as hell

moving the shapekey key on frame 8 instead of 8.55 solve the problem

from 5 minutes to 4 hours on full scene.

Attached a file with the problem,

Exact steps for others to reproduce the error
open the file, render the frame 97, it's fast, render frame 96 it's slow as hell
on the full scene, it went from 5 minutes to 1 hours
Tested on CPU and GPU

i{F373749}

Event Timeline

Confirmed on Debian Stretch with official 2.78, 2.77a, and 2.76b release builds from blender.org
We ran into this problem multiple times at work (Windows machines) and had no clue what was going on, so thanks @kevin deguisne (iscream) for the hint!

Sergey Sharybin (sergey) changed the task status from Unknown Status to Unknown Status.Oct 5 2016, 10:39 AM
Sergey Sharybin (sergey) claimed this task.

Cycles's motion blur doesn't work reliably when topology changes. The only thing cycles checks is the number of vertices (checking full topology match is quite expensive task). So if topology changes in a way that number of vertices stays the same, but you've got different order of vertices or different edges then you'll have some rendering artifacts or much longer render times (because object might become much bigger bounds which slows ray casting a lot).

This is a known limitation.

So thanks for the report, but closing as a TODO.