Difference between revisions of "Reference:Tracing Options"
m (more AM3 work)
|Line 400:||Line 400:|
<li>With +BM2 : 48 seconds total</li>
<li>With +BM2 : 48 seconds total</li>
Revision as of 17:52, 22 September 2018
There is more than one way to trace a ray. Sometimes there is a trade-off between quality and speed. Sometimes options designed to make tracing faster can slow things down. This section covers options that tell POV-Ray how to trace rays with the appropriate speed and quality settings.
Central to the many feature enhancements offered with version 3.7, POV-Ray now supports Symmetric MultiProcessing or SMP. The command line option
Work_Threads=n or the
+WTn switch allows you to specify the number of work threads to be used while rendering a scene. On Windows systems, the default is the number of detected cores. On Linux/Unix and OSX based systems, the default is first based on the number of detected cores, otherwise, the number of configured cores. If detection is not possible the default is set to 4. In all cases the maximum value is 512.
Render Block Size
POV-Ray provides a mechanism to specify the render block size via either an INI-style option
Render_Block_Size=n or on the command-line
+BSn, where n is an integer larger than or equal to 4. This represents the edge size of the square used to distribute work to the render threads, and thus the number of pixels in each block will be n squared. The default value is 32. If you specify a value that is greater than the larger of the width or height of the image being rendered, it is clipped to that value. Using render block sizes of less than eight can impact performance, particularly on large images that render quickly, as it significantly increases the amount of message traffic between the render back-end and the graphical front-end, which communicate using a shared-memory queue.
POV-Ray provides a mechanism to specify the order of render block via either an INI-style option
Render_Pattern=n or on the command-line
+RPn, where n is an integer between 0 and 5. This represents the various orders for the distribution of the blocks to the render threads. The default value is 0.
If you specify a value that is greater than the maximum number of patterns, it will revert to the default. Using a different
Render_Pattern has only an effect on the preview of the rendered image, as the first blocks might be placed differently, but does not change the final image once the render has been completed.
Pattern 0: is the classical order. The first block is in the top left corner, and it progress from left to right, and then it continues on the next row of blocks. Just like reading text.
Pattern 1: is the same as pattern 0, but the rows and columns are swapped. It starts at the top left corner and it progress from top to bottom.
Pattern 2: The top row is processed first, starting at each corner and meeting at the center of the row, then the bottom row is processed the same way. The last block is at the very center of the image.
Pattern 3: Is the opposite order of pattern 2, the first block is at the center of the image, the expansion being firstly horizontal.
Pattern 4: Is the same as pattern 2, except that the rows and columns have been swapped.
Pattern 5: Is the same as pattern 3, but the rows and columns are swapped, however the expansion from the center of the image is firstly vertical.
Render Block Step
Whatever the chosen pattern (with
+RP), the number of the next processed block can be incremented by more than 1, to jump over blocks, via either an INI-style option
Render_Block_Step=n or on the command-line
+RSn, where n is a positive non zero integer. The provided value of n gets reduced automatically to a smaller value if the provided value would lead to a situation where the some blocks would not get rendered.
Assuming an image made of 40 blocks, with
+RS9, the order of block numbers would be:
0, 9, 18, 27, 36, 5, 14, 23, 32, 1, 10, 19, 28, 37, 6, 15, 24, 33, 2, 11, 20, 29, 38, 7, 16, 25, 34, 3, 12, 21, 30, 39, 8, 17, 26, 35, 4, 13, 22, 31.
The same 40 blocks with
+RS8 would in fact use
+RS7 instead. As would a
+RS2 in fact be reduced to
+RS1 the default.
||Set quality value to n (0 <= n <= 11)|
Quality=n option or
switch allows you to specify the image rendering quality. You may choose to
lower the quality for test rendering and raise it for final renders. The
quality adjustments are made by eliminating some of the calculations that are
normally performed. For example settings below 4 do not render shadows.
Settings below 8 do not use reflection or refraction. The duplicate values
allow for future expansion. The values correspond to the following quality
||Just show quick colors. Use full ambient lighting only. Quick colors are used only at 5 or below.|
||Show specified diffuse and ambient light.|
||Render shadows, but no extended lights.|
||Render shadows, including extended lights.|
||Compute texture patterns, compute photons|
||Compute reflected, refracted, and transmitted rays.|
||Compute media, radiosity and subsurface light transport.|
The default is 9 if not specified.
Automatic Bounding Control
||Turn bounding on/off|
||Turn bounding on; Set threshold to 3 or previous amount|
||Turn bounding off|
||Set bound threshold to n|
||Turn bounding on; bound threshold to n|
||Turn bounding off; set future threshold to n|
||Turn light buffer on/off|
||Turn light buffer on|
||Turn light buffer off|
||Turn vista buffer on/off|
||Turn vista buffer on|
||Turn vista buffer off|
POV-Ray uses a variety of spatial sub-division systems to speed up
ray-object intersection tests. The primary system uses a hierarchy of nested
bounding boxes. This system compartmentalizes all finite objects in a scene
into invisible rectangular boxes that are arranged in a tree-like hierarchy.
Before testing the objects within the bounding boxes the tree is descended
and only those objects are tested whose bounds are hit by a ray. This can
greatly improve rendering speed. However for scenes with only a few objects
the overhead of using a bounding system is not worth the effort. The
Bounding=off option or
-MB switch allows you to force
bounding off. The default value is on.
+MBn switch allows you to set the minimum number of objects
necessary before bounding is used. The default is
means that if your scene has fewer than 3 objects POV-Ray will automatically
turn bounding off because the overhead is not worth it.
In general, any finite object and many types of CSG of finite objects will properly respond to this bounding system. In addition blobs and meshes use an additional internal bounding system. These systems are not affected by the above switch. They can be switched off using the appropriate syntax in the scene file (see Blob and Mesh for details).
Text objects are split into individual letters that are bounded using the bounding box hierarchy. Some CSG combinations of finite and infinite objects are also automatically bound. The end result is that you will rarely need to add manual bounding objects as was necessary in earlier versions of POV-Ray unless you use many infinite objects.
As of version 3.7 the
Light_Buffer options have been deprecated.
Removing User Bounding
||Turn unnecessary bounds removal on/off|
||Turn unnecessary bounds removal on|
||Turn unnecessary bounds removal off|
||Turn split bounded unions on/off|
||Turn split bounded unions on|
||Turn split bounded unions off|
Early versions of POV-Ray had no system of automatic bounding or spatial
sub-division to speed up ray-object intersection tests. Users had to manually
create bounding boxes to speed up the rendering. Since version 3.0, POV-Ray
has had more sophisticated automatic bounding than any previous version. In
many cases the manual bounding on older scenes is slower than the new
automatic systems. Therefore POV-Ray removes manual bounding when it knows it
will help. In rare instances you may want to keep manual bounding. Some older
scenes incorrectly used bounding when they should have used clipping. If
POV-Ray removes the bounds in these scenes the image will not look right. To
turn off the automatic removal of manual bounds you should specify
Remove_Bounds=off or use
-UR. The default is
One area where the jury is still out is the splitting of manually bounded
unions. Unbounded unions are always split into their component parts so that
automatic bounding works better. Most users do not bound unions because they
know that doing so is usually slower. If you do manually bound a union we
presume you really want it bound. For safety sake we do not presume to remove
such bounds. If you want to remove manual bounds from unions you should
Split_Unions=on or use
+SU. The default is
BSP (Binary Space Partitioning) tree bounding is now available. To turn it on use
Bounding_Method=2 in the INI file or on the command-line. When it is in use you will get some additional statistics in the output pane regarding the built tree.
Please keep in mind that this implementation of BSP is highly beta and will not speed up scenes in many cases (and in fact may slow some down). In particular the building of the tree can take a long time and lots of memory in severe cases. Using the BSP tree rather than our traditional BVH (Bounding Volume Hierarchy) system (default or
+BM1) is a choice best made for specific scenes that will benefit from the way the BSP operates, and in particular if the render is long enough to offset the build time. The BSP tree build time will be constant for a given scene and set of BSP parameters, regardless of the output resolution. A 30-second BSP build may not be a good choice on a 60-second test render but may be acceptable for a 60-minute final render if the use of BSP adds a few pixels per second.
On some scenes the difference however will be dramatic, with short build times and radically increased render speed.
We have provided some BSP-related options via the INI file and encourage you to experiment with them to see if you can get better results than the default values built in to POV-Ray. We will listen to feedback from this and if necessary tweak the defaults.
Note: We do not guarantee that all of the following INI file settings will remain in future releases.
BSP_MaxDepth=128 BSP_BaseAccessCost=1.0 BSP_ChildAccessCost=1.5 BSP_IsectCost=150.0 BSP_MissChance=0.2
The values shown above are the default. You can also get the defaults if you use a value of 0 for any of the above, or of course just by not specifying the option at all. For an explanation of what the values mean you may refer to Ray Tracing News article by Eric Haines.
See the distribution file
~scenes/bsp/Tango.pov for a good example of a scene that benefits from the BSP bounding.
Tango.pov rendered at 800x600, no AA
- With +BM1 : 70 seconds total
- With +BM2 : 48 seconds total
||Set's a value for the stochastic seed New in version 3.8|
By default some stochastic mechanisms in POV-Ray intentionally give different results for each render, with the intent that multiple renders can be averaged to get a higher-quality image. To this end, the corresponding pseudo-random number generators are seeded with a value derived from the current date and time.
+SSn option is specified, the seed will instead be derived from the specified value, allowing to produce exactly the same output each time by specifying that same value. Alternatively, the mechanism may be co-opted to prevent separate renders started at the same time from producing identical results, by explicitly specifying different values.
Note: Even if the seed is set identically, other factors may cause differences in the result. For example the render block size
+BSn or the render pattern
+RPn options. Results may also differ between versions of POV-Ray.
Presently anti-aliasing sampling method 3 is the only feature that is sensitive to the stochastic seed setting.
||Turns anti-aliasing on/off|
||Turns aa on with threshold 0.3 or previous amount|
||Turns anti-aliasing off|
||Sets aa-sampling method (either
||Sets anti-aliasing threshold|
||Sets aa on with aa-threshold at n.n|
||Sets aa off (aa-threshold n.n in future)|
||Sets aa-jitter on/off|
||Sets aa-jitter on with 1.0 or previous amount|
||Sets aa-jitter off|
||Sets aa-jitter amount to n.n. If n.n <= 0 aa-jitter is set off|
||Sets aa-jitter on; jitter amount to n.n. If n.n <= 0 aa-jitter is set off|
||Sets aa-jitter off (jitter amount n.n in future)|
||Sets aa-depth (1 <= n <= 9)|
||Sets the anti-aliasing gamma to n.n|
The ray-tracing process is in effect a discrete, digital sampling of the image with typically one sample per pixel. Such sampling can introduce a variety of errors. This includes a jagged, stair-step appearance in sloping or curved lines, a broken look for thin lines, moiré patterns of interference and lost detail or missing objects, which are so small they reside between adjacent pixels. The effect that is responsible for those errors is called aliasing.
Anti-aliasing is any technique used to help eliminate such errors or to reduce the negative impact they have on the image. In general, anti-aliasing makes the ray-traced image look smoother. The
Antialias=on option or
+A switch turns on POV-Ray's anti-aliasing system.
When anti-aliasing is turned on, POV-Ray attempts to reduce the errors by shooting more than one viewing ray into each pixel and averaging the results to determine the pixel's apparent color. This technique is called super-sampling and can improve the appearance of the final image but it drastically increases the time required to render a scene since many more calculations have to be done.
POV-Ray gives you the option to use one of two alternate super-sampling methods. The
Sampling_Method=n option or
+AMn switch selects either type
1 or type
2. Selecting one of those methods does not turn anti-aliasing on. This has to be done by using the
+A command line switch or
Type 1 is an adaptive, non-recursive, super-sampling method. It is adaptive because not every pixel is super-sampled. Type 2 is an adaptive and recursive super-sampling method. It is recursive because the pixel is sub-divided and sub-sub-divided recursively. The adaptive nature of type 2 is the variable depth of recursion. Type 3 is an adaptive, non-recursive stochastic oversampling method and is New in version 3.8
In the default, non-recursive method (
+AM1), POV-Ray initially traces one ray per pixel. If the color of a pixel differs from its neighbors (to the left or above) by at least the set threshold value then the pixel is super-sampled by shooting a given, fixed number of additional rays. The default threshold is 0.3 but it may be changed using the
Antialias_Threshold=n.n option. When the switches are used, the threshold may optionally follow the
+A. For example
+A0.1 turns anti-aliasing on and sets the threshold to 0.1.
The threshold comparison is computed as follows. If r1, g1, b1 and r2, g2, b2 are the rgb components of two pixels then the difference between pixels is computed by
diff = abs(r1-r2) + abs(g1-g2) + abs(b1-b2)
If this difference is greater than the threshold then both pixels are super-sampled. The rgb values are in the range from 0.0 to 1.0 thus the most two pixels can differ is 3.0. If the anti-aliasing threshold is 0.0 then every pixel is super-sampled. If the threshold is 3.0 then no anti-aliasing is done. Lower threshold means more anti-aliasing and less speed. Use anti-aliasing for your final version of a picture, not the rough draft. The lower the contrast, the lower the threshold should be. Higher contrast pictures can get away with higher tolerance values. Good values seem to be around 0.2 to 0.4.
When using the non-recursive method, the default number of super-samples is nine per pixel, located on a 3*3 grid. The
Antialias_Depth=n option or
+Rn switch controls the number of rows and columns of samples taken for a super-sampled pixel. For example
+R4 would give 4*4=16 samples per pixel.
The second, adaptive, recursive super-sampling method starts by tracing four rays at the corners of each pixel. If the resulting colors differ more than the threshold amount additional samples will be taken. This is done recursively, i.e. the pixel is divided into four sub-pixels that are separately traced and tested for further subdivision. The advantage of this method is the reduced number of rays that have to be traced. Samples that are common among adjacent pixels and sub-pixels are stored and reused to avoid re-tracing of rays. The recursive character of this method makes the super-sampling concentrate on those parts of the pixel that are more likely to need super-sampling (see figure below).
The maximum number of subdivisions is specified by the
Antialias_Depth=n option or
+Rn switch. This is different from the adaptive, non-recursive method where the total number of super-samples is specified. A maximum number of n subdivisions results in a maximum number of samples per pixel that is given by the following table. Where the first column represents anti-alias depth or
+Rn option. The second column is the number of additional samples per super-sampled pixel for the non-recursive method
+AM1. Lastly the third column is the maximum number of samples per super-sampled pixel for the recursive method
Note: The maximum number of samples in the recursive case is hardly ever reached for a given pixel. If the recursive method is used and the anti-aliasing threshold is not reached, each pixel will be the average of the rays traced at its corners. In others words, you get the average of those four pixels with no further sub-sampling. In most cases a recursion level of three is sufficient.
And the third... work in progress. More to follow.
Another way to reduce aliasing artifacts is to introduce noise into the sampling process. This is called jittering and works because the human visual system is much more forgiving to noise than it is to regular patterns. The location of the super-samples is jittered or wiggled a tiny amount when anti-aliasing is used. Jittering is used by default but it may be turned off with the
Jitter=off option or
-J switch. The amount of jittering can be set with the
Jitter_Amount=n.n option. When using switches the jitter scale may be specified after the
+Jn.n switch. For example
+J0.5 uses half the normal jitter. The default amount of 1.0 is the maximum jitter which will insure that all super-samples remain inside the original pixel.
Note: The jittering noise is random and non-repeatable so you should avoid using jitter in animation sequences as the anti-aliased pixels will vary and flicker annoyingly from frame to frame.
If anti-aliasing is not used one sample per pixel is taken regardless of the super-sampling method specified.
As the human eye is more sensitive to absolute brightness differences at a low overall brigtness than at higher ones, super-sampling based on linear light intensity differences would yield either poor anti-aliasing in darker regions, or unnecessary super-sampling in brighter regions of the image. To avoid this, POV-Ray compares gamma-adjusted values instead. (Note that this only affects the comparison operation; the averaging of the super-samples is done in whatever working color space is specified in the scene file via the
assumed_gamma keyword.) The
Antialias_Gamma=n.n command line option or
+AGn.n sets the gamma to apply before comparison, defaulting to 2.5. Note that the value is actually the inverse of the gamma applied, in order to use the same value range as the display and file gamma settings. Neutral behavior can be achieved using
mesh_camera feature added in version 3.7 also makes extreme super-sampling possible. See the distribution file
~scenes/camera/mesh_camera/ess/README.txt for additional information.
Radiosity High Reproducibility
As of version 3.7 a new radiosity mode has been introduced. When specifying
+HR on the command line, POV-Ray will spend extra effort to make sure renders are deterministic despite SMP. Currently radiosity is the only code to use this flag; in
+HR mode, radiosity pretrace starts out with fewer threads, and some extra rules are imposed on sample re-use that may cause surplus samples to be gathered.
Note: The high reproducibility mode is not intended for use with radiosity alone, and it will need more work to guarantee the same improved reproducibility in other features. Even though it works well with radiosity, this addition is still experimental.
Radiosity Load and Save
The following .ini / command line parameters are recognized:
Radiosity_File_Name="<name>" or +RF"<name>" to set the cache file name Radiosity_From_File=<on/off> or +RFI to enable reading the radiosity file at startup Radiosity_To_File=<on/off> or +RFO to enable writing new samples to the radiosity file
Note: The parameter names are preliminary, and may still be subject to change; there is a potential conflict between the shorthand forms.
+RFO are specified, new samples gathered are appended; otherwise,
+RFO causes the file to be overwritten if it exists.
New samples gathered are written whenever an SMP block is completed. Tests indicate that this is almost neutral regarding performance, compared to operation with radiosity file output disabled.
Radiosity Vain Pretrace
Also new as of version 3.7 an option has been added to speed up radiosity pretrace:
As some computations don't contribute to the generation of radiosity samples, they can safely be skipped during radiosity pretrace to gain some speed if the pretrace's other role as a coarse preview is not required.
The following .ini file/command line options control whether pretrace performs all computations so it can double-feature as a coarse preview (vain pretrace):
Radiosity_Vain_Pretrace=bool turns vain pretrace on/off +RVP turns vain pretrace on (default) -RVP turns vain pretrace off
Note: With vain pretrace off, preview will look remarkably odd during the radiosity pretrace phase; this is normal, and no reason to be alarmed.
At the moment, turning vain pretrace off will affect only classic lighting computations (diffuse lighting, highlights and iridescence); other features expendable during pretrace may follow in future versions.