(02-10-2021, 05:30 PM)tyFlow Wrote: You don't need that elaborate workaround, but you have to also enable instancing in the Mesh operator for moblur to work when the particle interface is on.
Thanks for your answer.
Unfortunately, changing the Mesh operator to render as instances and turning the Particle Object Interface on changes the frame rendering time from 18 seconds to 132 seconds. And this is just about the test scene, in a working project with a lot of geometry, the rendering time tends to infinity.
We approached Redshift support with this question and here's what they told us:
"Looks like it’s still the issue with changing topology. That means tyFlow is not giving us appropriate vertex velocities on the specified map channel. So we default to sampling the mesh at all sub-frames being blurred. If the number of vertices is changing, we cannot deform the mesh.
When that happens, we output a message that shows in Redshift Feedback Display (if enabled), the Render Messages window, and the Redshift log file:
WARNING: The geometry of ‘tyFlow002’ changes while the shutter is open. Cannot perform deformation blur on this mesh for this frame.
I’ve looked a little deeper here, and I see that tyFlow is actually populating the vertex velocity channel, but the vertex count on that channel is completely different. This breaks our code, which requires that the channel contains the same number of vertices. It looks like a vertex used by multiple faces is being assigned a separate velocity for each face."
Is there anything that can be done by tyFlow to fix the situation? So it would be possible to calculate MB via channel 20 for any topology and any number of geometries?