Add note to shadow_mesh
docs to warn about improper usage
#94547
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.
Fixes: #72071
Using a different mesh for shadow_mesh breaks rendering right now because the shadow mesh is used for the depth prepass.
If we don't use it for the depth prepass, we will hurt performance. Further, the rendering will still appear broken as we will get all kinds of self-shadowing artifacts. Therefore, we just shouldn't support using a different shaped mesh for shadows. Users should use the old workflow which is to have a child MeshInstance3D with
SHADOW_CASTING_SETTING_SHADOWS_ONLY
and have the source mesh useSHADOW_CASTING_SETTING_OFF
. Doing so has no additional cost over usingshadow_mesh
, but gives the user full control over how the shadow is drawn.