Not the camera params or settings,...specifically interested on the polymesh.
Thank you,
Interested in all variations of this...but at the moment, we have baked geometry, so supplying two matrices is not the preferred way, Thanks.
There has to be motion keys (arrays of values for parameters) or there's no motion blur
On a polymesh, the matrix parameter will have motion keys for transformation blur
and vlist and nlist have motion keys for deformation blur
Arnold itself doesn't calculate these motion keys, they are provided by the translator (for example, MtoA).
Hi Stephen, Thank you for the quick reply...
Are there docs that show how to specify motion keys on vlist and nlist ?
Thanks!
I ask because we don't use Maya to generate the assfile,...though we include mtoa.so.
Thanks,
I think I see how to do this, similar to specifying two matrices,etc..
Do I have to have a corresponding 'nlist' entry for each 'vlist' entry?
Meaning do I need a normal for each vertex? is that strictly required?
Thanks,