3.7.1 Changes Checklist
The following is a check list of the changes that need to be documented prior to version 3.7.1 release.
- A new finish parameter
use_alphahas been added to suppress highlights and reflections depending on pigment transparency.
- A new special pigment pattern
user_definedhas been added to define the pigment color directly in terms of a set of functions.
- A new pattern
potentialhas been added to define a pattern based on the potential field of a
map_typekeyword now supports the Angular Map projection for light probes, popularized by Paul Devebec, as
- Done Native support for repetition has been added to the
cracklepattern to avoid the discontinuities in the pattern caused by repeat warps.
- Done The torus syntax has been extended to give more control over the spindle in a self-intersecting torus
- Done Color and pigment maps now support non-linear interpolation to achieve more pleasing gradients
- Fresnel angle-dependent attenuation can now also be applied to highlights and the diffuse component for more physical realism
- Done UV mapping support has been added to cones and cylinders. See-It
- Done A new parameter
polarityhas been added to isosurfaces. See-It
- Done A new geometric primitive
lemonhas been added. See-It
Scene Description Language, Options and INI settings
- Done Support for variable-size arrays has been added
- Done A new data container
dictionaryhas been added to support structured storage of data
- Done Pseudo-dictionaries
globalhave been added, allowing to specifically access local or global identifiers respectively
- Done The
max_extentfunction as used to determine the size of an image map in pixels can now also be used on normal maps and density files
- Done Macros up to a certain size (currently hard-coded to 65536 characters per macro) are now cached in memory, improving parsing speed of invocations especially when the macro in question is defined in a different file
- All instances of
grayin keywords or INI file options can now alternatively be spelled
grey. Previously this was only the case inside function definitions where it applied only to the
- Done A new inbuilt constant
tauhas been added
#localsyntax has been extended to support tuple-style assignments. The main purpose is to allow macros to return a set of values rather than just a single one
- Done The macro syntax has been extended to allow for
- Done The creation of a log for the
+Crender abort-continue feature can now be suppressed using
-CCto save disk space
- Done Support for the ITU-R BT.709 and BT.2020 transfer functions has been added to POV-Ray's gamma handling portfolio
- Done A new function-based user-defined camera type
user_definedhas been added
- Light sources distance-based fading can now be set to obey an inverse-power law at all distances
- CIE L*a*b* conversion macros have been added to colors.inc
- A new include file colors_ral.inc has been added containing predefined colors according to the RAL Classic standard
- Thinking all copyright dates in code, scenes, documentation should be updated to 2016 (or 2017) for beta release
- For a 3.7.1 release we should probably pull all the X11 related sections from the documentation. Remember seeing something about VGA / SVGA support too about which I am suspicious, but maybe this all works?
- By default, gamma handling of NetPBM (PPM/PGM) in and output files now follows the official NetBPM standard, which mandates gamma-encoding using the ITU-R BT.709 transfer function. As usual this can be overridden by the
gammainput file parameter or
File_GammaINI setting, respectively
- The Compression setting now affects more file types: Specifying
Compression=1with file type
T(Targa) will now generate compressed Targa (same as file type
C), and explicitly specifying
Compression=0with file type
P(Netpbm PPM/PGM) will generate plain (ASCII) Netpbm rather than raw (binary)
- POV-Ray will now try to auto-detect whether an input TIFF file with alpha channel uses
premultipliedor non-premultiplied alpha mode, rather than blindly presuming
- The interaction of
filter allwith an image's alpha channel has been changed to be more intuitive: rather than adding the image's transparency to the user-specified transparency, the image's opacity is now effectively multiplied with the user-specified opacity. (requires
#version 3.71or later)
- The image file format previously referred to as IFF (now more precisely referred to as IFF-ILBM) is now associated with the
.lbmfile extension in addition to the
- On Unix with Simple DirectMedia Layer (SDL) enabled the p key can now be used to pause and un-pause a render
versionpseudo-variable will now evaluate to the effective language version at the time the expression is parsed, except when used in a
#versiondirective, in which case the behavior remains unchanged. The requirement to start each scene with a
#versionstatement is now more strongly enforced for POV-Ray 3.7 scenes. An error is reported if the scene file does not begin with a
#versiondirective but does have a
#version 3.71(or later) directive anywhere in the main scene file
ambientwith a suspiciously high value in a non-legacy scene will now issue a warning, unless
emissionis also specified
- A long-standing undocumented inconsistency in the treatment of backslashes in string literals, in which backslashes were essentially not interpreted as escape characters if the parser expected a filename, has been cleaned up. Backslashes are now treated as escape characters in all string literals. requires
#version 3.71or later
The focus of this change was correcting unix console messages. There was previously no notice 'p' and 'q' were active for +D renders. The final pause, if using +P, had always incorrectly said hitting any key would continue/quit when only 'q', enter or detecting on the SDL window would. Enabling 'p' to also continue from the final pause in addition to mid render ones makes 'p' operation consistent throughout the render (and it was cleaner code-wise). Forgot to mention yesterday this change is self-documenting due the prompts to the console changing to reflect it.
- Done Array elements no longer have to be of the same type. See-It
- Dithering is now fully supported for Radiance HDR output files
- Trailing whitespace in INI files no longer causes a warning
- Animation status messages now include the nominal frame number
- POV-Ray for Windows now reports file names and line numbers of warnings
- Radiosity can now honor the
brilliancesetting of a surface
- Color maps, pigment maps and the like are no longer limited to 256 entries. See-It and See-Also
More work needed at Reference:Average_Pattern, Reference:Normal_Map, Reference:Slope_Map, Reference:Patterned_Textures, Reference:Density (CLi)
- The number of components per blob is no longer artificially limited. Over-Here
I don't think any documentation is necessary except in the "what's new section", as the upper limit never seems to have been officially documented in the first place. (CLi)
Code Snippet's Comments and Content Related
Use this section for code snippet's to be included in reference. Comments and content related items are welcome too.
3.7.1 Scene File Checklist
- Done spindle torus example
- Done user_defined camera example
- Done Pavement pattern example
- Done Unit square scalings for pavement and tiling patterns added to pavement.pov and tiling.pov
- Potential pattern using blobs. Second with iso or as option in first scene.
- Nothing with ovus or lemon. Add to primativ.pov perhaps?
- Rename primativ.pov to primative.pov or delete and create individual files?
- portfolio/allobjects.pov out of date.
- Recent scenes with rendered PNGs - even some 3.7 ones - are not part of the scene directory html Friedrich A. Lohmueller created in 20123.
- Replace while loops with for loops where counting. Cleans up our example scenes.
Do we admit 3.7.1 is slower and explain why (C++)? See: https://github.com/POV-Ray/povray/issues/48