atomsGaffer
atomsGaffer copied to clipboard
Toolchefs
Atoms Crowd extension for Gaffer
AtomsVariationReader: instance MeshPrimitive according to arnold subdiv_type attribute, removed hardcoded 'linear' mesh type
First of all, this branch contains some minor performance fixes: 1) For this one, the credits go to Alexander who pointed it out. In most cases, an agent id's will...
This isn't needed after the generator. Note that this may require changes on the base class in Gaffer to allow modifying the top level location.
Once https://github.com/GafferHQ/gaffer/pull/3394 is merged and released, we'll want to update the `AtomsCrowdGenerator` to make use of it, the same way `GafferScene::Instancer` is doing.
We have a crowd with instancing enabled and a huge amount of duplication (1200 agents duplicated several times to make 20500 agents). Based on stats from an Arnold render, the...
We should run the tests for every PR / Release on Travis (or similar).
Is there a good reason to have the AtomsCrowdClothReader as a standalone node? It seems to just add extra data onto the points coming out of the AtomsCrowdReader before piping...
We can add a `Help->Atoms` menu that links to external Atoms docs and loads each example script.
If I transform the points between the `CrowdReader` and the `CrowdGenerator`, I expect that to move the agents origins, but it is not currently happening.
WIth #9, the internal EngineData is reporting the correct memory usage, but the overall consumption of the node still seems higher than what should be necessary for a point cloud....