Below is an extremely cut down version that still has the issue. All you need to do it make a pflow with the name PFSource001 and make sure the partic…
I’ve used the .getParticleTM quite well in the past in a scripted transform for geometry objects. Cg.
I did manually make the PFsource. It’s finding the PfSource ok, no errors. It just doesn’t seem to update internally so when I get the particle transf…
Indeed. This is just the chunk that deals with changing the frame and getting the transforms and writing to file. There’s obviously variables/paths/fu…
Thanks Klvnk. Could you elaborate a little more? Your suggestion sounds promising. I know how to add scripted custom attributes with functions/paramet…
Lo: How do you go about attaching callbacks to a rig? I only know how to add a callback to a scene rather than to objects. Cg.
PePeTD: They generally do. But not all of them. Hidden objects don’t necessarily have their script controllers evaluated. They need to be part of some…
48Design: You can install a function within a custom attribute on the rootnode of the scene and install a callback to execute it. But that setup lives…
OK, I’ve sorted out the multiple execution/weird value issue. Seems like a dependency bug related to path constraints. Not going to worry about that r…
Silly thing is, I’m often both putting custom attributes on objects in rigs with built in functions and I store plenty of variables in ca’s on the roo…
Of course. Thanks. Worked perfectly. Cheers, Cg.