Difference between revisions of "Documentation Talk:Tutorial Section 3.7"
Jholsenback (talk | contribs) m (created a workspace) |
Jholsenback (talk | contribs) m (added the section lead in text, and started grammar spelling and wording clean up.) |
||
Line 1: | Line 1: | ||
====Radiosity with conventional lighting==== | ====Radiosity with conventional lighting==== | ||
− | + | <!--<indexentry "Radiosity, with conventional lighting">---> | |
+ | |||
+ | <p>This section will introduce you to the technique of combining conventional and radiosity lighting. In this section, we'll be using basically the same sample scene located in <code>~/scenes/radiosity/radiosity2.pov</code>, however by changing various radiosity parameters, we can explore the effects that those changes can have on the appearance of the scene. Later on, in this tutorial, you can find examples of [[Documentation:Tutorial Section 3.7#Radiosity without conventional lighting|pure radiosity]] illumination.</p> | ||
+ | <p class="Note"><strong>Note:</strong> Unless stated otherwise, all images are rendered with the following settings:</p> | ||
+ | |||
+ | <pre> | ||
+ | global_settings { | ||
+ | radiosity { | ||
+ | pretrace_start 0.08 | ||
+ | pretrace_end 0.01 | ||
+ | count 150 | ||
+ | nearest_count 10 | ||
+ | error_bound 0.5 | ||
+ | recursion_limit 3 | ||
+ | low_error_factor 0.5 | ||
+ | gray_threshold 0.0 | ||
+ | minimum_reuse 0.005 | ||
+ | maximum_reuse 0.2 | ||
+ | brightness 1 | ||
+ | adc_bailout 0.005 | ||
+ | } | ||
+ | } | ||
+ | </pre> | ||
+ | |||
+ | <p>All objects except the sky have <code>diffuse 0.65</code> and <code>emission 0</code> in their finish block. The sky sphere has a bright blue pigment (what a surprise) with <code>diffuse 0</code> and <code>emission 1.0</code> as finish attributes.</p> | ||
+ | |||
+ | <p class="Note"><strong>Note:</strong> If using the <code>[[Documentation:Reference Section 3.1#Sky Sphere|sky_sphere]]</code> object, which does not support the <code>finish</code> keyword, instead of a <code>[[Documentation:Reference Section 4.1#Sphere|sphere]]</code> object that does, you will need define a <code>[[Documentation:Reference Section 2.5#The #default Directive|#default]]</code> finish, in order to affect it's finish attributes.</p> | ||
+ | |||
+ | <p>For example:</p> | ||
+ | |||
+ | <pre> | ||
+ | #default {finish { diffuse 0 emission 1 }} | ||
+ | </pre> | ||
+ | |||
+ | <p>For starters, here's the scene without radiosity (no <code>radiosity</code> block), with the settings shown above, and the difference between the two. The <code>emission 1</code> finish of the blue sky makes it function as kind of a diffuse light source. This leads to a bluish touch of the whole scene in the radiosity version.</p> | ||
<table class="matte" width="700px" cellpadding="0" cellspacing="10px"> | <table class="matte" width="700px" cellpadding="0" cellspacing="10px"> |
Revision as of 19:33, 20 January 2011
Radiosity with conventional lighting
This section will introduce you to the technique of combining conventional and radiosity lighting. In this section, we'll be using basically the same sample scene located in ~/scenes/radiosity/radiosity2.pov
, however by changing various radiosity parameters, we can explore the effects that those changes can have on the appearance of the scene. Later on, in this tutorial, you can find examples of pure radiosity illumination.
Note: Unless stated otherwise, all images are rendered with the following settings:
global_settings { radiosity { pretrace_start 0.08 pretrace_end 0.01 count 150 nearest_count 10 error_bound 0.5 recursion_limit 3 low_error_factor 0.5 gray_threshold 0.0 minimum_reuse 0.005 maximum_reuse 0.2 brightness 1 adc_bailout 0.005 } }
All objects except the sky have diffuse 0.65
and emission 0
in their finish block. The sky sphere has a bright blue pigment (what a surprise) with diffuse 0
and emission 1.0
as finish attributes.
Note: If using the sky_sphere
object, which does not support the finish
keyword, instead of a sphere
object that does, you will need define a #default
finish, in order to affect it's finish attributes.
For example:
#default {finish { diffuse 0 emission 1 }}
For starters, here's the scene without radiosity (no radiosity
block), with the settings shown above, and the difference between the two. The emission 1
finish of the blue sky makes it function as kind of a diffuse light source. This leads to a bluish touch of the whole scene in the radiosity version.
You can see that radiosity greatly affects the shadowed parts when applied in combination with conventional lighting.
Radiosity provides a lot of settings to trade off quality for rendering speed. For instance, here is the same scene with default settings (just a radiosity{}
block with no content), with our reference settings, and with some maddeningly high-quality settings (which you shouldn't try at home because they take ages to render); below each image you see the difference to the high-quality version:
Changing brightness
changes the intensity of radiosity effects. Specifying brightness 0
would be the same as without radiosity (theoretically; in practice POV-Ray doesn't accept a zero value). As a rule brightness 1
should work correctly in most cases. If the effects are too strong you can reduce this, though this is not recommended, as it's usually an indication that your textures are too bright and your illumination too dim. Larger values lead to quite strange results in most cases.
The recursion_limit
setting primarily affects the brightness of shadows, nooks and corners. The images below show the results of setting this parameter to 1, 2 and 5 respectively, with the second line showing the difference to our reference settings (recursion_limit 3
):
You can see that values higher than 3 do not lead to any better results in such a quite simple scene. In most cases values of 1 or 2 are sufficient, especially for outdoor scenes.
The error_bound
value mainly affects the structures of the shadows. Values larger than the default of 1.8 do not have much effect, they make the shadows even flatter. Extremely low values can lead to very good results, but the rendering time can become very long, and you may need to modify other parameters to avoid a grainy appearance:
Somewhat related to error_bound
is low_error_factor
. It reduces error_bound during the pretrace phase. Changing this can be useful to eliminate artifacts.
From now on, we'll be using recursion_limit 1
, error_bound 0.2
and low_error_factor 1.0
to emphasize the effects of the next parameters we'll have a look at.
The following 3 images illustrate the effect of count
. It is a general quality and accuracy parameter leading to higher quality and slower rendering at higher values. They're not a cure-for-all though. For the difference images we compared with count 150
.
Another parameter that affects quality is nearest_count
. You can use values from 1 to 20, default is 5; we're comparing to a value of 10 here:
Again higher values lead to less artifacts and smoother appearance but slower rendering.
nearest_count
also accepts a second parameter, which activates adaptive pretrace, providing a good means of speeding up pretrace without significant loss of quality (not shown here); the value must be smaller than the first parameter (e.g. nearest_count 20,10
). When set, POV-Ray will stop pretracing individual areas of the image where the average sample density already satisfies this second value, thereby avoiding to trace low-detail areas over and over again for little gain, while still being able to drill down deep into high-detail areas.
minimum_reuse
influences at which minimum distance previous radiosity samples are always reused during calculation, affecting quality and smoothness in nooks and corners. Higher values generally give a smoother appearance, at the cost of corner detail, while lower values may cause corners to look splotchy unless the other parameters (most notably count
and nearest_count
) are set for higher quality as well.
As minimum_reuse
must be lower than maximum_reuse
, to avoid a parse error with the highest setting we're using minimum_reuse 4.0
for these three images.
Another important value is pretrace_end
. It specifies how many pretrace steps are calculated and thereby strongly influences the speed. Usually lower values lead to better quality, but it is important to keep this in good relation to error_bound
.
Normally in the final trace no additional radiosity samples are taken unless absolutely needed. You can change this by adding always_sample on
, allowing you to increase pretrace_end
to speed up rendering. Note however that this is very prone to artifacts such as visible render block boundaries and horizontal "smearing", so it is usually only useful for test renders. You should also use a low setting for nearest_count
, or you may actually increase the rendering time (and the probability of getting the mentioned artifacts!).
The effect of max_sample
is similar to brightness
. It does not reduce the radiosity effect in general but weakens samples with brightness above the specified value.
You can strongly affect things with the objects' finishes. In fact that is the most important thing about radiosity. Normal objects should have emission finish 0 (default). Objects with emission > 0 actually act as light sources in radiosity scenes.
Remember that the default finish values used until now were diffuse 0.65 emission 0
.
Finally you can vary the sky in outdoor radiosity scenes. In all these examples it is implemented with a sphere object.
finish { emission 1 diffuse 0 }
and the pigment of the original sample scene were used until now. The following images show some variations: