AndersEgleus
08-04-2009, 01:04 PM
Hi there.
I'm making a mel particle rib-exporter script and I've run into a little problem.
I want to evaluate particles at completely arbitary subframes (like 12.125) since I must assume that the user can set any camera shutter angle and any number of motion blur steps.
The problem is that maya's particles only evaluate on whole frames, even if I use e.g. currentTime -e 12.125;. (Actually any time that's bigger than a whole frame will cause a new evaluation, e.g. 12.0001, but then it won't evaluate again until the time is larger than 13.)
I'd like to avoid using dynGlobal's oversample attribute, since it only accepts integers, which may mean many more oversamples than needed. (e.g. if I want to evaluate at 12.8, 12.93333333, 13.0666666667, and 13.4, - i.e. 4 time steps with a shutter angle of 144 - I need to have an oversample count of 15, even if the time between samples is only 1/7.5).
In the manual it says the forceDynamics attribute can be used to manually update particles: By requesting this attribute, all of the dynamics, emission, and death will be forced for this particle shape. It is intended to be used for batch mode and dynamics run-up.but nothing happens when I getAttr this attribute on a subframe.
Anyone else had this problem?
I'm making a mel particle rib-exporter script and I've run into a little problem.
I want to evaluate particles at completely arbitary subframes (like 12.125) since I must assume that the user can set any camera shutter angle and any number of motion blur steps.
The problem is that maya's particles only evaluate on whole frames, even if I use e.g. currentTime -e 12.125;. (Actually any time that's bigger than a whole frame will cause a new evaluation, e.g. 12.0001, but then it won't evaluate again until the time is larger than 13.)
I'd like to avoid using dynGlobal's oversample attribute, since it only accepts integers, which may mean many more oversamples than needed. (e.g. if I want to evaluate at 12.8, 12.93333333, 13.0666666667, and 13.4, - i.e. 4 time steps with a shutter angle of 144 - I need to have an oversample count of 15, even if the time between samples is only 1/7.5).
In the manual it says the forceDynamics attribute can be used to manually update particles: By requesting this attribute, all of the dynamics, emission, and death will be forced for this particle shape. It is intended to be used for batch mode and dynamics run-up.but nothing happens when I getAttr this attribute on a subframe.
Anyone else had this problem?