WebGPURenderer: Manual Shadow Update Control via shadow.needsUpdate
#29110
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.
Description
This PR allows to manually control the update of a shadow through the already available
shadow.autoUpdate
andshadow.needsUpdate
properties.Usage:
To demonstrate the feature, I updated the
webgpu_shadowmap_opacity
example:Before:
After:
To ensure this feature works correctly, I had to account for the versioning of depthTexture. Without this, when the Renderer initialize the FBO in the first render loop, it updates the attached textures, leading to the incorrect shadowMap being bound to the meshes in subsequent renders.
This contribution is funded by Utsubo