atomsGaffer
atomsGaffer copied to clipboard
Toolchefs
Atoms Crowd extension for Gaffer
the generator can receive per agent primvars from both the agent pointcloud as well as the variation reader geo, have control options as to what does end up on the...
It is currently functional but not very useful. It also needs unit tests.
Add an option to the AtomsCrowdGenerator to output a PointsPrimitive representing the animated agent skeletons rather than the final geometry.
I just experienced a hashing bug of some kind. I was using the AtomsMetadata node to override the `atoms:variation` and it seemed to work, but then disabling the node did...
We might not want to load all variations, so we can add a StringPlug to filter them using `StringAlgo::multiMatch`. It can default to "*" so we get all variations.
currently the weights/indices for deformation are stored as custom attributes, instead store them as primvars that will be exposed via the VariationReader and need to be read from the primvars...
We should be able to store in the variation file a mesh interpolation (linear vs catmulClark) and the variation reader should respect that. We can either add the Cortex convention...
Since we know the 10 primvars we're exposing on the points coming out of the CrowdReader, we should pre-populate the AtomsMetadata UI with those options as optional member plugs of...
Its more natural for Gaffer uses if an integer string field supports anything `IECore.FrameList.parse()` can handle.
We don't necessarily want to load the ai attributes exported from mtoa, so this should be optional.