Kevin Traywick

Michael Goldfarb says the same, (paraphrasing) "there's no point to storing rig attributes as points except that Houdini is especially good at manipulating points, etc.

I haven't used APEX a lot but I see your point. He feeds the same rig set up into several characters and the tags handle the different topos. Pretty nifty stuff.

What is the importance of Apex's use of point containers for nodes? Or, why is it useful that moving, adding or deleting the point geometry also moves, adds or deletes the corresponding node?

It is a pretty slick feature but I'm not really sure what to do with it. Is it that graph parity with the node network makes it easier to understand? Or is it a bigger idea down the road, that parameters will be adjusted in Python states so most work is done in the viewport, node parameters being updated in sync?

I just want to know what's in the list at the end after it did a fade to black...