There are six debug views for Spatial-Temporal Post-processing (STP). To access them, open the Rendering Debugger window and navigate to Rendering > Map Overlays and select STP. Unity shows the STP Debug Views property where you can select one of the views.
For more information on how to access the Rendering Debugger window, refer to How to access the Rendering Debugger.
Debug view | Description |
---|---|
Clipped Input Color | Show the HDRhigh dynamic range See in Glossary input color clipped between 0 and 1. |
Log Input Depth | Show the input depth in logarithmic scale. |
Reversible Tonemapped Input Color | Show the input color mapped to a 0–1 range with a reversible tonemapper. |
Shaped Absolute Input Motion | Visualize the input motion vectors. |
Motion Reprojection | Visualize the reprojected color difference across several frames. |
Sensitivity | Visualize the pixel sensitivities. Green areas show where STP can’t predict motion behavior. These areas are likely to render with reduced visual quality. STP struggles to predict motion in areas when occluded objects first become visible or when there is fast movement. Incorrect object motion vectors can also cause issues with motion prediction. Red areas highlight pixels that are excluded from TAA, so STP intentionally does not predict their motion. This helps avoid unnecessary blurring and ghosting, especially when rendering transparent objects. |
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.