Accessing the TP Particle Geometry

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/03/2012 at 10:48, xxxxxxxx wrote:

I got a problem working with Thinking Particles & Dynamics. If I apply the dynamic tag to a Particle Geometry object I got the dynamic behavior on the objects generated by the PG itself, but the particles don't follow them. In other words, the TP generation is used just to give birth to the objects, then the latter got dynamics while Thinking Particles follow the behavior determined by the TP nodes.

I need to access the dynamic objects, so is there a way to access the Particle Geometry structure via Python and navigate through the objects one by one? If not, is it possible to link the TP particles (position and alignment) to the dynamic objects generated by the Particle Geometry?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/03/2012 at 12:34, xxxxxxxx wrote:

you could try to map the tpparticle system on another particle system like standard particles or mograph which can handle dynamics. however reading those informations can become difficult,
becuase i am not sure if you can actually read the mo_clone or standard particle position calculated by the dynamics solver.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/03/2012 at 13:18, xxxxxxxx wrote:

Hi littledevil, thanks for your answer.

The problem remains even with a standard particle emitter. The particles travel on a straight line (or follow the behavior created by the particle forces) while the objects generated fall according to gravity. In mograph I think it's possibile to access the clones - I did it easily with a Python node - but of course you'll lose all the advantages of a true particle generation (emission speed or an emission variable in time, for example).

I tried also to freeze the Particle Geometry object using a "Current state to object" command via Python, but unfortunately when you do that - even using the command in the standard UI - the objects snap immediately to the particle positions, as they were not influenced by dynamics. It's a pity, because the command generates exactly what I need, a null object with the list of objects as children.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/03/2012 at 13:53, xxxxxxxx wrote:

well, that is what i said - the dynamics work on some kind of object cache level and it is difficult to get the true object matrix. when you want to use CStO cache your dynamic tags before you execute CStO this will fix your problems.