Documentation Talk:Tutorial Section 3.7 - Revision history

Jholsenback: done with this subsection

2011-01-25T00:50:58Z

done with this subsection

Jholsenback: done with this sub-section

2011-01-25T00:18:04Z

done with this sub-section

Jholsenback: some minor caption tweaks and image issues

2011-01-24T21:39:00Z

some minor caption tweaks and image issues

Show changes

Jholsenback: image tag changes

2011-01-24T17:11:17Z

image tag changes

Show changes

Jholsenback: image tag changes

2011-01-24T17:07:31Z

image tag changes

Show changes

Jholsenback: minor mod

2011-01-24T11:49:24Z

minor mod

Jholsenback: final changes ... section done now

2011-01-23T11:23:08Z

final changes ... section done now

Show changes

Jholsenback: missed a tag when i rearranged an image panel

2011-01-23T10:27:09Z

missed a tag when i rearranged an image panel

Jholsenback: corrections ... done with section

2011-01-23T10:18:19Z

corrections ... done with section

Jholsenback: continued clean up ... more later

2011-01-22T20:42:49Z

continued clean up ... more later

← Older revision		Revision as of 00:50, 25 January 2011
Line 1,166:		Line 1,166:

	====Performance Considerations====		====Performance Considerations====
		+	<!--<indexentry "Radiosity performance considerations">--->
		+
		+	<p>High quality radiosity can be very slow. To some extent this is the price to pay for realistic lighting, but there are a lot of things that can be done to improve speed.</p>
		+
		+	<p>If average to good quality radiosity will work for your scene, then it's probably a good idea to spend the time to find the <em>sweet spot</em> that strikes the best balance between quality and speed. Especially <code>recursion_limit</code> should be kept as low as possible. Sometimes <code>1</code> is sufficient, if not <code>2</code> or <code>3</code> should often be enough.</p>
		+
		+	<p>With high quality settings, radiosity data can take quite a lot of memory. Apart from that the other scene data is also used much more intensively than in a conventional scene. Therefore insufficient memory and swapping can slow down things even more. Here's a few [[Documentation:Reference Section 1.3#Radiosity Options\|radiosity options]] that might help.</p>
		+
		+	<p>Finally the scene geometry and textures are important too. Objects not visible in the camera usually only increase parsing time and memory use, but in a radiosity scene, also objects behind the camera can slow down the rendering process. See the section [[Documentation:Reference Section 3.2#Configuring Radiosity\|Configuring Radiosity]] for some helpful hints.</p>

@@ Line 1,133: / Line 1,133: @@
 </pre>
 ====Normals and Radiosity====
 ====Performance Considerations====

@@ Line 642: / Line 642: @@
 </table>
-<p>OK, lets change things up a bit before we continue. We'll be using the sample scene <code>~/scenes/radiosity/radiosity3.pov</code> for the rest of this tutorial.</p>
+<p class="Note"><strong>Note:</strong> We'll be using the sample scene <code>~/scenes/radiosity/radiosity3.pov</code> for the rest of this tutorial.</p>
 <p>This next series of images show our new test object with the default settings, then our reference settings, and lastly those maddeningly high-quality settings we used earlier. Notice that with the default settings, the image looks much worse than in the first part of this tutorial. The reason being, those settings were mainly selected for use with a conventionally lit scene. Keep in mind, radiosity-only scenes are less forgiving of low-quality settings.</p>

@@ Line 441: / Line 441: @@
    </td>
    <td>
-     [[Image:TutImgRadA2123.png|center|220px<!--class="centerpanel"--->]]
+     [[Image:TutImgRadA2123.png|center|220px<!--class="rightpanel"--->]]
    </td>
 </tr>

@@ Line 409: / Line 409: @@
 <p><code>minimum_reuse</code> 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 <code>count</code> and <code>nearest_count</code>) are set for higher quality as well.</p>
-<p>As <code>minimum_reuse</code> must be lower than <code>maximum_reuse</code>, to avoid a parse error with the highest setting we're using <code>minimum_reuse 4.0</code> for these next three images.</p>
+<p>As <code>minimum_reuse</code> must be lower than <code>maximum_reuse</code>, to avoid a parse error with the highest setting we're using <code>maximum_reuse 0.4</code> and the <code>minimum_reuse 0.005</code> case, was used for the comparison with these next three images.</p>
 <table class="matte" width="700px" cellpadding="0" cellspacing="10px">
@@ Line 417: / Line 417: @@
    </td>
    <td>
-     [[Image:TutImgRadA23.png|center|220px<!--class="centerpanel"--->]]
+     [[Image:TutImgRadA21.png|center|220px<!--class="centerpanel"--->]]
    </td>
    <td>
-     [[Image:TutImgRadA21.png|center|220px<!--class="rightpanel"--->]]
+     [[Image:TutImgRadA23.png|center|220px<!--class="rightpanel"--->]]
    </td>
 </tr>
@@ Line 428: / Line 428: @@
    </td>
    <td>
-     <p class="caption">minimum_reuse 0.015</p>
+     <p class="caption">minimum_reuse 0.005</p>
    </td>
    <td>
-     <p class="caption">minimum_reuse 0.005</p>
+     <p class="caption">minimum_reuse 0.015</p>
    </td>
 </tr>
@@ Line 439: / Line 439: @@
    </td>
    <td>
    </td>
    <td>
    </td>
 </tr>
@@ Line 449: / Line 449: @@
    </td>
    <td>
    </td>
    <td>
    </td>
 </tr>

@@ Line 614: / Line 614: @@
 ====Radiosity without conventional lighting====
 <!--<indexentry primary "Radiosity, without conventional lighting">--->
-<p>You can also leave out all light sources and have pure radiosity lighting. The situation then is similar to a cloudy day outside, when the light comes from no specific direction but from the whole sky.</p>
+<table class="matte" width="460px" cellpadding="0" cellspacing="10px">
 <tr>
    <td>
      [[Image:TutImgRadA14.png|center|220px<!--class="leftpanel"--->]]
    </td>
    <td>
@@ Line 633: / Line 635: @@
    <td>
      <p class="caption">with light source</p>
    </td>
    <td>
@@ Line 642: / Line 642: @@
 </table>
-<p>You can see that when the light source is removed the whole picture becomes very blue, because the scene is illuminated by a blue sky, while on a cloudy day, the color of the sky should be somewhere between grey and white.</p>
+<p>OK, lets change things up a bit before we continue. We'll be using the sample scene <code>~/scenes/radiosity/radiosity3.pov</code> for the rest of this tutorial.</p>
-<p>We'll be using the sample scene <code>~/scenes/radiosity/radiosity3.pov</code> for demonstration now, although we will use different radiosity parameters again (same as those initially used for the conventionally-lit scene).</p>
+<p>This next series of images show our new test object with the default settings, then our reference settings, and lastly those maddeningly high-quality settings we used earlier. Notice that with the default settings, the image looks much worse than in the first part of this tutorial. The reason being, those settings were mainly selected for use with a conventionally lit scene. Keep in mind, radiosity-only scenes are less forgiving of low-quality settings.</p>
-<p>For starters, here it is with the default settings, our reference settings, and those maddeningly high-quality settings used earlier:</p>
+<p class="Note"><strong>Note:</strong> As a reminder you might want to refer back to the reference [[Documentation:Tutorial_Section_3.7#Radiosity with conventional lighting|settings]] used at the beginning of this tutorial .</p>
 <table class="matte" width="700px" cellpadding="0" cellspacing="10px">
@@ Line 672: / Line 672: @@
 </tr>
 </table>
 <p>The following images demonstrate the effect of different settings for <code>recursion_limit</code>:</p>