User:Jholsenback

Organization

Basically, I've been using this area as a scratch pad of sorts. As I complete things, and clean-up I'll probably just add a link here for reference.

Scratch Pad

Change Log Extracts

These are change-log extracts that might be useful with helping to update the documentation. For now they are just in reverse chronological order until I can arrange them in a more useful manner.

Beta 35

• Radiosity maximum_reuse parameter now governs the maximum effective radius of a sample more directly.
• Added "out-of-the-box" transparency support for GIF files.
• Added support for PNG sRGB chunks.

Note: Non-legacy scene default gamma handling for image input files has changed significantly from previous betas, affecting all file formats except OpenEXR, Radiance HDR and (with minor differences) most flavors of PNG; there will be NO corresponding warnings. See below for more detail.

Input image files not carrying unambiguous gamma information will now be assumed to match a common gamma setting, and gamma-adjusted accordingly; this common input file gamma setting can be specified in the scene file using the following syntax:

global_settings {
  file_gamma GAMMA
  }

where GAMMA is either a numeric expression specifying the approximate display gamma for which input files are assumed to be gamma pre-corrected, or the keyword srgb indicating that input files are assumed to match the sRGB standard. (In the latter case, gamma adjustment is applied according to the sRGB standard, instead of approximating with a gamma 2.2 power-law function.) The default setting is sRGB.

Regardless of this global setting, gamma correction is not applied if the image input file is obviously used as a mere data container, such as when immediately used in a height field.

Default gamma handling rules for any image input file can be overridden by specifying file_gamma GAMMA immediately after the file name, e.g.:

image_map {
  jpeg "foobar.jpg" file_gamma 1.8
  interpolate 2
  }

This also applies to contexts where gamma adjustment is not normally applied, e.g. file formats that are defined to be encoded linearly, or files used in height fields, to simplify handling of files not conforming to standards.

Note: Gamma handling for PNG input files has changed as follows in legacy #version 3.6 scenes:

• In the absence of an assumed_gamma statement, non-indexed PNG files with a gAMA chunk (i.e. virtually all PNG files) will appear far brighter than with POV-Ray 3.6
• In the presence of an assumed_gamma 1.0 statement, indexed PNG files (uncommon) will appear darker than with POV-Ray 3.6
• In the presence of an assumed_gamma 2.2 statement, PNG files with a gAMA lower than 2.2 (uncommon) will appear darker than with POV-Ray 3.6
• PNG files with an sRGB chunk but no gAMA chunk may appear significantly different than with POV-Ray 3.6
• PNG files may generally appear slightly different than with POV-Ray 3.6

A warning will be printed in these cases, except for the latter.

Beta 34

• Added support for diffuse backside illumination:

To model thin, diffusely-translucent objects (e.g. paper, curtains, leaves etc.), an optional 2nd float parameter has been added to the diffuse finish statement to control the effect of illumination from the back of the surface. The default value is 0.0, i.e. no diffuse backside illumination. For realistic results, the sum of both parameters should be between 0.0 and 1.0, and the 2nd parameter should be the smaller of the two.

Note: This feature is currently experimental and may be subject to change. In particular, the syntax as well as interoperation with double_illuminate, multi-layered textures or conserve_energy are still under investigation.

A new sample scene, "advanced/diffuse_back.pov", has been provided to illustrate this new feature.

• New option added 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, higlights and iridescence); other features expendable during pretrace may follow in future versions.

• Windows console version now sends stream output to stderr by default.

Beta 33

• Added no_radiosity keyword, as known from MegaPOV:

Specifying no_radiosity in an object block makes that object invisible to radiosity rays, in the same way as no_image, no_reflection and no_shadow make an object invisible to primary, reflected and shadow test rays, respectively.

• Revival of Radiosity Load/Save + various other radiosity code changes:

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)

If both +RFI and +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.

• New radiosity "high reproducibility" mode:

When specifying High_Reproducibility or +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).

Keyword Addition Example

This outlines the steps to add a new keyword to the documentation. In this case deprecated

• first determine where the descriptive passage goes then add it
• update the syntax diagram in the appropriate places
• update the syntax diagram in the Quick Reference
• update the Identifiers and Keywords list (not done yet)

Note: save this until all keyword additions have been identified because it's an alphabetic list in html table form.

• document any other place(s) that it's used
• add a table of contents entry

Links

• The source and notes on the LaTeX markup used in the documentation.