Boomer Labs

It seems that velocities are not (properly) baked. Here's a simple version of what I'm trying to do:

- create a box and setup some simple pos/rot animation
- export the animation using a SuperMesher
- create a standard pflow object
- replace the "Position Icon" operator with a "Position Object" operator
- pick the SuperMesher object as the source object
- check both "Inherit Emitter Movement" and "Animated Shape"
- remove other operators (except birth and display of course)

When you play the animation you should see that most particles stay at their initial position, and some fly off. So apparently, there is _some_ velocity data present?

Unfortunately, the lack of velocity data means that it's not only unusable to use as an emitter in PFlow, but also in Phoenix and Fume in a lot of cases.

Is there something wrong in the way I'm setting things up, or is velocity data simply not supported by SuperMesher?

Thanks in advance,
Martijn

I've setup a scene to illustrate the problem:
[url]http://www.mediafire.com/?iy0lt8jazi8s6jm[/url]
Password:boomer

There are 3 boxes in the scene: the original, a Mesher compound and a SuperMesher object. The box is animated using an XForm modifier from frame 0 to 50 and particles are emitted at frame 25.

If you change the "Position Object" operator in PFlow to use the SuperMesher object (after caching Box01 obviously) you'll see that the particles seem to travel in the right direction, just at an extremely high speed.

Thanks,
Martijn

Another update on the issue; I seem to get better results when I increase the number of samples per frame in SuperMesher to something like 50. So maybe SuperMesher is returning wrong velocity values to PFlow due to an interpolation problem?

"We pride ourselves in our responsiveness to our customers." ?

Martijn,

Sorry for the delay, we're trying to get SM for 2012 out the door. Are you using SM to cache the PFlow or as the source object for particles that are emitted?

If the former, remember, SM converts particles into a mesh, so particle velocity information is lost.

Thanks,

Matt