You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 them into the generator. Can we move this functionality to the AtomsCrowdReader instead?
The text was updated successfully, but these errors were encountered:
After using the ClothReader in production a bit, we feel it should remain a separate node, but should not require a 3rd input on the Generator. The current graph in the example script looks like:
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 them into the generator. Can we move this functionality to the AtomsCrowdReader instead?
The text was updated successfully, but these errors were encountered: