WebGPUBackend: Fix manual clear() regression.
#31388
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #30647
Description
While investigating #31387, I've noticed that #30647 has introduced a minor regression in
WebGPUBackend.clear()when rendering directly to the default framebuffer (e.g. when usingTHREE.LinearSRGBColorSpaceas the output color space). Below fiddles demonstrates the glitch:https://jsfiddle.net/5k3xga61/
The default render pass descriptor is shared so it is not possible to rely on cached depth and stencil clear values in
clear(). They must be configured on every clear invocation or the configuration values in the depth stencil attachment are incorrect.