PostProcessingUtils: Add method for normal reconstruction. #29703
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: -
Description
This PR introduces
PostProcessingUtils.getNormalFromDepth()
which can be used to compute normals from depth. This can be useful if MRT is too costly for some reason (e.g. bandwidth restrictions).I've updated the AO modules to use this new code path if no normal render target is available.
I want to make clear that reconstructed normals are slightly different compared to our current normal render target since it represents the actual flat surface of the geometry. This technique is inadequate for stuff like SSR since you end up with a flat-shaded, facetted look. However, it is actually the better pick for AO which is explained in https://wickedengine.net/2019/09/improved-normal-reconstruction-from-depth/comment-page-1/.
@sunag The quality difference is barely visible in
webgpu_postprocessing_ao
but we should keep in mind this issue when usingtransformedNormalView
for normal texture input.