Thanks Bobo.
My explanation was a bit mixed up.
I realise changing point counts are problematic, but the sample scene that is producing errors is very simple.
Pflow with cubes. Nothing deleted, just a standard flow. I have removed all complicated bits of my project, and just replaced with a simple cube and speed op. So only one event.
Load this into Maya, and even with no motion blur, the Xmesh cache won’t produce a standard velocity pass with Vray.
In the same scene I created a brand new, virgin flow, and this works. Simple cubes, and produces a velocity pass.
So i’m thinking there is something in the PFlow that is causing this error? It’s likely not Xmesh fault.
// Warning: Mesh “xmesh_DOESNT_WORKShape1” has changing number of vertices (1464 expected, 1472 actual). //
But…when i render the dodgy cache in 3dsMax, it works. No motion blur activated, I see a velocity pass.
Here are some renders. Default vray settings, no motion blur.
