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
Similar to #5080, if you are passing a canvas as a uniform to a post process, it will not be updated even if the canvas changes. I believe this is by design, but there doesn't seem to be a way to explicitly update it with the public API.
This Sandcastle will draw a red/blue rectangle to a canvas, and it will force the PostProcessStage to re-create the texture with this private API hack:
And it would behave as it does in the above Sandcastle. Doing this currently will crash because it expects that uniform to be a Cesium.Texture object at that point.
Similar to #5080, if you are passing a canvas as a uniform to a post process, it will not be updated even if the canvas changes. I believe this is by design, but there doesn't seem to be a way to explicitly update it with the public API.
This Sandcastle will draw a red/blue rectangle to a canvas, and it will force the PostProcessStage to re-create the texture with this private API hack:
We could make PostProcessStage handle setting it directly like this:
And it would behave as it does in the above Sandcastle. Doing this currently will crash because it expects that uniform to be a
Cesium.Texture
object at that point.Came up on the forum.
The text was updated successfully, but these errors were encountered: