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
We should support compute shaders. These will function somewhat differently, and I think that we should not duplicate too much between our existing display-focused shaders and the compute shaders.
Compute shaders should not have vertex/geometry/fragment, so we need to set up a slightly different object. We can still use a Shader I think, but we won't want to use the same setup for a ShaderProgram. We may end up not using all of Shader, either, since there we handle stuff like blending functions, which aren't relevant to this.
The text was updated successfully, but these errors were encountered:
Another big reason to support these as special-purpose objects is that often they will not need to be computed every render call. For instance, a histogram does not need to be computed constantly.
We should support compute shaders. These will function somewhat differently, and I think that we should not duplicate too much between our existing display-focused shaders and the compute shaders.
Compute shaders should not have vertex/geometry/fragment, so we need to set up a slightly different object. We can still use a
Shader
I think, but we won't want to use the same setup for aShaderProgram
. We may end up not using all ofShader
, either, since there we handle stuff like blending functions, which aren't relevant to this.The text was updated successfully, but these errors were encountered: