To help artists control the overall look and exposure of a scene, the post-processing stack comes with a set of industry-standard monitors. You can find them in the preview area of the Inspector. Like with any other preview area in the Inspector, you can show/hide it by clicking it and undock it by right-clicking its title.
Each monitor can be enabled in play mode for real-time update by clicking the button with the play icon in the titlebar. Note that this can greatly affect performance of your scene in the editor, so use with caution. This feature is only available on compute-shader enabled platforms.
A standard gamma histogram, similar to the one found in common graphics editing software. A histogram illustrates how pixels in an image are distributed by graphing the number of pixels at each color intensity level. It can help you determine whether an image is properly exposed or not.
This monitors displays the full range of luma information in the render. The horizontal axis of the graph corresponds to the render (from left to right) and the vertical axis is the luminance. You can think of it as an advanced histogram, with one vertical histogram for each column of your image.
The Parade monitor is similar to the Waveform only it splits the image into red, green and blue separately.
It is useful in seeing the overall RGB balance in your image, for instance, if there is an obvious offset in one particular channel, and in making sure objects and elements in the shot that should be black, or white are true black or true white. Something that is true black, white (or grey for that matter) will have equal values across all channels.
This monitor measures the overall range of hue (marked at yellow, red, magenta, blue, cyan and green) and saturation within the image. Measurements are relative to the center of the scope.
More saturated colors in the frame stretch those parts of the graph farther toward the edge, while less saturated colors remain closer to the center of the Vectorscope which represents absolute zero saturation. By judging how many parts of the Vectorscope graph stick out at different angles, you can see how many hues there are in the image. Furthermore, by judging how well centered the middle of the Vectorscope graph is relative to the absolute center, you can get an idea of whether there’s a color imbalance in the image. If the Vectorscope graph is off-centered, the direction in which it leans lets you know that there’s a color cast (tint) in the render.
Shader model 3
See the Graphics Hardware Capabilities and Emulation page for further details and a list of compliant hardware.
2017–05–24 Page published with no editorial review
New feature in 5.6
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?
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
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:
Thanks for helping to make the Unity documentation better!