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
Since all this really does is modify a constant primitive variable, there is an argument for just using a PrimitiveVariable node to do the work. However :
- Changing the type can change the bound of the primitive, and we must always keep the bound consistent, so a dedicated node is required.
- We may wish to make the type be a specific part of the PointsPrimitive API in future, rather than an ad-hoc primitive variable. Having a dedicated node will allow us to do that without breaking compatibility in Gaffer scripts.
FixesGafferHQ#476.
Since all this really does is modify a constant primitive variable, there is an argument for just using a PrimitiveVariable node to do the work. However :
- Changing the type can change the bound of the primitive, and we must always keep the bound consistent, so a dedicated node is required.
- We may wish to make the type be a specific part of the PointsPrimitive API in future, rather than an ad-hoc primitive variable. Having a dedicated node will allow us to do that without breaking compatibility in Gaffer scripts.
FixesGafferHQ#476.
This would be similar to the MeshType node, but allow the type of PointsPrimitives to be set (disk, blobby, sprite etc).
The text was updated successfully, but these errors were encountered: