Table Of Contents
|
|
The Trace Depths section is used to impose maximum limits for different ray types across your entire scene.
Increasing Trace Depth values can quickly and greatly increase render times in scenes with many bounces. In general it is a best practice to use as few as you need to achieve the result that you desire.
Overriding Trace Depths at the Material Level
Trace Depth values can be overridden on a per-material basis under the Optimizations section of materials like the Redshift Standard Material, this includes overriding above or below the global trace depth values.
The Combined depth parameter specifies the maximum limit for global illumination, reflection, volume, and transmission / refraction rays combined.
This means that if the individual depth value for global illumination, reflections or refractions is higher than the Combined Depth the resulting render will still be capped at the Combined Depth value.
For example, let's say that reflection and refraction are both set to a value of 4 and combined is set to 6. If a ray had already been reflected 4 times, then it could only be refracted 2 more times because the combined trace depth is 6.
The Reflection depth parameter puts an individual cap on how many times a reflection ray can bounce.
The Refraction depth parameter puts an individual cap on how many times a refraction ray can bounce or pass through objects.
The Transparency depth parameter puts an individual cap on how many times a transparency ray can pass straight through objects.
Transparency is utilized for things like Opacity in the Redshift Material to go much deeper and render much faster than refractions.
Transparency Depth is not limited by the Combined Depth parameter.
|
|
| Example scene |
|
|
|
|
|
| Combined: 6 Reflection: 4 Refraction: 6 Transparency: 16 |
8 6 8 20 |
24 20 24 48 |
24 1 24 48 |
|
Color Management in greater detail
For more information on the subject of color management please see the Color Management - OCIO ACES page.
This sets the path to the OpenColorIO config file to be used.
By default Redshift ships with and uses its own predefined configuration but a custom OCIO config be set here as well.
This sets the linear color space that Redshift renders in, ACEScg by default which allows Redshift to make full use of its wider rendering color gamut.
This is the Output Display Transform that should be set to a color space that is supported by the display that you are working on, for most people this will be sRGB.
This determines how the image is displayed on screen and works in conjunction with the Display transform. By default this can be set to 4 different views, an ACES SDR tone-mapped result, un-tone-mapped, a logarithmic color space (ACEScct) or the raw linear result which is unaffected by the Display transform.
|
|
|
|
|
| View: ACES 1.0 SDR-Video | Un-tone-mapped | Log | Raw |
When enabled this setting will bake in the view transform.
When enabled this will use any file rules established within the currently used OCIO config file. OCIO file rules are used to automatically set the correct color space for assets that fall within established parameters.
Examples:
Enables or disables the rendering of any default lights in the respective digital content creation tool.
If your render appears brighter or differently lit than you expect this is a good option to check and disable.
