[3.x] Prevent use of Opaque Pre-Pass's threshold on top of Alpha Scissor #45372
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.
In SpatialMaterials and ShaderMaterials, both Alpha Scissor and Opaque Pre-Pass can discard fragments (== create fully-transparent pixels), but Opaque Pre-Pass has a hardcoded threshold of 0.1 that the end-developer cannot modify.
This PR makes SpatialMaterials use the alpha scissor threshold instead of Opaque Pre-Pass's own threshold whenever Alpha Scissor is in use. This prevents the strange behavior where any fragment with an ALPHA value under 0.1 would be discarded, no matter what Alpha Scissor value you set.
Using blue noise for ALPHA_SCISSOR and a radial gradient:
Scene in image: PrepassTesting.zip
Related: #45288
Do tell me if this breaks the intent of Opaque Pre-Pass.