Revision PovRay

#---------------------------------------------------------------------------# Note: To view an original flyspray bug report (FS#xxx), replace the leading
# FS# of the bug ID with the URL http://bugs.povray.org/.

# For example, to read FS#270, visit http://bugs.povray.org/270.
# To view a referenced newsgroup posting (<xxxxx@news.povray.org>), prefix
# the message ID with the URL http://news.povray.org/.
# For example, to read <42765ef3$1@news.povray.org>, visit:
# http://news.povray.org/<42765ef3$1@news.povray.org>.
# The '<' and '>' are optional (if using a shell you may want to omit them).
#-----------------------------------------------------------------------------------------------------------Changes between 3.7.RC7 and 3.7.0
--------------------------------Change 6048 on 2013/09/14 by jholsenback@linux-c2bm
picking up a last minute change
Change 6047 on 2013/09/14 by jgrimbert@smpdirect
fix of formula to restore backward compatibility of heightfield on
red+green non-indexed color image (not only backward compatible, but also
correct formula to cover the full range as intended and documented) Added
also comment to explain why the indexed-image code should NOT be fixed:
despite providing more range, index*257 would break the backward
compatibility, so index*256 should remains (for historical reasons only)
Change 6037 on 2013/09/01 by jholsenback@linux-c2bm
updates to changes/revision files
cleanup... updates and deletes
delete outdated files
several more changes to unix man page
follow up to change #6027
updates to unix man page
Change 6026 on 2013/08/27 by chrisc@x8
add warranty disclaimer to console output
remove outdated support header files for borland, mingw and watcom
compilers. if support is needed for any of the above, it would be better to

start a fresh header as the old ones have not been used since 3.6
correct typo in rename
remove old 4BPP toolbar icons as 16-color mode support isn't really
relevant anymore
rename a few files whose names were upper-case
move SubmitMinidump to internal area
another tweak to the about box
update about bitmap to remove explicit URL's and add support to about
window code to make some areas act as hyperlinks
fix issue with editor selection due to off-by-one line numbers. make use of
SetCaretPos consistent
Change 6008 on 2013/08/20 by clipka@xcli-pc-7
fix for FS#304
Change 6007 on 2013/08/18 by clipka@xcli-pc-7
fix cpuinfo stub for unofficial builds
move about.psd from bitmaps/source to smp/internal/windows
move #undef back inside official code block
added some files left out of previous submissions
Change 5997 on 2013/08/18 by thorsten@host26
adds Mac xcode project and support files, still some compile errors due to
misconfigured paths etc. Big issues resolved though.
Change 5996 on 2013/08/18 by clipka@cli-pc-7
minor indentation cleanup of various sample scene files

swathe of windows changes for 3.7 AGPL3 release. Most visible is removal of
the splash window and updating of the about dialog. 'Tip of the day'
feature removed. Licensing clarified for pvbitmap.cpp/.h. pvlegal.h updated
to reflect AGPL3. readme.html/.txt updated. Import libraries added for
povcmax so as to allow cmedit to link without it. Several functions only
used in official builds moved to new file 'official.h'. Many other changes
related to official vs unofficial builds.
move Intel CPU info code to legacy license area; add stub for
unofficial builds
add BSD-style license header to chi2.cpp as discussed with author
remove some distribution license-related files that are no longer required
update a few unix files to reflect AGPL
Change 5984 on 2013/08/11 by thorsten@xhost26
first version of Mac display code for a preview window created by the
terminal application
Change 5983 on 2013/08/11 by thorsten@xhost26
clean up Mac tree
tweak console project, remove unused codemax project
remove outdated makefiles
remove vs8 and vs9 solutions
integrate flohmuller branch to trunk
tweaks related to console build (windows version)
remove all dependence on codemax header files

move codemax source to //depot/povray/smp/legacy-license/codemax/...
move cmedit source to //depot/povray/smp/windows/cmedit
fix filetype of prebuild.sh (unix specific)
first pass at explicitly assigning licences to individual source files in
the distribution tree. Notes: fish13 has been deleted, and the Insert Menu
and Templates sub-trees have not been updated
corrections to a malformed regex used to fill a script variable
trivial file header fix
change headers to reflect AGPL; remove beta-test boilerplate
fixed typo in warp allocation: spherical warp would have been reported
as cylindrical warp in case of leak or failure to allocate
corrected a segmentation fault that can occur when starting povray from
within blender (unix specific)
addressing FS#294 splines are not thread safe

follow up to change #5889 corrected typo
rename a distribution template file that had spaces in it's filename
completed rollback of change #5876
addressing FS#262 linux sources being compiled twice
partical rollback of change #5876 (radiosity)
follow up to change #5859 (consistency)
follow up to change #5877 (minor comment update)
Change 5877 on 2013/03/30 by thorsten@thorsten-pc-2012
moves some code to frontend, where it is needed
adds back experimental warning for radiosity and adds experimental warning
for gamma handling
cleaned up our jpeg code to use the proper constants for the jpeglib's
custom "boolean" type (we erroneously passed standard C++ bool constants
instead, which could lead to compile errors on some systems)
activate one message de-activate another
suppress what appears to be a duplicate version related message

bump unix VERSION to 3.7.0
bump VERSION to 3.7.0
rollback change #5843
fixes for CID#967299 - CID#967301 resource leak
fix for CID#967298 resource leak
fixes for CID#967302 and CID#967303 resource leak
fixes FS#274 light source fading doesn't work properly with
area_illumination and subsurface scattering
addressing CID's# 967358-967362 Uninitialized variables
addressing CID's# 967337-967345 Uninitialized scalar variables
addressing CID's# 967333-967336 Uninitialized scalar variables
addressing CID# 967350 Uninitialized pointer read
minor fix to radiosity statistics (octree samples/node)

minor but effective changes to octree code for improved performance
in radiosity-heavy scenes
addressing CID #967264 non array delete used on array "str"
fix for FS#271 (old behaviour is retained for pre-3.7 scenes)
fixes a potential illegal memory access when reading a broken .pot
(16-bit greyscale GIF) file, detected as Coverity issue CID #967365
should also solve CID #967363 and #967364 along the way
update source code readme.html
fix unquoted path in shell extension registration and add registry key
backups for uninstall
minor setup tweak (windows version)
update about box image (windows version)
update keywords used for context-sensitive help (windows version)
change copyright date to 2013
update windows help file
-----------------------------------
Changes between 3.7.RC6 and 3.7.RC7

----------------------------------Change 5795 on 2013/02/10 by chrisc@x8
add Append_File INI option (same as +GP)
follow up to #5786: write banner to
unless the stream is debug. without
where a new render starts. we don't
presume the user wants to format it
stream each time we open for append,

this it's often difficult to determine
do this for the debug stream as we
as they see fit

add Jerome Grimbert to contributing developer list
update to insert menu from Friedrich Lohmueller
addendum to change #5786
fixed a portability issue of change #5784
add +GP option, which allows users to append streamed console to
existing console stream output file(s). Further, this option is now
forced-on internally for the second frame of an animation,so output streams
are appended. This has the side effect that the command-line option can
be used to append all animation output to an existing file as well
some minor code sanitizing
added even more const modifiers to the code
upgraded zlib to version 1.2.7 windows VS
addendum to change #5777
upgraded libpng and libjpeg to versions 1.5.14 and 9 respectively in
windows VS
conditionally filter indexentry tags from the unx and mac doc-sets, leaving
them in the windows docs, as they are required to produce searchable
index in chm file
fix a few minor UI issues
update changes/revision file for RC7
fix for FS#270: render abort-continue (+C) sometimes skips blocks
added plenty of const modifiers to the code; kicked out a few unused
parameters and one piece of unused code
a few signedness fixes in image handling code
updated copyright information for some 3rd party libraries
bump version to RC7 so unix build packages get branded properly
updated changes/revision files
a few whitespace fixes in revision.txt
fix a long-standing bug where pressing 'pause' during a parse or render
could sometimes put the frontend/backend sync into an unrecoverable state.
the root cause was the fact that even if a call to the backend's pause
method succeeds (e.g. the backend state correctly transitions to
SceneData::Scene_Paused in the case of the parser), it is still possible
for the task thread to move to Scene_Ready if the parser doesn't
call Task::Cooperate() before finishing. the frontend code has until now
assumed that if a call to e.g. RenderFrontend::PauseParser() succeeded,
the parser would stay paused until told to resume or stop.
add the proportion of the image in X and Y directions to the pixel offset
displayed when the mouse hovers over the render window. e.g. if the mouse
is at X=25 Y=50 of a 200x200 pixel render, the window title will
show "25,50 [0.125,0.250]". this is to make it easier to work out

row/column values for entering into the command-line for partial renders.
add new option to prevent the system from sleeping whilst a render is in
progress. by default this is selected.
add an entry to the default tools menu to browse the sample scenes folder.
add standard declares to the user keywords file.
make the shortcuts placed on the desktop shorter, as windows usually hides
the end of them.
Fix for FS#150: Windows file association problems
Fix for FS#224: Keyword Completion does not work for several names
Various fixes/improvements to the way Windows INSTALL works and how the
documents path is auto-detected if not specified
Fix for FS#153: Error determining I/O permissions when using .ini file
Fix for FS#232: illegal map_type usage reporting. Additionally parser also
now issues an error for invalid interpolate values as well
Bump benchmark version to 2.01. This is to avoid comparison with the 2.00
used in various prior betas (primarily due to changes in the renderer
rather than the benchmark itself)
Replaced access declarations (already deprecated in C++98,
dropped in C++11) with using declarations
Adds a few more options to the editor tab right-click menu as suggested in F
S#135
Fix for FS#109: Debug_File no longer appends frame-by-frame debug data
Fix for FS#267: Bug in "sor" primitive leads to random black

artifacts in radiosity scenes
Minor changes to address issues uncovered by static code analysis
Fix for FS#266: command line options in ini files don't accept quoted
strings as parameters and other flaws found by means of static code
analysis, plus minor code changes to aid in static code analysis
Addressing CID#967224: Coverity static software analysis
Partial fix for FS#265 supress clang compilation warnings
Follow-up: hotfix for #5731
Fixed a bug in file-backed image container found by code review
Housekeeping: indentations and comments
As a follow-up to change #5719: added new source files to VS10 project
Update to change #5710, to avoid hard-coding the value for boost::TIME_UTC
aka boost::TIME_UTC_. Also renamed _TIME_UTC_ to POV_TIME_UTC for more
robustness against any future naming conflicts.
Unknown command line options didn't always produce an error;
Also a fix for a minor flaw in string handling of INI settings

Fix for FS#257 (cannot find input file when resuming animation render)
Fix a bug introduced with change #5665
Assign .pov file association to POVWIN when installing.
Fix for FS#238 (error during #read causes file to be kept open).
Improve cloning of v3.6 INI and provide better defaults.
Fix to handle filenames with a comma in them (crash report 419).
Tweak the Windows setup file.
Bump version to RC7.
Fixed an issue caused by boost's change of TIME_UTC to TIME_UTC_.
Fix to get rid of the following compile warning on Linux variants:
shape/poly.cpp:188:3: warning: this decimal constant is unsigned only in
ISO C90 [enabled by default]
Fix for benchmark thread vs CPU count.
Fix for FS#249 (UTF-8 files with BOM not being accepted)
Housekeeping (whitespace and comments)
Fixed radiosity issues with "diffuse albedo" syntax
Fix whitespace in screen.inc

Adds back crand support.
Addressing FS#247 set no_radiosity in Screen_Object()
Allow GD flag to work correctly (Fix FS#234): a typo.
Follow up to #5678
Update to #5678: workaround for fmod() apparently not conforming to C++
standard on some linux machines.
Fix for FS#233 Picture index out of range. - Fatal error in renderer:
Uncategorized error.
---------------------------------------Changes between 3.7.beta.RC5 and 3.7.RC6
---------------------------------------Change 5674 on 2012/06/18 by jholsenback@linux-c2bm
Pick up last minute changes before release of RC6
Follow up fix for #5672 to address compile problems on linux platform.
Fixed some numeric overflow issues in image handling; also fixed some
other questionable code found along the way.
Resync revsions/changes files.
Potential fixes for a number of crash reports related to the editor,
particularly drag & drop actions, and a fix for the XP64 installer.
A minor fix for radiosity adc_bail_out handling.
More comments changes and whitespace cleanup, plus some trivial code cleanup
.
A few comments changes and whitespace cleanup.
A follow up to change #5649 corrected a formatting issue with radiosity
statistics reporting.
Fix for potential endless loop in CH2RGB macro
Fix merge issue from change #5387 which re-introduced a bug fixed earlier
on (most recent crash report #385, dump file #343).
Fix divide-by-zero in stats code when radiosity query count is 0
(crash report #384, dump file #342)
Additional fix associated with #5624 (colored transparent background)
Bump revision to RC6.
Fix for FS#241: Photons not working correctly.
Cleaned up various C-style casts:
- fixed some fishy ones
- removed some superfluous ones
- replaced with reinterpret_cast some that were accidently casting away
const qualifiers.
- replaced with const_cast some that were deliberately casting away
volatile qualifiers.
- replaced with reinterpret_cast all others I spotted in the same files.
- fixed some const qualifiers in function signatures.
Fixed problems with colored transparent backgrounds.

Updated setup script, plus a few improvements.
Fixed the Windows help file searchable index. Note this is based on the
snapshot of the wiki documentation set taken for RC4.
Fixes to VS10 (windows version) build process
- fixed ALL tiff project targets to build tiff config headers
- fixed Debug/x64 target to build OpenEXR to Float
Insert menu (windows version) update from Friedrich Lohmller.
---------------------------------------Change 5618 on 2012/02/23 by jholsenback@linux-c2bm
Bump to RC5 in the "correct" place
Resync changes/revision.txt files
Bump unix version to RC5
Fix for FS#239 improper uid/gid handling incorrectly branded some files
during non elevated privilege builds.
Fix for crashdump #357 (triggered by non-closed SSLT-enabled
mesh inside CSG)
Make dump submitter a bit more robust.
Fix for FS#12 (facets pattern in normal map)
More installer work, should be more or less done now.
----------------------------------------
Changes between 3.7.beta.RC3 and 3.7.RC4

---------------------------------------Change 5606 on 2012/02/04 by chrisc@x8
Fix to FMA4 detection. AMD optimizations re-enabled.
Fix for FS#235 UNIX segmentation fault: when using the animation loop
and large images are displayed.
Updated the windows help file.
Changed message displayed on crash.
Initial version (windows) of NSIS-based installer.
Added AMD optimizations for noise. Note that these are currently disabled.
Updated the crashdump submitter.
Add support for documents path to be anywhere, rather than requiring it to
be in a standard location.
Changed the windows crash reporting tool dump generation logic to always
generate both full and mini dumps.
Change 5589 on 2011/12/15 by jholsenback_aries_1
Removed obsolete comments (Library Path limitation)
Added "Console" and "Console-SSE2" configurations to VS10 solution and
some projects, and updated config & console code, to get Windows console
project back working (needs to be back-ported to VS8 and VS9; no debug
configuration yet); extensive testing required; expect shellout to be
still dysfunctional.
Updates to VS10 console project (still doesn't build at present though)
Added Penrose P1 (N=6) and P2 (N=2) tilings as 25 and 26; changed the
existing P3 tiling pattern number to 27
Overhauled identifiers & comments in new patterns' code; Added a new
"tiling" pattern: 25 type (N=2) produces a Penrose P3 tile
Added support for tuning brightness of image-mapped sky spheres. See FS#9
area_illumination now also respects fade_power and fade_distance. See FS#46
major overhaul of iridescence feature
Change 5529/5528/5527 on 2011/11/22 by clipka@cli-pc-7
added new "albedo" keyword, that can be used right after
"diffuse", "phong" or "specular
fix for the windows editor crash that was reported in crashdump#111
fix for FS#216: comment out the Radiosity= directive in raddem.ini
that directive became obsolete in 3.7
fix for FS#225: translating a light source fails to translate
the looks_like textures
update of VS 2010 solution & projects: windows build can now statically link
boost and openEXR libraries built from scratch
update to add openEXR include directory tree for installation from source
added VS 2010 projects to build boost_date_time, boost_thread and
openEXR-related projects (not included in solution yet)
a logistics rollback of source/base/image/openexr.cpp and
vfe/win/compilers/msvc.h (checked them in too early)
added source trees for boost (subset of 1.45.0)

and openEXR (subset of 1.6.1 with subset of IlmBase 1.0.1)
fixed issue that caused Visual Studio 2010 to always consider
povbackend to be outdated
removed unused functions from vfe/win/syspovconfig.h that kept generating
type conversion warnings
some fixes to VS 2010 projects:
- fixed tiff project to build tiff config headers
- properly added subsurface.h and subsurface.cpp to povbackend project
updating these files without change, in hope that an update of the RSC
keywords will fix the files from always popping up in
"reconcile offline work"
Change 5497 on 2011/09/22 by clipka@cli-pc-xp64
fix for FS#221 "Undefined looks_like object causes hard crash"
made POV_FREE macro safer to use
another fix for #5487
fix for stuff broken by #5487
reverted changes #5474 and #5477 and implemented new fix for FS#208; local
identifiers can now be passed out of macros without limitation.
Change 5486 on 2011/09/08 by jholsenback@jholsenback_aries
Resync changes and revision files with recent activities
Bump version to RC4
Update of benchmark.cpp related to #5480, #5477 and #5474
Follow up to change #5443 to retain a TODO comment

Follow up to change #5336 fixing FS#185
Follow up to #5474 and #5477 to avoid a second error message
Rolled back change #5470 (due to undesired side effects) and implemented
new fix for FS#165
Scene file update (follow up to #5475)
Fix a regression of 5474 (returning a local colour, vector or float symbol
(or any expression based on it) is not a problem, the symbol can be deleted
as the value(s) are already copied in safe zone.
Fix to scene file to not return a #local directly from a #macro:
- Related to change #5474 and FS#208: multiply #local by 1.
Fix addressing FS#208:
- Detects deletion of current symbol and reports the error
Fix addressing FS#165:
- The radius of the shooting cone was adjusted to include the whole sphere
- Enhanced "Photon message reporting" to address FS#190
- Correction for segfault introduced in change #5467
Follow up to FS#169 memory leak:
- Fixed the leak of 2 photon maps per frame to render. Became huge with
the animation FS#169 used (1189 frames) leak was about 9 gigabytes on
64 bit system.
Fix to avoid duplication of error message in parser reported in FS#215
Added a dump of the command line (unix only) when command-line option parsing
error is reported. This addressess FS#214 which was due to an alias that
would have been undetected without insight about an alias being used.
Finalized user contributed (jgehrcke) addressing FS#213
Corrections to fix introduced in change #5455
User contributed fix addressing endless loop condition reported in FS#213
Changed -V in unix option to --V (-version) to avoid conflict with
-V (verbose) from core that was reported in FS#204
Follow up to change #5450:
- removed now obsolete SceneThreadData members
Fix for UV mapping broken for parametric reported in FS#210
A fix for "Cannot open file" error reported in FS#206
- When text output files specified in INI) and added a few comments to path.h
and path.cpp. Current solution allows arbitrary file names for output stream
files; code for changing this to accept only "plain" file names is also
provided but currently disabled
Follow up to change #5447:
- Fix a valgrind complaint about reading uninitialised data
in renderfrontend.cpp
- Fix the issue with textures during tesselation with tessel{} and
tesselate{} that was crashing at render time if a vertex was not textured due
to using default texture on original object
Fix for computation of weighted textures problem reported in FS#209
Improved error message output when text in-/output files cannot be opened
Minor formatting cleanup to tiling.pov
Temporary fix for quick_color problem reported in FS#166
- Moved the setting of qualityFlags into the constructor of the TraceTask,

to avoid its value being overriden by the constructor of Radiosity
Add check for DF3 file without size FS#156
Fix for Radiosity artifacts at low error_bound FS#203
A follow up to change #5436
A user contributed fix to the HFCreate_ (shapes.inc) macro
Suppress "bound_by" warnings when Bevelled_Text (shapes.inc) macro is called
Fix for Calibri TrueType font garbled FS#200
Corrected scene file typos reported in FS#199
~scenes/textures/patterns/tiling.pov now has the capability to conditionally
write it's color_map to a text file.
Subsurface scattering improvements:
- added syntax to global subsurface block:
global_settings { subsurface { radiosity BOOL } }
specifies whether subsurface light transport effects should be applied to
incoming radiosity-based diffuse illumination; if this setting is
off (default), subsurface light transport effects will only be applied to
direct illumination from classic light sources. Setting this to on will
improve realism especially for materials with high translucency, but at a
significant cost in rendering time.
- added syntax to global radiosity block:
global_settings { radiosity { subsurface BOOL } }
specifies whether radiosity sampling should honor subsurface light transport;
if this setting is off (default), radiosity-based diffuse illumination is
computed as if the surrounding objects had subsurface light transport turned
off. Setting this to on may improve realism especially in the presence of
materials with high translucency, but at some cost in rendering time.
- Subsurface scattering is disabled in all quality levels except +Q9

or higher.
- More thorough fix to complement change #5425.
- Minor changes to reduce intensity of patterned noise artifacts on
subsurface textures.
added a temporary trap for certain subsurface conditions
Change 5424 on on 2011/03/19 by clipka@cli-pc-xp64
change to mitigate banding with dark subsurface pigments
change to fix a no-op -J option
change to fix memory access violation when closing braces in a funtion
were missing
added two scene files to the distribution
Change 5414 on 2011/02/27 by jgrimbert@experiment
change +IM command line option to +MI
change to mitigate problems introduced in change 5411
updated subsurface scattering sample scene
update SSLT code (various fixes and radiosity)
changes to improve robustness regarding low translucency and/or high
mm_per_unit settings for objects in general and blobs in particular
added support for CSG (caveat: unions of overlapping components will cause
unexpected results; use merge instead)
bugfixes & improvements to SSLT code;
syntax for material definition has changed as follows:
texture {
pigment { PIGMENT }
finish { ...
subsurface { translucency COLOR }
}
}
interior { ior FLOAT }
The pigment determines the SSLT material's overall appearance when applied
to an object with sufficiently large structures. The translucency color
(which can alternatively be a float) determines the strength of the
subsurface light transport effect (note that the values may be >1.0; also
note that the effect doesn't scale with the object; instead, to adjust
materials to the dimensions of your scene, use the global mm_per_unit
setting). The material's index of refraction also affects the appearance of
the material, and is mandatory for SSLT materials.
SSLT is now enabled only when a global_settings subsurface block is present;
to enable SSLT but use the default settings, specify an empty block,
i.e. "subsurface{}"
Due to the experimental status of SSLT, there are currently some caveats:
- Incorrect use may result in hard crashes instead of parse warnings.
- Pigments having any zero color components currently don't play nice with
SSLT; for example instead of "rgb 1" you should use something like
"rgb <1,0.05,0.05>". Use at your own risk!
Added these user contributed mesh_camera scene files to:
~scenes/camera/mesh_camera/ess
ess-ortho-camera.pov
ess-persp-camera.pov
ortho-camera.pov
persp-camera.pov
fixed bug causing "../../" in file paths to be stripped.
changed list of experimental features: removed radiosity, added subsurface
light transport
fix for using interpolated image_maps in functions results in pixel-sized
dot-artifacts
- A change to rewrite the 'ref=' tag as 'id=' in function GetAnchorInfo
- Changes in the function GetMDHash to support two image formats so they BOTH
can be recognized during migtation to the new format.
- A trap was added to alert if an unsupported image format is encountered.
----------------------------------------

update windows help file.
update windows insert menu.
Bump version to RC3.
add statusbar tooltip for windows version, primarily to allow full status
message to be shown on hover if its status bar section is too small.
merge changes 5382 and 5384 from jgrimbert branch to trunk, with modifications
to suit.
This adds a new INI parameter called Max_Image_Buffer_Memory (+IM), which
gives the number of megabytes of RAM to allow for output image caching.
If the output image would use more than this, a file backed temporary image
is used instead. If not specified, it defaults to 128mb.
since cooperate() is currently very low-impact, call it for every primary ray
as well as every 16th ray.
Don't create the in-memory output image if image output is turned off.
Change 5384 on 2011/01/16 by jgrimbert@experiment [jgrimbert branch]
I/O bottleneck, after benchmark: code rewrite from fs#180, ready to get some
parameters (from povray.ini) as soon as a way is possible.
Previous code kept under #ifdef, new code in #else; Clean-up up to code manage
rs.
Issues fixed from fs#180: height*weight not matching blocksize, removed
gigantic vector of bool, removed assumed wrong optimisation about small
width. Also fixed the flag for the open() call (granting only read & write to
the user so far)
Added meta information for 3rd party: at the end of the file/pixel array,
(use seek(END, -3*sizeof(size_type)) to get ready to read them)), 3 size_type
values: size of a pixel in byte, witdh & height.
Committed for next urgent RC.
Change 5383 on 2011/01/15 by nkopp@cc-devel-test
Fix bug that occasionally caused a crash in scenes with media (the bug was
introduced by an earlier refactoring)

Change 5382 on 2011/01/11 by jgrimbert@experiment [jgrimbert branch]
Remove the I/O bottleneck (it's even worse than that) due to storing the
pixels in progress in a file whenever the rendering dimension is big enough.
The cost is 64 lines of data cache instead of 1 line. (as long as +BS is not
bigger than 64 (better with 32) and that the order of block rendering is per
line (as it is per default, so change at your own risk with big images))
two FixTags additions to filter out indexentry and sectiondesc tags because th
ey aren't need anymore.
a fix to remove an extra closing div tag exposed by html validation
deleted old header info (my bad) to scene files
author updates and additions to scene files
remove obsolete scene files. author contributed replacements to follow.
FixTags addition to clobber "<" and ">" with escaped html versions. Most of
the offenders occurred in pre blocks where vectors were being represented. My
guess is someone just copy and pasted direct from a scene file into the
original html docs.
more extra or missing tag fixes that caused html validation errors
fixed misplaced opening table row tags that were causing html validation
errors (3 places)
add boost/function.hpp to povray.h to fix compilation issues on some unix
systems.
--------------------------------------Changes between 3.7.beta.41 and 3.7.RC2
--------------------------------------Change 5360 on 2011/01/06 by chrisc@x8
updates to SimpleVector usage to allow easy declaration of limits in platform
include files. also increase default sizes.

fix FS#188 (no_reflection broken)
Change 5347 on 2011/01/05 by chrisc@cc-ubuntu-test
fix signal handling issue reported in FS#187.
bump version to RC2.
fixed bug FS#186; parser will now adjust sub-polygon end points to exactly
match the start points.
disable full memory allocation tracking on windows in favor of rougher
estimate based on samples of peak memory usage from windows API. also some
other misc changes to windows code.
fix crash found by crashdump #77 (platform base can be NULL before the image
class gets destroyed in the case of unusual shutdown).
fix crash in editor where FormatMessage() fails. refer crashdump #76.
fixed gamma showcase scene
update about box to read 2011, also fix some mis-alignment and other small iss
ues.
Change 5337 on 2011/01/04 by nkopp@cc-devel-test
Minor refactoring of media+photon code
fixed FS#185 (wrong message about image resolution)
fix for FS#184 (Too many pretrace steps when pretrace_start < pretrace_end).
A parse error will now be generated if pretrace_start < pretrace_end.
add windows help file.
updated insert menu files.

add in very basic support for running shell-outs on unix.
hack around shellout permission issue in unix version (use a global for the me
antime). untested.
update built-in win demo scene for 3.7.
removing beta status, moving to RC. no more timeouts.
benchmark results on windows are now copied to the clipboard.
a few changes due to observations made during analysis of crash dumps. no
ultimate cause for crashes involved yet determined due to insufficient
information in the minidump.
some work on photon statistics.
Change 5315 on 2011/01/01 by chrisc@cc-devel-test
Photon fixes from Nathan.
using "color srgb" (or similar) before assumed_gamma was defined resulted in
a hard crash; fixed by generating a proper parse error instead.
modified radiosity3.pov tutorial scene to use more realistic surface finish
updated scenes that will feature in the radiosity tutorial, to be more
fitting for POV-Ray 3.7
changes to suppress assumed_gamma warnings
release changes #version and assumed_gamma

make windows status pane a bit wider and add process memory usage slot in
status bar.
fix memory leak.
go back to using the current version as the default language version and
modify the warning messages associated with a missing or late #version.
last-minute backward compatibility update:
Gamma Handling:
The assumed_gamma keyword is no longer deprecated; to the contrary, it is
now considered mandatory if a #version 3.7 or higher is specified, and its
absence will raise a "possible error" in this case, with a value of 1.0 bein
g
presumed. (Note that #version, too, is now mandatory, and its absence will
raise a warning as well).
The assumed_gamma value is now presumed to denote the "working color
space", in which classic color literals are specified and color
computations to be performed. Note however that this will give unrealistic
results for any value other than 1.0.
Colors specified using "srgb" & co. will be converted from sRGB to the
working color space.
image_map input files for which definitive implicit or explicit gamma
information is available (either by file format specification like the HDRI
formats, header information like PNG with sRGB or gAMA chunk, or a user
override via the "gamma" keyword) will be converted to the working color
space. If no definitive information is available, the respective files will
be presumed to match assumed_gamma if #version is < 3.7 or unspecified, or
any official recommendation if #version >= 3.7 is specified.
height_field, bump_map and image_pattern input files will not be subject to
gamma-adjustment, unless the user explicitly specifies an override via the
"gamma" keyword; in that case, the file is presumed to match the gamma
value specified, and converted to linear values, irrespective of
assumed_gamma.
Concerning anti-aliasing, for the decision whether to anti-alias the color
values will be converted from the working color space to that specified by
the Assumed_Gamma INI setting; the averaging of the samples however will be
performed in the working color space.
For render preview, the generated image will be converted from the working
color space to that specified by the Display_Gamma setting. If
Display_Gamma is not specified, a platform-specific default will be
presumed.
For file output, the generated image will be converted from the working
color space to whatever the file format mandates (this applies to OpenEXR
and Radiance HDR); if no such mandatory color space exists, the image will
be converted into that specified by the File_Gamma setting. If File_Gamma
is not specified either, the image will be converted into whatever is
officially recommended for that file format, or the de-facto standard; if
even that doesn't exist, no gamma adjustment is performed. In any case, if
the file format provides a means to specify a gamma in the image header
(this applies to PNG), the respective data is set according to whatever
gamma the image is converted to, regardless of the working color space.
If assumed_gamma is not specified, and #version is set to pre-3.7 or
undefined, no gamma handling is performed at all.
In terms of backward compatibility, this translates as follows:
If assumed_gamma is not specified, and #version is set to pre-3.7 or
undefined, full compatibility with 3.6 and earlier is maintaned.
If assumed_gamma is specified and #version is set to pre-3.7 or undefined,
compatibility with 3.6 is subject to the following restrictions: (a) full
output file handling compatibility requires File_Gamma to be set to the
same value as Display_Gamma (or left undefined if Display_Gamma is
undefined), and (b) input file handling is not backward compatible in case
of PNG files.
If assumed_gamma is not specified and #version is set to 3.7 or higher,
compatibility with 3.6 or earlier is not maintained.
-------------------------------------------Changes between 3.7.beta.40 and 3.7.beta.41
-------------------------------------------Change 5286 on 2010/12/20 by chrisc@x8
fix code list control appearing on primary monitor while povwin is on non-prim
ary monitor.
make render window sanity check smarter with respect to multiple monitor
s.
add INI keywords to highlight list for editor.
last-minute update to colour syntax for gamma pre-corrected colours; dropped
the "gamma" keyword there (it remains enabled for image input files) in favor
of the following syntax:
colour
colour
colour
colour
srgb <Rp,Gp,Bp>
srgbt <Rp,Gp,Bp,T>
srgbf <Rp,Gp,Bp,F>
srgbft <Rp,Gp,Bp,F,T>
where Rp,Gp,Bp are colour component values pre-corrected for a display

conforming to the sRGB colour space, and F,T are linear colour component
values.
update benchmark INI file to reflect removed/added options. update
compiled-in benchmark file to match one in distribution.

implement requirement for "#version 3.7" to be provided to obtain full v3.7 fu
nctionality.
prior to a #version statement appearing, the version defaults to 3.62.
additionally, if the first #version appears after any other declaration, or
#version does not appear at all, a post-parse warning is issued.
default to boost::thread_specific_pointer for taskDataPtr with compilers that
don't support native TLS.
integrate changes 5273 and 5275 from jgrimbert branch to trunk.
5275: comment out dead (and bogus) code in Poly object, raising max or
der to 35 because 15 was too small
(someone needed a 16th order), and add a new syntax to describe
a polynomial equation (it's an addition,
the old way is kept):
5273: fs#179 proposal for simple fix (tested) to missing $HOME
comment out dead (and bogus) code in Poly object, raising max order to 35
because 15 was too small (someone needed a 16th order), and add a new syntax
to describe a polynomial equation (it's an addition, the old way is kept):
polynomial { <order>, [xyz(<a>,<b>,<c>):<value>,]* [remaining as usual for p
oly]}
Default value for all coefficient is 0.0;
each xyz(): set the coefficient to <value> for x^a.y^b.z^c;
(constant is xyz(0,0,0)). Ordering of xyz is irrelevant (but identical i
ndex keep only the last one)
a sphere (radius 1... x^2 + y^2 + z^2 -1 =0)
polynomial{ 2, xyz(2,0,0):1, xyz(0,2,0):1, xyz(0,0,2):1, xyz(0,0,0):-1 }
fix bug FS#182 (multi-textured blobs in intersections / differences broken)
fs#179 proposal for simple fix (tested) to missing $HOME
changed the mechanism to retrieve & format the current time from SDL; new
syntax is as follows:
- The keyword "now" evaluates to the time elapsed since 2000-01-01, 00:00:00
GMT in days, with a precision of seconds or better.
- The function "datetime(FLOAT [,STRING])" interprets the FLOAT as days
since 2001-01-01, 00:00:00 GMT, and the STRING as a formatting string (sam
e
format and default as was previously taken by "now([STRING])").
Consequently, "datetime(now)" does what previously "now()" did, and
"datetime(now,STRING)" does what previously "now(STRING)" did.
deprecate histogram output. some fixes to create_ini output.
insert menu render fixes.
avoid crash condition in editor find/replace if memory allocation fails.
follow up to address compilation error introduced with change #5261
see if this fixes the fseek64 issue on linux.
better handling of bad alloc and runtime error exceptions during message
processing (don't pass them up to the main thread).
work around double-free causing memory corruption and later crash when create
scene (or probably any POVMS callback function) threw an exception.
make windows frontend more aware of backend failures.
change main thread and povray init to accept a callback to notify when the
main thread exits. this is needed to make sure the front end knows of a
premature exit of the backend thread and to avoid using the (now deleted)
message queue.
POVMS_Send now reports a timeout when one happens.
Added new include file, "ior.inc", defining ior & dispersion constants for a
lot of materials.
Added new sample/test scene, "scenes/gamma/gamma_showcase.pov" (used in new
gamma section in the docs)

disabled #default { image_map { gamma ... } } statement; may be re-enabled in
future versions, probably with a different syntax
re-enable show_clouds in the builtin benchmark scene
Display gamma handling was broken in two places; fixed.
remove obsoleted code (image_map gamma)
remove obsoleted code (image_map gamma)
Fixed metadata time zome bug introduced with #5210 (see FS#64 comments);
POV-Ray will now write proper Zulu time into the metadata again.
added dither method information to options output
Fixed a few flaws that caused the dither INI options & command line parameter
to not work properly; added dither support for Radiance HDR
Dithering Support / Gamma Improvements / Code Refactoring:
Add support for output file dithering; dithering is controlled by the INI
file settings "Dither=BOOL" and "Dither_Method=xx" as well as the command
line option "+/-THxx", where xx is one of:
"B2".."B4": Bayer pattern dithering using 2x2, 3x3 or 4x4 patterns, respecti
vely
"D1": simple 1-dimensional error diffusion dithering
"D2": simple 2-dimensional error diffusion dithering (needs extra memory for
2 pixel rows)
"FS": Floyd-Steinberg error diffusion dithering (needs extra memory for 2 pi
xel rows)
The default is "-THfs", i.e. dithering is off, with Floyd-Steinberg being the
default if only "+TH" is specified.
Dithering works for all file formats except JPEG and OpenEXR (no intention to
implement) as well as Radiance HDR (non-straightforward to implement); these
file formats simply ignore the setting.
Added dithering to reder preview, using 4x4 Bayer dithering.
Display_Gamma now supports the "sRGB" option just as File_Gamma already did;
besides "sRGB", "srgb" and "SRGB", any combination of upper-/lowercase
letters is now recognized.
Moved image data quantization / encoding / decoding functions from
image.h/cpp to new files encoding.h/cpp.
fix divide-by-zero crash in editor support code (refer crash report #50).
change default update check period to one day in lead-up to final release.
make sure simplevector.h pulls in pov_err.h.
expand uses of FixedSimpleVector<64> to 127 elements. this doesn't fix the iss
ue
of course but will mitigate it a bit at the cost of increased memory usage.
bump version to beta.40.
fixed bug causing interpolated image maps to be shifted by half a pixel, as
described in news://news.povray.org:119/4bdad2a5@news.povray.org.
mitigate issue with crackle sometimes chewing up huge amounts of RAM. see
FS#56 for more details.
NB this fix is not ideal, in particular we ought to provide an INI setting to
allow the user to nominate how much RAM they want to use for the cache.
currently it's hard-coded to roughly 30mb per thread max during a block, and
15mb per thread when a block is cleaned up after it's done. if the size of
the cache would exceed the upper hard limit, new entries will not be cached.
differentiate between hitting the limits of the fixed vector class and actual
memory allocation failure.
improve reporting of uncategorized or unknown exception codes to aid in
tracking down the cause.

add ovus.cpp/h to windows projects.
integrate changes 5188 to head from jgrimbert branch into trunk.
adding the ovus code (#5200 & #5201) which was missing.
integrate change 5183 to trunk.
improved alpha premultiplication handling for pattern images
metadata improvements:
- Using boost::posix_time and boost::date_time::gregorian now for timestamp
computations rather than boost::date_time::c_time (which is not thread-safe
on some platforms).
- Moved TGA file format-specific timestamp generation code out of Metadata
class.
- PNG output now also writes a tIME chunk.
- Modified PNG metadata handling to be thread-safe.
- Fixed PNG chunk order to place tEXt chunks before image data, as required
according to PNG specification.
minor code cleanup:
- replaced min3/max3 macros in configbackend.h and MAX3 macro in octree.h
with new template functions min3/max3 in types.h
- removed some obsolete constants from frame.h
- eliminated a few unnecessary include statements, and made boost include
statements more consistent
fixed 5203: the map is now simpler (all centers of tile is at i/num, border
at (i+1)/num) (for i from 0 to num-1). The gradient on each tile is the same
for every tiles on the same tiling.
Multiple changes to gamma handling:
Removed file_gamma keyword. Input image file default can now be set via
default { image_map { gamma FLOAT } }
or
default { image_map { gamma srgb } }
For backward compatibility with legacy scenes, POV-Ray 3.7 will now mimick
all the gamma handling of POV-Ray 3.6 if the scene has a #version statement
specifying a version of 3.6x or earlier, and/or specifies an assumed_gamma,
with the following exceptions:
* If the scene overrides the default input file gamma, POV-Ray will fall
back to the new gamma handling model.
* If the
an INI
later,
output
scene is rendered using the File_Gamma INI file setting, or using

file setting or command-line option to specify a version of 3.7 or
input file gamma handling will still mimick 3.6 behaviour, but
file gamma handling will use the new model.
* PNG input file handling is not fully backward compatible.

Due to architectural changes, bug fixes and improvements, backward
compatibility for PNG input files is subject to the following exceptions:
* For palette-based PNG files (an uncommon flavour of PNG), backward
compatibility is provided only if assumed_gamma is not specified. (This is
due to a POV-Ray 3.6 bug not mimicked by POV-Ray 3.7.)
* For non-palette-based PNG files, backward compatibility is provided only
if assumed_gamma is specified. (This is due to an architectural change tha
t
makes this overly difficult to mimick.)
* For PNG files carrying both an sRGB chunk and a fitting gAMA chunk,
results will slightly differ. (This is due to POV-Ray 3.7 recognizing sRGB
chunks, which POV-Ray 3.6 did not do.)
* For PNG files carrying an sRGB chunk but no gAMA chunk (or a wrong one),
backward compatibility is not provided. (Again this is due to POV-Ray 3.7
recognizing sRGB chunks.)
Older platform SDK's don't have PROCESS_MODE_BACKGROUND_BEGIN defined.
Adding pavement & tiling patterns.
tiling # (#: 1 to 24) provide 24 classical tiling pattern with 1 or more kind
of tiles.
The full map is used when rendering a tiling. 0 is the center of first tile.
1 is the border of the only tile, or the center of another tile.
When more than one kind of tile is used (#), the border are at 1/#, 2/#, ... #
-1/#
(would it be simpler to have the border at 0/#, 1/#... #-1/# ? and center at
1/#-, 2/#-, #/#- ? might be amended later)
pavement: (using polymino paving the plane)
* number_of_sides (3,4,6) : the basic tile is a triangle, a square or an
hexagon
* number_of_tiles (1 to 5 or 6): the number of basic tiles to combine togethe
r
to make one real tile
* pattern (depend on side & tile) (1 to ...): how the basic are combined
together
* exterior (1 to 3, irrelevant for hexagon)
* interior (1 to 3)
* form (1 to 3, or 1 to 4 for square)
Variations on type of corner. 0 is plain, 1 is a straight cut, 2 is a curved c
ut.
All complet sets are covered.
Add square & triangular pattern (2D, in xz plane, 4 & 6 area in shape of squar
es and triangles)
Adding bitwise operation (bitwise_and(), bitwise_or(), bitwise_xor()) Similar
to max(), not limited to 2 parameters.
Also provide keywords for ovus object
Add the ovus shape. Documentation in french at http://jgrimbert.free.fr/pov/pa
tch/ovus.html
It's like a torus, but in egg shape ...
ovus { base_radius, top_radius }
(top_radius < 2.0*base_radius or else it's just a sphere)
Retrofit of my old patch from povray 3.1; The code is mine (it
with equations, eight years ago), so I can here license it for
distribution. Egg, Avocado, Head... plenty of usage (for head,
upside down with a slant, the top radius is ready to match the
was a fun time

official
rotate it
jaws)
Change 5196 on 2010/11/22 by jgrimbert@grimbert

Experimental, add exterior type 7 & 8 for fractal pattern, using the number
of actual iteration to get out (=e) and the factor (=n). 7 gives back
mod(e,n)/n (covering 0 to n-1/n), while 8 covers 0 to 1 with mod(e,n+1)/n.
Not protected against silly n (like n<1) so far.

update support for file-backed RGBFT images to allow 64-bit seek offsets.
NOTE: platforms that do not implement fseek64() must provide one (either a
function or #define).
add code to automatically switch to using file-backed intermediate images
when width >= 32 and pixel count >= 1024*1024.
Add new option to set render priority to background (only available on Vista o
r later).
Add note to crash handler dialog mentioning the continue option.
Make standard minidump output more verbose as current dumps are a bit too
sparse to be helpful in some cases.
fix issue where a shutdown after a render that allocated a lot of memory
blocks (or any other case where the shutdown takes more than five seconds)
could throw an uncaught exception. this could then cause the 'terminated in
an unusual way' windows error message.
fix issue introduced with #4979 that would cause gamma to be screwed up with
non-transparent TGA input files
fixed target platform metadata
fixed #5183: the display of Frame Step was last frame when the Frame Step
option was not used.
Revision of Fractal fields in pattern structure to allow deeper iterations
(past 32767, now upto 2^32-1) for fractal patterns. Footprint of structure
should stay the same, as the fields for types (interior & exterior) have been
reduced to unsigned char (only 0 to 6 used so far, whenever the number of
types reaches 255 it will be time to revert to a short)
+STP / Frame_Step= , animation option inspired from megapov with two
restrictions: only positive step value are supported (forward, no backward
rendering) and the value is not available in the SDL (it won't be costly to
add it now as a #declare, but philosophicaly it should not be visible: we are
just rendering non consecutives frames, the clock & frame number (as well as
delta) should not affected).
At the same patch, the return of the display of the Animation Options, right
after the Parser Options (well, inside the parser option in fact). (it does
not display the actual clock information when animation is on, only the
animation's parameters)

turn a pov_base::Exception thrown during parse into a parse error. this
allows the line number of the error to be reported. see FS#80.
fix FS#168 (noise_generator default broken)
Add invalid parameter handler, will now throw kParamErr exception when the
RTL complains about invalid parameters.
Merge changes 5167, 5168, 5169, 5170 and 5171 to trunk with a number of change
s.
All: Replace spaces with tabs where appropriate.
#5169: Some bugfixes, formatting changes.
#5170: Some bugfixes.
#5170: Removed 'input_file_name' token; this is now implemented via an
automatically-inserted declare (see #5175).
#5170: call to localtime_r changed to boost::date_time::c_time::gmtime() to
avoid platform portability issues (windows doesn't have the _r variant)
and
to use GMT as the default timezone (so we can insert Z into the time st
ring
rather than relying on strftime returning an ISO 8601 compliant string
for '%z').
#5170: Call to strftime wrapped with try/except and windows code modified to
raise kParamErr upon the vc RTL calling the CRT invalid parameter handl
er
(which would otherwise cause program termination when users pass an inv
alid
formatting string).
Add support for passing ASCII strings via kPOVAttrib_Declare.
Add pre-declared variable 'input_file_name' to vfe setup code.
Addendum to #5170 (fs#134): protect the string returned by now("...format
string...") against error in format string ending in a too long answer for
the allocated array. Also use a #define for the size of that array, so it's
easier to change it if needed.
fs#134 : provide SDL with "input_file_name", a token replaced by a string
which is the name of the input file of the scene; and a string returning
function "now()".
now() can have a string parameter (but can also be used without; the
parenthesis are mandatory anyway).
When provided with a string, its value is used for formatting the current
local time. Formatting documentation is the one of strftime() C function.
(LC_TIME is taken into account too, so "%x" "%X" and "%c" might be different
from one system to another)
Without parameter (that's not 'now("")', but 'now()' ), the format is
"%Y-%m-%d %T-%z"
You can get the number of second from Epoch with "%s" (and for other
possibilities, have a look at the man page of strftime). (whatever can the
Epoch be on your system)
The final string is limited to about 200 glyphs (or char), you should not
need as much for a printable time.
FS#105: the return of the Output Options (with minor corrections about Jpeg
quality handling, and default row & columns start/end): The TODO about
filename/path are fixed using similar approach in Parser Options (going the
UCS2 way first, then converting to ascii).
Rendering order replaced with distinct rendering options: pattern (-RP /
Render_Pattern) and block step (-RS / Render_Block_Step)
Pattern is now (unsigned) positive, default to 0 (as previous)
Block Step is as previously, reduced to a pseudoprime with height*width (in
block count)
Now a given pattern and a block step can both be specified at the same time.
Adding a final version for RenderOrder (-RO) option: default remain as previou
sly
(from left to right, then top to bottom). Default is 0 (as well as 1)
with -1, it's top to bottom, then left to right
with -2, it's closing from left & right to center, top & bottom alternatively
to middle
with -3, it's the opposite from -2 (starting at center-middle, going left &
right, then to top & bottom)
with -4 it's -2 rotated (like -1 is to 0): closing top & bottom to middle,
alternatively left & right to centre
with -5, it's the opposite from -4 (starting at middle-center)
with N > 0, it's about 1 square every N (about: N might get reduced to allow
clock arithmetic to cover the whole picture: N must be pseudo-prime with
number of blocks to render; at worst it is shrinked to 1... the default)

merge changes 5162-5165 to trunk.
fs#154 : get owner & group of $HOME to assert the ownership of povray.conf &
povray.ini in $HOME/... subtree during installation (should be now
fine with both "sudo make install" from joe user, and "make install"
from root user)
fs#64 : add metatags to output image (excepted for BMP, there is no room in BM
P
format for comment).
The date of creation, the software name and 4 lines of additional text
(recommended to stay under 80 char), all in ASCII.
So far the 4 lines are just kind of constants depending from the compilation
option. If you have a better usage for these lines, just go for it.
fs#167 : force the computation on resize() to happen on unsigned long int by
either adding ul qualifier to existing constant or by introducing a
1ul factor in all resize (w * h ...) calls.
fs#167 : force the computation on resize() to happen on unsigned long int by
either adding ul qualifier to existing constant or by introducing a
1ul factor in all resize( w * h ...) calls.
fs#64 : add metatags to output image (excepted for BMP, there is no room in
BMP format for comment).
The date of creation, the software name and 4 lines of additional text
(recommended to stay under 80 char), all in ASCII.
So far the 4 lines are just kind of constants depending from the compilation
option. If you have a better usage for these lines, just go for it.
fs#154 : get owner & group of $HOME to assert the ownership of povray.conf &
povray.ini in $HOME/... subtree during installation (should be now fi
ne
with both "sudo make install" from joe user, and "make install" from
root user)
handle case where INI file has old paths due to setup changes.
Change 5156 on 2010/09/13 by chrisc@build
add sse2 DLL's to setup.
integrate changes from 32-bit installer.

convert branched 32-bit installer to suit 64-bit platform.
update to beta 39, add crash dump submit binary, and fix install location issu
e.
update 32-bit install script to allow attempted install to program files even
if not elevated.
-------------------------------------------Change 5140 on 2010/09/02 by jholsenback@jholsenback_aries
update revision.txt and changes.txt prior to beta-39 release
bump version to beta 39
add max ray distance to camera definition, also marks mesh camera
as experimental.
added mesh_camera demo scenes
fix for bug introduced with change #5124
consistency change with recent built-in benchmark. reference change #5105
Add mesh_camera to available camera types.
The mesh camera is a special camera type that allows complete control of
the ray origin and direction for each pixel of the output image. The basic
concept is to associate pixels with faces defined within a mesh or mesh2
object. The mesh need not be instantiated in the scene, though it can be
(and doing so can lead to some interesting uses, such as texture baking
or illumination calculations).
In its simplest form, each pixel of the output image is assigned to a face
of the mesh according to (width * (int) y) + (int) x. However, more complex
mapping is possible via multiple meshes and multiple rays per pixel. The
type of mapping in use is determined by the distribution method parameter
in the camera declaration. Except for mapping #3, the ray origin will be
set to the centriod of the face, and the direction will be that of the
face's normal. For mapping #3, barycentric co-ordinates are determined
from the UV co-ords of the first face to match the X and Y position, and
those are then coverted to a position on the face which will serve as the
ray origin. Support is provided to move the origin off the face along the
normal, and to reverse the ray direction.
For most of the distribution methods, any POV feature that causes subpixel positioning to be used for shooting rays (e.g. AA or jitter) will
not do anything useful, because X and Y are converted to integers for
indexing purposes. At this time, no warning is issued if AA etc is
requested when rendering a non-applicable distribution; this may be
added later.
The syntax for the mesh camera is currently as follows:
camera {
mesh_camera {
rays_per_pixel
distribution_type
MESH_OBJECT
[MESH_OBJECT ...]
}
[location]
[direction]
[smooth]
}
rays_per_pixel:
This float parameter controls the number of rays that will be shot for each
pixel
in the output image. Each distribution allows different values, but the mini
mum is
always 1.
distribution_type:
This float parameter controls how pixels are assigned to faces, as documente
d below.
distribution #0:
This method allows single or multiple rays per pixel, with the ray number
for that pixel allocated to each mesh in turn. The index into the meshes
is the ray number (where rays_per_pixel > 1), and the index into the
selected mesh is the pixel number within the output image. If there is no
face at that pixel position, the resulting output pixel is unaffected.
You must supply at least as many meshes as rays_per_pixel. Each pixel is
shot rays_per_pixel times, and the results averaged. Any ray that does not
correspond with a face (i.e. the pixel number >= face count) will not
affect the resulting pixel color. Generally, it would be expected that
the number of faces in each mesh is the same, but this is not a requiremen
t.
Using multiple rays per pixel is useful for generating AA (since standard
AA
won't work) or for special effects such as focal blur, motion blur, and so
forth, with each additional mesh specified in the camera representing a
slightly different camera position.
Note that it is legal to use transformations on meshes specified in the
camera body, hence it's possible to obtain basic AA by using a single mesh
multiple times, with subsequent ones jittered slightly from the first,
and a suitable rays_per_pixel count.
distribution #1:
This method allows both multiple rays per pixel and summing of meshes; i.e
.
the faces of all the supplied meshes are logically summed together as if
they were one single mesh. In this mode, if you specify more than one ray
per pixel, the second ray for a given pixel will go to the face at (width
*
height * ray_number) + pixel_number, where ray_number is the count of rays
shot into a specific pixel. If the calculated face index exceeds the total
number of aces for all the meshes, no ray is shot.
The primary use for this summing method is convenience in generation of
the meshes, as some modellers slow down to an irritating extent with
very large meshes; using distribution #1 allows these to be split up.
distribution #2:
Distribution method 2 is a horizontal array of sub-cameras, one per mesh
(i.e. like method #0, it does not sum meshes). The image is divided
horizontally into #num_meshes blocks, with the first mesh listed being the
left-most camera, and the last being the right-most. The most obvious use
of this would be with two meshes to generate a stereo camera arrangement.
In this mode, you can (currently) only have a single ray per pixel.
distribution #3:
This method will reverse-map the face from the UV co-ordinates. Currently,
only a single ray per pixel is supported, however, unlike the preceding
methods, standard AA and jitter will work. This method is particularly
useful for texture baking and resolution-independant mesh cameras, but
requires that the mesh have a UV map supplied with it.
You can use the smooth modifier to allow interpolation of the normals at
the vertices. This allows for use of UV mapped meshes as cameras with the
benefit of not being resolution dependant, unlike the other distributions.
The interpolation is identical to that used for smooth_triangles.
NB if used for texture baking, the generated image may have visible seams
when applied back to the mesh. This can be mitigated; see Jaime Vives
Piqueres sample scripts. Also, depending on the way the original UV map
was set up, using AA may produce incorrect pixels on the outside edge of
the generated maps.
mesh_object:
One or more mesh or mesh2 objects to be used for the camera. These will be
treated differently depending on the distribution method, as explained above
.
Transformations on the meshes can be used here, and will reflect on the
resulting image as it would be expected for a regular camera.
location:
On this special camera, location doesn't affect where the camera is placed
per se (that information is on the mesh object itself), but is used to
move the origin of the ray off the face, along the normal of that face.
This would typically be done for texture baking or illumination
calculation scenes where the camera mesh is also instantiated into the
scene (usually only a tiny amount of displacement is needed).
The X and Y for location is not currently used, and the Z always refers
to the normal of the face, rather than the real Z direction in the scene.
direction:
Like location, this doesn't correspond to the real direction vector of the
camera. It serves only to reverse the normal of all the faces, if
necessary. If the Z component is less than -EPSILON, then the rays will be
shot in the opposite direction than they would otherwise have been.
X and Y are not used.
Potential uses of the mesh camera include:
o Calculation of illumination on a surface represented by a mesh.
This was the first use of the mesh camera; a NASA JPL project
wished to calculated watts/m2 of illumination across a portion
of the moon's surface, for which they had a detailed grid and
hence were able to create a mesh.
o Texture baking (creation of an image suitable to be used as a UV
map). Given a mesh with UV co-ordinates defined, POV-Ray can generate
an image that can be later used in either POV itself or any modelling
application that can load UV-mapped textures. This means that any of
POV-Ray's native textures may be baked to a map (however note that
use of transparency on objects will give a confusing result).
o Any arbitrary camera shape, including all existing POV-Ray cameras
(though of course there is little point in replicating an existing
camera).
o Precise modeling of optical aberrations in lenses (presuming data is
available to generate a mesh that follows the aberrations). It may
also be possible to model a lens that reverses such abberations if
the scene being rendered has an image map containing an image taken
through the lens.
o Modeling optical devices that employ filters, such as camera CCD's
(by having a mesh that defines R, G and B image sensor elements and
the color filters that are typically overlayed on them).
o Any effect that could be achieved by shooting multiple rays for a
single pixel from different locations (or in different directions)
and averaging the results.
o Simulation of compound eyes such as those of insects.
o Certain types of animation (where only the camera moves), using
distribution #2 and a post-processor to split the output image.
This can be useful for scenes that take a very long time to parse
compared to the time taken to render (which can be an impediment
if using the traditional POV clock-based loop).
o If a means of limiting the maximum ray length is added, then a mesh
camera could be used to probe a scene to generate voxel or slice data
(the latter is useful for generating STL data for 3d printers).
Examples (placement macros not included for brevity):
// Stereo camera:
camera {
mesh_camera {
1 2
mesh {
camera_mesh
meshcam_placement(c_location_left,c_look_at)
}
mesh {
camera_mesh
meshcam_placement(c_location_right,c_look_at)
}
}
location <0,0,-.01>
}
// Texture baking:
camera {
mesh_camera {
1 3
mesh2 {vase1}
mesh2 {vase1}
mesh2 {vase1}
}
location <0, 0, -0.01>
direction <0, 0, 1>
}
Fix for a few Linux compiler warnings
Fix for some Microsoft-isms and other flaws introduced with changes #5109
and #5111.
a few misc changes/fixes, including support (not enabled) for ASCII PPM
output [handy for text processing of output image during testing].
fix for use of templated version of min().
fixed a bug in radiosity introduced with change #5112 that could cause
samples to be re-used too far away
Added support for focal blur with user-defined bokeh, using the
following syntax:
camera {
// ... focal blur camera...
bokeh {
pigment { ... }
}
}
If bokeh is specified, focal blur will use a custom sampling sequence based
on the specified pigment's brightness in the range <0,0,0> to <1,1,0>, i.e.
the unit square in the XY plane.
Parser failed to eat away the parameter value after the obsolete
"max_intersections" keyword, causing it to crash instead of gracefully
ignoring it with a warning; fixed.
fixed some dormant photons code that, according to code inspection, was
broken with radiosity change #4761
Radiosity improvements:
- Removed the max 1600 count limit; if the count exceeds 1600, POV-Ray will
now use a Halton sequence instead of the built-in sequence.
- POV-Ray can now draw sample directions in a round-robin fashion from a
larger pool, so that different samples can use different sets of sample
directions, leveraging the benefit of the nearest_count mechanism.
For this purpose, the count keyword syntax has been changed:
count RAYS_PER_SAMPLE [, DIRECTION_POOL_SIZE ]
- Added importance sampling to radiosity; full ray computations are
performed only for a certain portion of sample rays, depending on the
importance of the first object each ray encounters. Importance can be
assigned on a per-object basis using the followng syntax (using a sphere
as an example):
sphere { ... radiosity { importance IMPORTANCE } }
where IMPORTANCE is a value in the range from >0.0 to <=1.0 specifying the
percentage of rays to actually compute on average. A particular ray will
only be fully computed if it is within the first COUNT*IMPORTANCE rays of
the sampling sequence; due to the low-discrepancy sub-random nature of the
sequence, this is mostly equivalent to a per-ray weighted random choice,
while maintaining a low-discrepancy uniform distribution on a per-object
basis. Rays actually computed are weighted to compensate for those
not computed.
Objects derived from previously defined objects will default to the
"inherited" importance. CSG components without an explicit importance will
default to their parent object's importance. Other objects normally
default to an importance of 1.0, but this can be changed in a
default {} block:
default { radiosity { importance DEFAULT_IMPORTANCE } }
NOTE: The "radiosity on|off" feature for objects (specifying whether an
object shall receive radiosity illumination) is currently NOT available.

Depending on user feedback, it will be substituted with some keyword
within the object-specific radiosity{} block, or dropped completely.
- Some more minor modifications.
Improved focal blur:
- Modified code to generate extra samples in a circular rather than square
pattern when blur_samples is not 4, 7, 19 or 37, leading to a circular
rather than square bokeh.
- Modified the code that re-placed an extra sample if it would be close to
another one, in order to get rid of the lower-right bias the old
code produced.
- Extra samples are now generated from a halton sequence rather than a
random stream.
- Modified blur_samples syntax to optionally specify a minimum number of
samples to be taken before testing against confidence/variance settings
(default is 4 if blur_samples maximum is <7, otherwise 7), to provide a
means to get rid of stray non-blurred pixels. The new syntax is:
blur_samples [ MIN_SAMPLES, ] MAX_SAMPLES
- Eliminated the VEC2 type in favor of Vector2d.
- Simplified a few statements and did a bit of cleanup.
SSLT improvements:
- Fixed a bug in SSLT code that caused the single-scattering
term to be ignored.
- Using halton sequence instead of random generator for picking sampling
directions, to reduce visible patterns in noise.
Introduced new framework for internal random number generators, intended for
reducing the memory footprint (by sharing precomputed values among
generators with identical parameters) as well as easier replacement of
implementations.
minor code simplification in aoi pattern
changed Output_File_Type to type "n" reference FS#155
changed radiosity defaults to "always_sample off" and "recursion_limit 2"

corrected 1 pixel error in mosaic preview see FS#114
fix for FS#162 "Character 101 (0x65) not found in /usr/share/fonts/truetype/fr
eefont/FreeSans.ttf"
Installer changes suggested in article <web.4c558a54f4269f7c380f8080@news.povr
ay.org>
fixed a preprocessor definition in Win32-SSE2 console project
removed duplicate references to Windows system libraries
Remove soft expiration from unixconsole.cpp.
fix parse warnings reported in FS#157
fix name of editor DLL when building SSE2 binary.
enable editor DLL build by default in solution.
fixed bug FS#158 in render options output code, causing a wrong value to be
reported for antialiasing gamma
shellout fix.
fix error in windows version expiry test.
modified code to avoid even more deprecation warnings with libpng 1.4;
NEEDS TESTING with both 1.2 and 1.4!
properly allow for libpng 1.25 AND 1.4.3

Rollback //depot/povray/smp/unix/configure.ac to revision 41
modified code to avoid deprecation warnings with libpng 1.4;
NEEDS TESTING with both 1.2 and 1.4!
sample scene vector typo corrections FS#110
configure updates for libpng 1.4 you MAY want to defer this until
change #5031 is completed.
Added support for using the sRGB transfer function for output file gamma;
syntax is "File_Gamma=sRGB". ("SRGB" and "srgb" are supported as well.)
Note: When "File_Gamma=sRGB" is used with PNG output file format, POV-Ray
writes an sRGB chunk, thereby claiming that the output conforms to the sRGB
color space; however, this claim is not necessarily true, as POV-Ray is
currently not color space aware; it depends on whether your scene input data
conforms to the sRGB color space.
Note: The other gamma INI file parameters (Antialias_Gamma and DisplayGamma)
do NOT support the "sRGB" value at present.
Changes regarding alpha handling, plus some cleanup:
- Added "premultiplied BOOL" parameter to input image file syntax; like the
"gamma"/"file_gamma" parameter, it must immediately follow the filename
(though the order of "gamma"/"file_gamma" and "premultiplied" does not
matter). The boolean parameter specifies whether the file is stored in
premultiplied ("associated") or non-premultiplied ("straight") alpha format,
overriding the file format specific default. (This keyword has no effect on
files without an alpha channel.)
- Prepared code for adding an INI-file parameter to override file format
specific alpha mode (premultiplied vs. non-premultiplied) for output files.
- Cleaned up the lists of reserved words in reswords.cpp and reswords.h.
Various changes related to PNG files:
- modified png.cpp to be ready for libpng 1.4 (Needs Testing!)
- fixed flaw in PNG input file gamma handling that caused unnecessary loss of
precision
- fixed bug in change #4979 that screwed up image file input under certain
conditions (most particularly PNG files)
Fixed uv mapping for bezier spline lathe.
Minor change to radiosity adaptive pretrace code.
Modified radiosity pretrace mechanism:
- POV-Ray will now create only one set
instead of one set for each pretrace
pertain to the whole pretrace rather
wait for a pretrace step to be fully
of threads for the whole pretrace,

step; likewise, progress report will
than each step; POV-Ray will no longer
completed, and instead assign threads t
o
the next step as soon as all blocks of the previous step are either finished
or already assigned.
- Implemented adaptive pretrace. When a second parameter is specified after
the "nearest_count" keyword, pretrace will stop re-iterating over areas
where, on average, that many (average-quality) samples are already present
per ray.
- Refactored some related code.
Adds "#declare atand = function (x) {degrees(atan(x))} " to "math.inc"
fix for metallic phong highlights which were broken by change #4962
added #elseif statement; the #if, #ifdef and #ifndef directives syntax is
changed as follows:
IF_DIRECTIVE:
#if ( Cond ) TOKENS... [ELSE_DIRECTIVE] #end
IFDEF_DIRECTIVE:
#ifdef ( IDENTIFIER ) TOKENS... [ELSE_DIRECTIVE] #end
IFNDEF_DIRECTIVE:
#ifndef ( IDENTIFIER ) TOKENS... [ELSE_DIRECTIVE] #end
ELSE_DIRECTIVE:
#else TOKENS... |
#elseif ( Cond ) TOKENS... [ELSE_DIRECTIVE]
Example:
#if (Foo)
#debug "Foo is true\n"
#elseif (Bar)
#debug "Foo is false, but Bar is true\n"
#else
#debug "Foo and Bar are both false\n"
#end
fix issue with windows insert menu preview loading of BMP's that contained DPI
information, and expand number of available insert menu ID's to about 9000.
avoid pulling in all of the std and boost namespaces in many places in favor
of some more specific uses. NB requires changes to platform header files,
already done for unix version, the mac port can clone the changes from the
windows syspovconfig.h.
Added "emission" parameter to the finish block; syntax and effect are
virtually identicall to "ambient", except that "emission" is unaffected by
the global "ambient_light" parameter, which will now effectively be set to 0
if radiosity is active (except in legacy scenes having #version set to <
3.70). The intention is to simplify the use of materials designed for
non-radiosity scenes in scenes with radiosity, or the design of scenes that
can be rendered with or without radiosity.
round out core shellout support for the time being.
TODO: add support to simplefrontend.h.
add special handling for INI lines that are shell-out commands.
eliminate dependancy on colors.inc in distro file.
re-implement support for shellouts (WIP, INCOMPLETE).
windows editor tab/indent settings are no longer per-file+global default;
changes affect all opened files.
add display of filename on tab hover in windows editor, and add right-click
menu to tabs allowing opening of folder in explorer and copy of filename to
clipboard.
windows: increase maximum number of insert menu sections to 8192, and ensure
that if no INI file exists, a default one that includes the insert menu for
output is made.
add support for loading of JPG and PNG files as windows insert menu hints.
removed outdated information and corrected typos from some distro files.
changed input file gamma syntax for individual files; as an alternative to
the "file_gamma" keyword, the parser will now also accept the "gamma" keyword
originally introduced for specifying gamma in color values. (To specify the
default input file gamma in the global_settings section, "file_gamma" is
still mandatory though, as "gamma" would be ambiguous and misleading.)
fix FS#116 "assertion fails when using 'filter all' with small-palette images"
Changed antialiasing to compare gamma-adjusted colours instead of linear
colours, to improve antialiasing of darker regions.
Note that this gamma-adjustment is only applied to copies of the sample
values, and does not affect averaging of the sample values, which is still
performed on the original linear data. It is also independent of both preview
display and output file gamma.
The antialiasing gamma-adjustment is controlled by the new ini-file /
command-line options "Antialias_Gamma=x" and "+AGx" respectively, defaulting
to 2.5. Note that this differs from Display_Gamma and File_Gamma defaults, as
it is intended to fit human vision rather than typical CRT characteristics.
Nevertheless, the value specified is once again the inverse of the gamma
actually applied, in order to use the more familiar value range.
fix FS#114 "Mosaic Preview not displaying properly" for unix systems.
Fixed a bug introduced with change #4979 that caused semi-transparent objects
visible against a default background to be displayed wrong in the preview
window when alpha output was off. (File output was unaffected though.)
Added "gamma" keyword to specify gamma pre-corrected colours.
The colour syntax is extended as follows:
COLOR_BODY:
COLOR_VECTOR [GAMMA] |
COLOR_KEYWORD_GROUP |
COLOR_IDENTIFIER [GAMMA]
...
COLOR_KEYWORD_ITEM:
COLOR_IDENTIFIER
|
red Red_Amount
|
blue Blue_Amount
|
green Green_Amount
|
filter Filter_Amount |
transmit Transmit_Amount |
GAMMA
GAMMA:
gamma Gamma_Value |
gamma srgb
Specifying "gamma Gamma_Value" indicates that the colour components are
gamma-precorrected for a display gamma of Gamma_Value, instructing POV-Ray to
automatically convert the colour components to linear values using the
following formula:
Effective_Red_Amount
Effective_Green_Amount
Effective_Blue_Amount
Effective_Filter_Amount
Effective_Transmit_Amount
=
=
=
=
=
pow ( Red_Amount, Gamma_Value )

pow ( Green_Amount, Gamma_Value )
pow ( Blue_Amount, Gamma_Value )
Filter_Amount
Transmit_Amount
Likewise, specifying "gamma srgb" indicates that the colour components are
gamma-precorrected using the sRGB transfer function (being roughly, but not
quite, equivalent to a Gamma_Value of 2.2).
Note that gamma is NOT an additional component, but rather modifies the
interpretation of the other colour keywords. For instance, the following
statements are all fully equivalent:
#declare Foo = colour rgbt <0.2, 0.3, 0.4, 0.5> gamma 2;
#declare Foo = colour rgbt <0.04,0.09,0.16,0.50>;
#local Fnord = colour rgbt <0.2, 0.3, 0.4, 0.5>; #declare Foo = colour Fnord
gamma 2;
Also note that specifying gamma does not affect the filter or transmit compone
nts.
more changes to input image transparency handling:
- For material_map, /no/ alpha premultiplication handling is done whatsoever;
instead, the data as stored in the file is used.
- For bump_map and image_pattern, images with alpha channel are treated as if
they had a black background (unless the alpha channel itself is used).
fix FS#113 "Multi-layered reflections broken"
Added comments & fixed a few flaws in the GammaCurve class
Changed alpha handling for image file in- and output:
* Previous versions of POV-Ray always expected straight (non-premultiplied)

alpha for file input, while always writing associated (premultiplied) alpha
for output; this has been changed on a per-file-format basis to use the same
alpha handling mode for in- and output alike:
- PNG will use straight alpha as per specification;
- OpenEXR and TIFF will use associated alpha as per specifications;
- TGA and BMP 32-bit RGBA (an inofficial extension to BMP) will use
straight alpha, retaining file input compatibility for now, until a final
decision has been made on these formats.
* When generating non-premultiplied alpha output to a classic
low-dynamic-range file format (e.g. PNG), transparency of particularly brigh
t
areas will now be reduced, in order to better preserve highlights on
transparent objects. (Note that this mechanism has some limitations with
colored highlights.)
* When used with file formats for which alpha output is currently not
supported by POV-Ray (or only via an inofficial extension, as with BMP),
turning on alpha output via Output_Alpha=on or +UA will now generate a
warning.
* Fixed various bugs in image.cpp found during code inspection.
fix FS#111 "Remove_Bounds=off / -UR does not work properly"
Fixed FS#112 "OpenEXR alpha is only written when it shouldn't be"
Changes to sky_sphere handling:
- Using filter in a sky_sphere with layered pigments now has the same effect
as in a large sphere with a multi-layered texture. (For compatibility with
legacy scenes, specifying a #version < 3.70 will revert to the old, poorly
specified behavior.)
- Using Output_Alpha=on with legacy scenes (#version < 3.70) will now
suppress sky spheres and background except in reflections, for backward
compatibility with v3.6.
Parser now checks for plausible relation between radiosity minimum_reuse and m
aximum_reuse:
- If ony one value is specified, parser will warn if minimum_reuse > maximum_r
euse/2,
and adjust the unspecified value accordingly.
- If both values are specified, parser will warn if minimum_reuse > maximum_re
use/2,
but not modify any of the values; if minimum_reuse >= maximum_reuse; the par
ser will
raise an error.
Replaced virtually all occurrences of Colour type with RGBColour, using
separate filter and/or transmit variables/parameters where needed, to get a
clearer picture of where these values are actually used and processed, and
where they were just plain ballast.
Consolidated a few duplicate constants.
Changed effect of filter in a layered-pigment sky_sphere to match the
behavior of a corresponding layered-texture large regular sphere. (The old
behavior, though probably having been unintentional, is automatically
re-activated for backward compatibility when #version < 3.7 is specified.)
Partial fix for broken alpha channel output; v3.6 behavior is now reproduced
exactly (including bugs), regardless of version. Further changes will address
the premultiplied-alpha issue (which was already handled wrong in 3.6) and
possibly add options for use cases where v3.6 behavior might be undesired.
Fix crash reported in http://news.povray.org/4bd949b3@news.povray.org
beta 37a install scripts.
change version to beta 37a.
fixed an issue with SSLT that could cause rendering threads to hang
fix for FS#107 "Failed to parse INI file, over network"
follow-up to change #4962 to suppress excessive parse warnings about ignored
filter & transmit components
Yet more code refactoring:
- replaced lots of COLOUR parameters & variables with Colour or RGBColour
- replaced various Colour parameters & variables with RGBColour
- replaced a few int parameters & variables with bool
- declared several more parameters as const
- removed a few obsolete parameters and pieces of code

- refactored image interpolation for better performance and (hopefully) ease
of understanding
- eliminated references to "ray.h" include file (except in ray.cpp)
*PLUS*:
- Implemented bicubic image interpolation as interpolation type 3
various output file type-related changes:
- When specifying an input image in SDL without a file type (neither via type
keyword nor via extension), parser would not fall back to system default
(broken since change #4932); fixed.
- When specifying an IFF input image in SDL, POV-Ray would instead attempt to
read it as a TIFF file; should be fixed (not that anybody would probably car
e
these days...).
- Some code pertaining to histogram output was not updated with change #4932;
fixed. (no symptoms there, as histogram output is presently out of order
anyway)
- Some code pertaining to logging of output settings was not updated with
change #4932; fixed. (no symptoms there either, as logging of output setting
s
is presently out of order as well)
- Validity check for Grayscale_Output setting was broken with change #4932; fi
xed.
- Changed default output file format for Windows version to PNG (note that
"sys" format still remains mapped to BMP)
- Unix config was not updated properly with changes #4932 and #4948; fixed.
- Some minor code refactoring pertaining to the #4932 changes.
fix for FS#104 "Output file gamma broken for File_Gamma=1.0"
disabled chroma sub-sampling in JPEG output; reduced default quality setting
from 95% to 85% to retain same overall quality & file size.
fix FS#103 "JPEG output does not conform to baseline JFIF standard"
Changed a wagonload of function parameters to const, plus some other minor
code refactoring
update install scripts for beta 37.
Update changes.txt/revision.txt.
bump version to beta 37.
fix issue where parse fails if output file type not specified (see change #493
2).
preliminary workaround for FS#81 "sphere_sweep generating artifacts"
partial fix for FS#102 "#switch directive parsing problem": POV-Ray will now
complain if the first #case or #range after a #switch is missing the hash
sign ("#")
fix for FS#92 "Sphere_Sweep Bug": Modified quadratic polynom solver to
"normalize" polynoms first before checking for optimizations, to prevent
problems when all coefficients are small
fixed FS#100 "cutaway_textures"; removed some obsolete code along the way
modified #break semantics; the #break directive can now be used...:
- anywhere within a #case or #range block, to skip to the end of the
#switch directive (previously, #break was only useful right before the nex
t
#case, #range or #else directive, to indicate that a slip-through was not
desired);
- anywhere within a loop block (both #while and #for), to preliminarily
terminate the loop; and
- anywhere within a #macro block, to preliminarily terminate the macro.
Example for the use in a loop:
#local R = seed(4711);
#for (I, 1, 100)

#if (rand(R) < I/1000)
#break // terminate loop early
#end
#debug concat(str(I,0,0), " iterations and counting\n")
#end
Where multiple #switch, loop and/or #macro blocks are nested, #break will
leave only the innermost of these.
implement FS#84 "A for-loop construct":
#for (Identifier, Start, End [, Step])
//...
#end
is now available for simple loops incrementing Identifier from Start to End
(inclusive) with the given Step size (default: +1.0). Basically, it works the
same as the classic #while pattern:
#local Identifier = Start;
#while (Identifier <= End)
//...
#local Identifier = Identifier + Step;
#end
Some additional notes:
- If Step is negative, comparison will be automatically adjusted to match a
"countdown" pattern.
- Start, End and Step are evaluated only *once*.
- The loop counter is a full-fledged local variable. Any local variable of
the same name already defined before the loop *will* be overwritten withou
t
warning (note that in the main scene file, all local variables outside of
macros are effectively global); inside the loop, any tampering with the
variable is possible for effect, as long as it is defined as a local numer
ic
variable at the end of each iteration.
- After the loop has terminated, the variable will remain defined, typically
holding the value End+Step.
- The loop counter must *not* be an array element.
fixed FS#97 "Forward-slash pathnames not fully supported in Windows version",
plus:
- some code refactoring pertaining to path handling
- fixed FS#83 "redundant code in pvengine.cpp" (removed apparently duplicate
code from pvengine.cpp handler for KEYWORD_LOOKUP_MESSAGE)
some photons changes:

* Partially fixed FS#93 "Photons are unnaturally amplified by pass_through o
bjects"
NOTE: As the error is also present in POV-Ray 3.6, behavior has necessaril
y
changed with this fix; pass_through objects will now affect the color of
photons on their way to their target, according to pigment filter/transmit
,
interior fade, and media (which implies that opaque objects will block
photons even when declared pass_through); it needs to be seen whether this
new behavior will be accepted by the users, or whether some additional
mechanism will have to be implemented to choose between old and new
behavior for compatibility with legacy scenes. At present, behavior can
only be changed at compile time with the preprocessor defines PT_FILTER_BE
FORE_TARGET
and PT_AMPLIFY_BUG in photons.cpp.
* Fixed FS#95 "Photons are over-attenuated by semi-transparent surfaces"
* Some minor code refactoring & comment changes in photons-related code
fix FS#94 "Unexpected refraction angle in interfaces with changing IOR <> 1.0"
Cosmetic Code & Comment Changes
Radiosity code changed:
- When a new sample has been gathered after sample lookup returned
insufficient samples, sample lookup is no longer run again; instead, the n
ew
sample is interpolated with the results of the earlier lookup.
- The actual number of samples required to satisfy the reuse_count setting i
s
now influenced by sample quality, with high-quality samples reducing the
effective number of samples required (down to 1/4 of the parameter value i
n
extreme cases) and low-quality samples increasing the number. Note that th
is
may change the balance between speed and quality for some scenes.
- Fixed some bugs & flawed comments found during code inspection.
- Implemented AOI pattern (thanks to Grimbert Jerome for most of the code);
the syntax is as follows:
pigment { aoi pigment_map { ... } }
normal { aoi normal_map { ... } }
texture { aoi texture_map { ... } }

The pattern gives a value proportional to the angle between the ray and the
surface; for consistency with the slope pattern, values range from 0.5 where
ray is tangent to the suftace, to 1.0 where perpendicular; in practice,
values below 0.5 may occur in conjunction with smooth triangles or meshes.
(Note that this differs from the current MegaPOV implementation, where the v
alues
range from 0.5 down to 0.0 instead.)
- Extended slope pattern to specify a reference point instead of a direction;
the new syntax is as follows:
slope { point_at <ReferencePoint> [, Lo_Slope, Hi_Slope] }
(Note that this variant currently does *not* allow for the "altitude" keywor
d to be used.)
The functionality is similar to MegaPOV's "aoi <ReferencePoint>" pattern,
except that the values are reversed, i.e. range from 0.0 for surfaces
facing away from the point in question, to 1.0 for surfaces facing towards
that point; thus, "slope { <Vector> }" and "slope { point_at
<Vector>*VeryLargeNumber }" have virtually the same effect.
- Fixed FS#90 "POV-Ray accepts additional patterns after "slope""
- Various purely cosmetic code changes (comments and formatting) to photons.cp
p
fix for FS#78 "Wrong rendering of BeamTest-Scene in 3.7.beta.35a"
fix for FS#67 "alpha channel in image map is ignored for shadows"
Various changes to image file output:
Code refactoring:
- Image file output now uses the GammaCurve mechanism already in use for
image file input, to allow for arbitrary transfer functions (e.g. as used by
sRGB) in the future.
- Output/histogram file type is now identified by the command line / INI
options parser, removing some uglies from the code and allowing for easier
maintenance of file type letters.
Fixes:
- Fixed FS#88 "File output code does not properly handle negative color valu
es"
- Fixed FS#89 "PPM output garbled for bit depths other than 8 bits"
- Fixed a benign coding flaw in HDR image input code (wrong parameter type i
n function prototype)
- Fixed file type names in some error messages
Changes:
- Radiance HDR image output no longer writes the proprietary GAMMA header
field.
- PPM image output now supports 16-bit greyscale output (effectively
writing a PGM file instead), to be activated via the "Greyscale_Output=on"
option or the "+FPg" file type switch.
Add manual update check menu item for Windows UI.
Change 4929 on 2010/03/14 by calimet@lavender
Unix beta.35a config: require boost >= 1.37 and (for now) libpng < 1.4
update for beta 36, add hard expiry and remove standard timeout from windows v
ersion.
activate update checks in windows version.
Minor radiosity changes:
- maximum_reuse parameter now governs the maximum effective radius of a
sample more directly.
- Removed obsolete code.
- Trimmed down radiosity sample memory footprint a bit.
- Improved robustness of code
- Improved pretrace "pixel" coordinates computation
- Eliminated some "magic numbers"
Fix to changes.txt/revision.txt.
Update about.bmp for windows source dist.
Update windows source dist.
Fix cone axis bug

Fix crash caused by PossibleError function being called with invalid first par
ameter.
Change version to beta 35a.
------------------------------------------Changes between 3.7.beta.34 and 3.7.beta.35
------------------------------------------Change 4906 on 2009/12/31 by chrisc@x8
Fix FS#73 (Blend map cannot get 256 entries).
Thanks to J\E9r\F4me Grimbert for the proposed fix.
Fix FS#59 (Cone intersection test broken)
Implement suggested fix from J\E9r\F4me Grimbert.
NB this fix should be back-ported to 3.6.
Fix FS#51 (POV-Ray crashes hard on missing parenthesis).
The cause of this bug was a pointer to the include file input stream being
retained in the token structure after the stream was closed. The fix involves
comparing the token filehandle pointer to the input file pointer when it is
about to be closed, and setting it to NULL if this is the case. Additionally,
if the include file stack is popped, the token filehandle is set to the
handle of the enclosing file. This will result in any parse errors that occur
for the current token being reported as being in the enclosing file (assuming
that an error occurs before a new token is started). Typically this will be
just after the include or macro statement that opened the file.
Set expiry to March 1 2010, bump version to beta 35.
change hard-coded timeout to 2011.
Proper fix for FS#32 "tiff file extention error" and other changes to file
extension handling:
When trying to load a file of a certain type, the unchanged filename is now
tried first IF it ends in one of the default extensions for the type;
otherwise it is tested only after trying to append one of the defailt
extensions.
When trying to infer a file type from the file name, all of the default
extensions are now compared against, instead of just the first (so that e.g.
"foo.jpeg" will now be identified as a jpep file name).
Some additional code refactoring regarding file extension handling.

Updated list of contributors (console only; bitmaps need to be updated accordi
ngly)
a few trivial changes
Fix FS#53 "Blob trace level":
Trace level increment is now performed on rays being reflected or refracted
at a surface, rather than on rays hitting a potentially refracting or
reflecting object, to do away with the need to figure out beforehand which
objects should increment the trace level and which shouldn't.
Note that slight discrepancies with previous versions may occur regarding
maximum trace level statistics; e.g. a scene without any reflective or
refractive surfaces will report a maximum trace level of 1 instead of 0.
Trace level for radiosity secondary rays will now be incremented according to
the same rules, instead of being incremented for every object surface they
encounter.
Note that this change does not pertain to photons, the trace level of which
is still incremented at every object surface they encounter, including purely
transparent, non-refracting surfaces.
Minor fix for change #4890: Gamma correction was not always forced on when
global file_gamma was used after assumed_gamma.
Dispersion changes:
- fixed FS#61 ("Dispersion does not give proper results")
- improved results with low dispersion sample count
- refactored code for future improvements
Change 4892 on 2009/10/01 by chrisc@cc-luggable
GUIEXT updates from Hugo Arnaut.
Improve input image file gamma handling.
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.
FS#10 "Add support for specifying input images' gamma pre-correction":
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.
* Various bug fixes and minor improvements in input file reading code.
* Added "out-of-the-box" transparency support for GIF files.
* Added support for PNG sRGB chunks.
* 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.
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.
SDL preview display: temporarly disable the window title; see http://bugs.povr
ay.org/23

Update libtiff from version 3.6.1 to 3.8.2.
This fixes FS#57 "Compressed TIFF image_map renders all transparent".
Fix FS#55 "Output_Alpha=on doesn't work as documented"
Subsurface Light Transport improvements:
- Illumination samples for diffuse contribution are now shared among R, G and
B color components; this eliminates color noise, and also appearently reduce
s
RNG-induced patterns. Although this comes at a cost of increasing luminance
noise, the performance increase should allow to fully counter this effect by
increasing the sample count accordingly.
- Fixed some asserts that did not compile on Linux.
Modified ray-object-intersection postcondition handling.
Those postconditions effectively rejected whole objects based on whether the
closest intersection would match the condition, instead of filtering out
individual intersections before determining the closest one. This would lead
to artifacts, e.g. small-scale smoothed mesh objects would fail to
self-shadow near edges where the normal would be almost perpendicular to a
group light source.
Changed this so that compliance with the postcondition is now tested on all
intersections of a particular object when trying to determine the closest
intersection point with that object.
Configure errors on missing NON_REDISTRIBUTABLE_BUILD=yes when required
Improved integration of subsurface code within POV-Ray.
Subsurface light transport code should now properly handle light attenuation
due to distance, spotlight falloff or intervening non-opaque objects
(including media and projected_through objects). Diffuse ambient illumination
is also supported to some extent (multiple-scattering term only) when
radiosity is turned on (however, it does not actually call radiosity code at
present).
Fixed FS#52 "inside() function does not accept meshes despite valid inside_vec
tor"
Some code refactoring.

pov::Trace::RadiosityFunctor and pov::RadiosityFunction:
- Removed some unused method parameters.
pov::Trace:
- Added more comments to the declaration
- Modified method parameters to consistently be const where feasible, and
use reference types in favor of pointers.
- Modified area light code handling to leave the original LightSource data
unchanged; extracted all except the initialization part of
TraceAreaLightShadowRay() into new method TraceAreaLightSubsetShadowRay();
slightly simplified the code
- Renamed some parameters and variables for consistency.
Various:
- Defined a few function/method parameters as const
- Cleaned up some macros
Fixed and re-enabled change #4845 ("moved media handling code..."; see also #4
860).
This may significantly speed up scenes using both "heavyweight" averaged or
pattern-mapped textures (e.g. micronormals) and interior media.
Fix FS#49 "number_of_waves default value not properly initialized"
Some code refactoring and commenting:
pov::Intersection: Added some doxygen-compatible comments; removed some
unused members; moved Intersection::GetLocalIPoint() functionality to
pov::Blob (the only place where it was used).
pov::Blob: moved Intersection::GetLocalIPoint() functionality to here.
pov::RadiosityFunction (and related): Eliminated some members that duplicated
SceneRadiositySettings values; renamed some local variables.
pov::Trace: Added some doxygen-compatible comments; removed an unused
parameter from Trace::ComputeOneWhiteLightRay().
Fix bug FS#48 "CSG bounding box computation broken with shearing transformatio
n"
------------------------------------------Change 4861 on 2009/08/06 by clipka@cli-pc-xp64

Refactoring of Trace class for more consistent use of types:
- replacing DBL with double
- replacing Colour with RGBColour where suitable
- replacing COLOUR / RGB macros with Colour / RGBColour method calls
- replacing colour component math with colour class math where suitable
- replacing array-style colour component access with accessor method calls
- declaring Colour& / RGBColour& parameters as const where appropriate
- replacing VECTOR macros with Vector3d method calls where suitable
- simplifying some unnecessarily complicated code
added sample scene "advanced/diffuse_back.pov" to illustrate diffuse backside
illumination (see changelist #4854)
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 stateme
nt
to control the effect of illumination from the back of the surface. The defaul
t
value is 0.0, i.e. no diffuse backside illumination. For realistic results, th
e
sum of both parameters should be between 0.0 and 1.0, and the 2nd parameter sh
ould
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.
fix FS#40 (FreeBSD lacking POSIX CLOCK_PROCESS_CPUTIME_ID) using the simple wo
rkaround
proposed in http://news.povray.org/4a5f8092@news.povray.org
added option 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 perfor
ms all
computations so it can double-feature as a coarse preview ("vain pretrace"):
Radiosity_Vain_Pretrace=bool
+RVP
-RVP
turns vain pretrace on/off

turns vain pretrace on (default)
turns vain pretrace off
Note that 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 com
putations
(diffuse lighting, higlights and iridescence); other features expendable durin
g pretrace
may follow in future versions.
FS#39 - "cats" and "life" sample scenes broken (follow-up)
NOTE: Only the line ending of the very last line of each file changed (CR to C
R+LF); some
programs may consider this a non-change, so be sure to get the updated version
!
windows console version now sends stream output to stderr by default.
------------------------------------------Change 4828 on 2009/06/17 by calimet@lavender
[unix] config: fix FS#34 (http://bugs.povray.org/task/34) and update generic a
utoconf macros
improve support for image output to stdout/stderr for supported file types. th
e BANNER_STREAM
output will still be a problem if writing the image to stdout as currently thi
s cannot be turned
off. however note that the linux and winconsole versions write these streams t
o STDERR so this
should be OK on those platforms.
NOTE: this submission does not implement progressive output; the image is only
written
after the render completes. progressive output will be added in a later submis
sion.
don't fclose stream if it's stdout, stderr or stdin, plus add support for outp
ut to stderr.
fix FS#14 (coincident transparency issue)
The postcondition in intersection tests had no means of taking SMALL_TOLERANCE

into
account on those occasions it's needed (such as when doing shadow tests). This
is now
implemented.
fix FS#17 (square blotches in transparency).
shadow cache assignment was testing for transparancy against CSG member rather
than CSG itself.
more cleanly handle circumstance where the VFE session closes unexpectedly (e
.g.
due to an exception).
add support for an exception during message dispatch being forwarded all the w
ay to the
front-end code (see #4817) and provide a means to automatically stop a render
when such
an exception occurs. this is a bit hacky in that it's possible to get multiple
instances
of the exception before the render stop takes effect (due to POVMS messages al
ready
queued or that get queued before the request is received).
optimize the way imageProcessing handles creating new images; should reduce th
e chance
of an out-of-memory error.
add support for file-backed RGBFT image container and use it for intermediate
image
storage if allocating a memory-backed one fails. this implementation is basic
in that it
doesn't support large files (anything more than what fseek/fwrite etc can hand
le) and
only buffers a single line. the proper solution to the intermediate image stor
age issue
is to go away from using an image container and cache the render blocks on dis
k instead,
using a class that can stream fully-completed rows to the image output code (r
equired for
writing to stdout to work properly again).
add support for an exception during message dispatch being forwarded all the w
ay to the
front-end code. previously such exceptions were discarded, meaning that if e.g
. an image
write operation failed due to lack of disk space, the front-end wouldn't know
(and the
render would continue).
NOTE: this has changed the semantics of POVMS_ProcessMessages: previously, it

would
never throw an exception or allow one to reach the caller. VFE insulates calle
rs from
this but platforms not using VFE need to be prepared to handle an exception if
one
occurs.
Change 4816 on 2009/06/07 by clipka@cli-pc-xp.rad
Add some more radiosity stats for performance tweaking
fix FS#33 (parse accepting invalid vector float components).
the parser will now throw an error if an additional period ('.') is found in a
floating-point literal.
see http://bugs.povray.org/task/33.
fix bug FS#16
code introduced in change #4452 did not iterate the blend map or materials to
check for reflection.
this could result in a render with infinitely increasing trace level (until st
ack
overflow) due to maxTraceLevel not being incremented.
See http://bugs.povray.org/task/16.
preliminary fix for FS#32 (tiff file extention error):
Exact specified filename is now always searched for, if only as a last resort
fix bug FS#15 (using trace or inside with a julia fractal causes a crash).
See http://bugs.povray.org/task/15.
fix bug FS#13 (files of exactly 4k cause editor crash in 64-bit windows)
see http://bugs.povray.org/task/13
fix editor crash on 64-bit systems.
[unix] fix "FS#21 - unix scripts have wrong version set"
[unix] config: drop support for --with-boost-src configure option.
The workaround offered by this option has been marked unsafe since the first
POV 3.7 source release (beta.28). Moreover, installing Boost from sources
got much easier since at least version 1.35.
Note: with this change, the libraries/ folder is no longer distributed.

[unix] get rid of --disable-vsnprintf-check and unimplemented SVGA support (-with-svga); misc tweaks
Fix "FS#31 - function pattern in image map" (transmit component was inverted i
n pigment function images)
Fixed "FS#24 - isosurface, bounding box & threads"; added some debug assertion
s to make
sure similar issues with IStack pop up early in future
Fix ARRAYS_WriteDF3 macro:
- Fix 16-bit depth output
- Fix a parse warning
[unix] config: Boost >= 1.36 required
[unix] config: generic updates from GNU automake 1.11
add no_radiosity keyword, as known from MegaPOV:
Specifying "no_radiosity" in an object block makes that object invisible to ra
diosity
rays, in the same way as "no_image", "no_reflection" and "no_shadow" make an o
bject
invisible to primary, reflected and shadow test rays, respectively.
combine IntStats and FPStats into RenderStats class; this allows for more conv
enient access.
introduce new thread-local storage macro; this is intended to replace use of b
oost's
thread_specifc_ptr such that we can get more direct (i.e. faster) access to th
e data
being referred to. currently this isn't used for anything new (CurrentTaskCoop
erate uses
it as before), but over time more uses will be enabled.
NOTE: there is a default implementation of the TLS macro named DECLARE_THREAD_
LOCAL_PTR in frame.h.
This uses the syntax that GCC expects, and thus should work for unix and mac p
latforms,
however I've not tested it.
remove reference to uninitialized local variable causing radiosity stats to be

displayed when they should not be.
statistics re-work to provide support for floating-point values as well as int
.
also change ThreadData arguments in most places to no longer be const.
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 r
adiosity 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; otherw
ise, +RFO
causes the file to be overwritten if it exists.
New samples gathered are written whenever an SMP block is completed. Tests ind
icate
that this is almost neutral regarding performance, compared to operation with
radiosity
file output disabled.
--------------------Accompanying changes:
- moved most of the radiosity parameters out of povrayold.h; overhauled hand
ling of
per-recursion settings
- each thread now has its own sample cache block allocation pool, reducing t
hread
synchronization overhead; according to tests, this gives a slight performa
nce benefit.
--------------------Unrelated changes:
- changed structure of the code computing sample ray directions, as initial
preparations
for future "smart" sampling algorithms
- now using different "waveforms" to average nearby samples, using a more sm
oothly blurring
function for top-level samples during final render, while using a faster f
unction for
deep-recursion samples and/or pretrace
- slightly tweaked individual per-recursion parameters

fixed duplicate color names in glass.inc
Various Radiosity improvements:
- further cleaned up code; improved performance for "bounce depth" >= 2 agai
n
- new "high reproducibility" mode: when specifying "High_Reproducibility" or
"+HR" on the
command line, POV-Ray will spend extra effort to make sure renders are det
erministic despite
SMP (currently, radiosity is the only code to use this flag; in HR mode, r
adiosity pretrace
starts out with fewer threads, and some extra rules are imposed on sample
re-use that may cause
surplus samples to be gathered)
------------------------------------------Change 4753 on 2009/03/31 by clipka@cli-pc-xp.rad
added ARRAYS_WriteDF3 macro to arrays.inc for writing an array to a df3 file
fix bug creating artifacts in output file when mosaic preview is used with +EP
2 and -A
Added experimental support for subsurface light transport (aka subsurface scat
tering).
Currently, SSLT is activated for a particular object by adding the following s
tatement to
its finish (note that this is very likely to change):
subsurface { COLOR, COLOR }
specifying the (reduced) scattering coefficients (sigma'[s]) and absorption co
efficients
(sigma[a]), respectively, in units of 1/mm, for each of the three basic colors
. The object's
IOR will also affect the results.
The algorithm is designed to give realistic results at a scale of 10 mm per PO
V-Ray unit by
default; for other scales, place the following statement in the global_setting
s section:
mm_per_unit NUMBER
To tune the algorithm for quality or performance, the number of samples for th
e diffuse
scattering and single-scattering approximation, respectively, can be specified
by placing
the following statement in the global_settings section:
subsurface { samples NUMBER, NUMBER }
SSLT is still in alpha stage.
added radiosity octree performance stats; fixed stats for max trace level & pa
rse time
implement binary #write
alter the return type of GetThreadID() related functions to be POVMS_Sys_Threa
d_Type.
Change POVMS_Sys_Thread_Type to be unsigned long (needed for 64-bit Macintosh
x86 build).
improvements to performance in crackle cache. in particular, avoid calling mal
loc() for
each cached entry, and rely on performance of unordered_map's default allocato
r to not hammer
the heap. NB I tried using boost's pool allocator but this gave particularly p
oor performance
on render shutdown (during destruction of the allocated entries).
optimised the management of the crackle cache size by setting limits in megaby
tes (currently
per-thread and not user-settable: this needs looking at).
NB there is some scope for investigation of whether or not the crackle cache c
ould be efficiently
turned back into a single cache per scene, rather than per thread; cache effic
iency seems fairly
high and thus most accesses are reads.
optimised crackle cache entry setup a little by avoid branches during main loo
p at cost of extra
memory lookups.
changed crackle to use the boost hash.
renamed the standard POV 'Rectangle' class to 'Rect' due to a long-standing an
d rather annoying
clash with a Windows definition of the same same name. unfortunately some boos
t headers (such as
pool allocators, and also the mutex code) pull in windows.h and contaminate th
e namespace with
windows crap. while I could work around it by explicitly specifying pov_base::
Rectangle it's
cleaner just to change the definition to avoid this.
unix config: changes for beta.31
- require boost >= 1.35 to build latest radiosity changes
- add check whether the selected C++ compiler works to fix issue reported in
http://news.povray.org/web.494ffd924e4b35bcedb0f3170%40news.povray.org
- add more robust check to detect boost
- add support for ICC's -xHost flag (version 11.0 and above) and preliminary
support for SSE4
unix config: ax_test_compiler_flags.m4 checks current flag with all previously
selected flags;
does not use AC_TRY_COMMAND anymore
tweak randomsequences.h to make visual studio 2005 happy.
tweak display of render shutdown and file warnings on Windows.
change 'render shutdown' to 'shutdown' in shutdown messagefactory.
fix inconsistent usage of int/long in line numbers within POVMS messages.
implement filename display in message output where name is supplied.
introduce means for objects to submit a message on shutdown. this is
currently only implemented for isosurfaces (the max_gradient warning), but
can be implemented for any object type by providing an implementation of
ObjectBase::DispatchShutdownMessages.
auto-size progress bar to fit in remaining status panel space; if not enough
room, don't show it at all.
fixed bug that caused wrong radiosity illumination on transformed mapped textu
res
config: ax_x86_arch.m4 does not use AC_TRY_COMMAND anymore;
add preliminary support for SSE4x and newer Core i7, Phenom CPUs
config: ax_fix_incorrect_path.m4 does not use AC_TRY_COMMAND anymore
config: rewrite ax_compiler_version.m4 macro for better logging;
do not use autoconf's undocumented/deprecated/dangerous AC_TRY_COMMAND anymore
remove a non-ASCII character (radiosity updates, change 4687)
install script: fix non-POSIX 'read' options as reported in
http://news.povray.org/web.496e790f156c502e2adf27b40@news.povray.org
config: fix issue reported in http://news.povray.org/web.494fe25d9d9e24ec569d0
e9f0@news.povray.org
updates/fix for newer GNU autoconf versions (tested with 2.63)
config: updates from the Autoconf Macro Archive; minor mod for ax_compare_vers
ion.m4
config: generic updates from GNU automake 1.10.2
ported SSLT code by Sarah Tariq and Lawrence (Lorenzo) Ibarria from v3.5
proof-of-concept source files.
code is not active currently. lots more work to do.
Radiosity updates from Christoph Lipka, with some minor re-formatting and
updates to suit changes in the boost::thread library.
various minor changes mostly related to building the code with boost v1.37.0
add Visual Studio 2008 project.
fix install issue where SSE2 binary was always used even if system didn't
have SSE2.
update windows readme.txt, add HTML version (readme.txt is now derived from
the HTML one).
fix bashism is various scripts; see http://news.povray.org/48c1d1b9$1@news.pov
ray.org
fix bashism is various scripts; see http://news.povray.org/48c1d1b9$1@news.pov
ray.org
allow 'save as' to succeed without 'file is already open in editor' error if
case of current file is being changed.
add CPU count code from Intel Corp.
this allows us (at least on Intel CPU's) to get a more accurate count of
actual CPU cores installed. this is particularly useful for fixing the
issue with the stats (Windows counts virtual processors as physical ones,
which mucks up the CPU vs elapsed time ratio calculation).
update teapot sample scene.
change flat_enough to 0.0001 (was 0.01).
change teapot texture, checker color, and background color.
fix error on line 179 where incorrect y-coordinate was given (reported by
Yannick Patois).
add colored text output to message window. warning and debug messages get
different colors than error messages and standard text.
change default background to be a plain color.
add deprecation to glass_old.inc and related changes (from Jim Holsenback).
add ability to declare an identifier as deprecated.
#declare deprecated Col_Glass_Old=color rgbf <0.8, 0.9, 0.85, 0.85>;
#declare deprecated once Col_Glass_Old=color rgbf <0.8, 0.9, 0.85, 0.85>;
#declare deprecated "Some message" Col_Glass_Old=color rgbf <0.8, 0.9, 0.85,
0.85>;
A deprecated identifier generates no message at the time it is declared: a
warning is only issued if it is used.
If the optional 'once' keyword is present it must immediately follow the

'deprecated' keyword and indicates that the warning should only be displayed
once per parse.
If the optional message string is present, it will be used as the warning to
be displayed if the identifier is used. Otherwise, a message of the form
"Identifier 'FOO' was declared deprecated." is used.
An identifier is considered 'used' if it is referenced anywhere (even if in
another #declare).
add some extra libraries to the link for installations that don't already
imply them.
updated objects and portfolio files from Sabrina Kilian.
See <48876483@news.povray.org> for details.
work around crackle hash issue reported by Yvo by reverting to old hash functi
on.
Issue: new hash function returns large range of possible values, causing
memory used by cache to grow quickly.
move assumed location of user-editable files into a subdir of 'My Documents'.
update sample INI files to read 3.7.
scenes and include updates from Jim Holsenback and Stephen Shonfield.
See <48876483@news.povray.org> for details.
bump version to beta 29, expiry to 1 November 2008.
a few tweaks to the project files; in particular, allow boost path to be
specified via $(BOOST_ROOT).
fixes two crashes reported in thread <web.48b1839e38b6f50ec03ef3130@news.povra
y.org>.
also be a little more conservative with the cache allocations (min 1 entry
even if no lights).
fix sphere_sweep parse crash reported in <web.48bc447cc2ccad1e8510f03f0@news.p

ovray.org>.
change Ascii to USC2 function such that ASCII codes > 127 are not sign-extende
d.
change UCS2 to Ascii function such such that UCS2 codes between 128 and 255 ar
e
now accepted.
change media confidence test to accept 0.0 as per docs.
thanks to Yvo for picking this lurking error up (could cause crashes in JPEG c
ode).
include Solaris patch by John Martin as reported in <web.47e9bdccd4b82d06c7064
b8c0%40news.povray.org>.
Update VERSION to beta.28
about box and status panel changes.
set XP icon as default.
add PSD for about box.
change way parse warnings are dispatched internally if not optimized for
console.
fix 'white outlines in df3 patterns with interpolate 2' issue reported in
<483d2920@news.povray.org>.
NB fix solves problem by clamping the return value to no less than 0. a more
correct approach might be to work out why the (very small) negative values
were being generated in the first place.
fix 'clock not working in functions' issue reported in
<486c3c98$1@news.povray.org>.
make sure windows exception handler body only gets executed once no matter
how many threads are running.
fix str() crash reported in <web.4880f0adaf19f856c59235590@news.povray.org>.

fix bounding box calculation flaw that caused in some cases major slow-downs
in scenes using difference (e.g. abyss.pov).
re-implement light color cache for textures. without this, each subsequent
layer (after the first) in a multi-layered texture will cause an unnecessary
call to TraceShadowRay and its subsequent intersection test to determine the
light color at that point.
NOTE 1: the original 3.6 code did not re-initialise the 'Tested' flag in
ComputeShadowColour; I presume this is to re-use the cache at that level ...
need to check if this is the case. the current code does the same.
NOTE 2: there's more work to do on this. it's just a first step; there are
other places where caching is needed.
work around boost::regex-related problem.
bugfix for INI directory exclusion in IO permissions.
more work on splitting program data/user data.
revert to using INI file for pvengine options.
improve 3.6 migration code.
fix issue whereby manual bounds, clips, patterns, UV, and interior were left
behind when a transformation was applied to a CSG object.
add handling of std::bad_alloc() to parser, rather than letting it fall
through to task. this allows the file and line number that was being parsed
at the time to be displayed. also, the bad_alloc handler in task attempts to
raise a POV_EXCEPTION, which could fail due to insufficient memory for the
exception object; this is no longer attempted.
alter pvmem.cpp to throw std::bad_alloc() upon memory allocation failure.
add support for specifying grayscale output via INI file or command-line.
this is intended to replace the use of hf_gray_16 in global_settings.
hf_gray_16, if encountered, has no effect on the output type and will
additionally generate a warning message (as before).

currently only PNG file support is provided with grayscale output; others
will be added over time.
grayscale output may be specified via 'Grayscale_Output=true' as an INI
option, or '+Fxg' (for output type 'x') as a command-line option. For
example, '+Fng' for PNG grayscale output.
caveat: grayscale output implies the maximum bit-depth the format supports;
for PNG this is 16. it is not valid to specify bits per color channel with
'g' (e.g. '+Fng16' is not allowed, and nor for that matter is '+Fn16g'). if
bits per channel is provided via an INI option, it is ignored.
fix crash with inverse and CSG reported in <web.4828b51b6d261ebff3e4f6a20@news
.povray.org>.
fix incorrect flag test which would have resulted in issues with cutaway
textures and CSG or objects with double_illuminate set.
Fix for "no_image and transparency" problem reported in <web.46f84a9cd032f3c7c
b86afba0@news.povray.org>.
NB: there might be other circumstances where we need to honor the NO_IMAGE
flag at this point in the code; this fix just added refraction to the test.
Fix the animation frame number issue reported in <478561e3@news.povray.org>;
beware of side-effects (hopefully none).
Re-enable Include_Header thanks to patch from Stefaan De Roeck (see <47fb5d65@
news.povray.org>).
Also fix unrelated bug discovered when testing above: if an attempt to open
an include file threw an exception (e.g. due to file I/O restrictions), POV-Ra
y
would crash if the include stack element had not been previously used.
Fix 'library path accumulation' issue reported in <481da512$1@news.povray.org>
.
apply isosurface cache fix suggested by Lukas Winter in <47c5b8b6$1@news.povra
y.org>.
Workaround for race condition that would cause 'timed out waiting for worker t
hread' error.
[unix] fix the --prefix ignored issue reported by Warp
http://news.povray.org/47f28cfe@news.povray.org
dd two missing includes; after reports by Sean McGrath on
http://news.povray.org/web.47e7abdfb582dec03803aa600@news.povray.org
http://blogs.sun.com/smg/entry/povray_3_7_on_solaris
apply gentoo patch for build failure with gcc 4.3
http://bugs.gentoo.org/show_bug.cgi?id=216684
a raft of changes, mostly related to our default class name, registry location
, and migration.
as of this checkin, POVWIN now uses its own registry branch instead of sharing
the one used by 3.6.
support has been added for automatically migrating INI-based settings from a p
rior 3.6 install.
other misc changes also included.
fix file drop crash reported in <47ac0f69$1@news.povray.org>.
stub out windows video capture support code (needs re-implementation).
remove last vestiges of pvengine.ini support (with exception for compatibility
in GUIEXT).
NB this doesn't affect pov-ray's own INI file handling.
Move pvtools.ini to logged-in user's Application Data\POV-Ray for Windows dire
ctory.
As of this checkin, version 5 of the common control DLL is required. This was
supplied with IE5, so it's highly unlikely that it won't be present on any
version of windows that we still support.
add auto setting of thread count and rework --benchmark for linux platform.
The number of threads is now set as the number of detected CPUs, or
4 otherwise. The built-in benchmark now accepts +Lpath command-line

options and does no longer read any INI file but the provided one.
moves all settings that used to be in pvengine.ini into the registry.
Change 4519 on 2008/01/19 by warp@warp
fixed double-illumination problem with the area_illumination feature.
irid, ground fog, and constant fog were using noise generator 0 rather than
the default generator.
Change 4513 on 2008/01/01 by calimet@nx
build system: fix problems in detecting Athlon64 X2 cpus and OpenEXR < 1.4.
Thanks to Jaime for the reports.
add fix for the 'area lights and transform' bug reported in
<web.4639ad4565c782bbc717c9af0@news.povray.org>.
changes to parser error message handling intended to reduce the incidence of
duplicate messages.
------------------------------------------Change 4494 on 2007/11/27 by nkopp@lightspeed
Update photon code to take advantage of multiple threads.
Fixed superellipsoid bug reported in <6p8nj3tckhrd1pihpofmvltqrfrs4lish8@4ax.c
om>
Added a new warp: cubic. It maps an area in the x-y plane between <0,0>
and <1,1> in the same way as box uv-mapping does.
A new pattern type: 'cubic'. It takes six texture elements and maps each
one to each pyramid centered at each half-axis (thus effectively mapping
each texture element to each side of a origin-centered cube).
Added support for reading the pixel resolution of an image map. This is done
by giving an image map pigment identifier to max_extent(), which will then
return the resolution of the image map as the x and y value of the returned ve
ctor.
Added support for full area light diffuse and specular illumination. By defaul
t
this is off, but can be turned on with the new keyword 'area_illumination [on|
off]'
inside the light_source definition block.
POVWIN now allows an expired beta to be extended by up to one week at a time,
up to a maximum of 12 months.
Change 4457 on 2007/09/15 by nkopp@lightspeed
Fix photon issues with refraction and dispersion
Comparison ('=', '!=', '<', '<=', '>', '>=') support for strings.
-------------------------------------------Changes between 3.7.beta.20b and 3.7.beta.22
-------------------------------------------Change 4452 on 2007/08/28 by warp@warp
The trace level in the trace() function is now incremented only if
an object was hit and the object is marked to increment the trace
level, or if the ray was a radiosity ray. Objects which do not use
reflection nor ior (but which might be semi-transparent) are marked
as not incrementing the trace level.
Change 4447 on 2007/08/09 by chrisc@cc-vm-xp
Workaround for the temp file mapping not being completed.
Temp files are now created as before (in the place specified).
Change 4445 on 2007/08/09 by chrisc@cc-vm-xp
Fix issue whereby an I/O restrictions error would be displayed rather than
'input file not found' in certain cases where POVWIN was asked to render a
source file that was not present.
Multi-threaded signal handler, replaces the basic implementation.
The signal handler is now running its own thread waiting to receive signals
via sigwait(). Cancelling the benchmark before it starts is now handled via
the handler as well, and returns proper exit value.
Further fix for media_attenuation bug
(fix new bug that was introduced in changelist 4394)

Fix SDL crash reported in <4617c41e$1@news.povray.org>.
Add Control-A support in commandline input box (select all).
change render window keypress code to hand focus to main window for any key, n
ot just escape.
Fix fog (and participating media) shadow attenuation issues.
Media computation was ignoring the lightsource's media_attenuation
flag under some circumstances, and was attenuating shadow rays if
the shadow ray had intersected an object.
Fix jpeg temp file issue reported in thread <web.46168c053403448a4f02351a0@new
s.povray.org>.
Fix incorrect exit value when closing the display window (user abort)
Temporarily hard-code INI keywords into editor syntax table for INI files.
-------------------------------------------Changes between 3.7.beta.20 and 3.7.beta.20b
add 'alternate render file' feature to povwin IDE. the purpose of this
feature is to make working on include files and macros more convenient.
if the user requests that a file which is not a '.pov' or '.ini' file,
povwin consults an internal list of include file to source file mappings
which is accumulated for each render (note this is not persistent). if
the file that is to be rendered is in this list, the user is asked if
they would prefer to render the source file that most recently included
it instead. their decision is stored for the remainder of the session.
additionally, add extensions .MCR and .MAC to list of files POV
considers include files (i.e. which are filtered as such in the various
file dialogs and assigned the POV file type for the editor syntax
highlighting).
add .INI file type to editor syntax highlighting. currently does not
recognise POV keywords; this is to be added.
add window menu to IDE. entries are MRU-sorted.
also some other misc changes, including removing links to IRTC CD etc.
Activate new memory statistics code; update win mem stats code to suit.
NOTE: This is a work in progress. Currently it only gives global memory
stats (not per-thread). Per-thread stats are planned and are more useful
than global stats since we can then determine the memory usage of e.g.
the parse stage vs the render stage, plus ignore any allocs from non-core
related threads (e.g. the UI).
NB this feature requires non-trivial platform-specific code to function.
I'd advise holding off doing other platform support until the windows
code is done, as the interface will probably change.
fix problems in running the internal benchmark (setting the number of
threads; aborting the benchmark before it starts)
better error checking for timers; pretend the CPU time is always right for
now.
configure.ac: always check getrusage() and gettimeofday()
various changes and fixes including:
- the display PauseWhenDone() method now takes a parameter that signals
whether we need to exit immediatly (for instance if ctrl+c is hit)
- set expiry to 2007-04-16
- better handling of render cancel (text display; within animation)
- read session status a bit more often (200ms instead of 250)
- immediatly notify a change in the backend state (set event mask)
to better synchronize the relevant console messages
- exit code now returns 0=ok | 1=error | 2=user abort
fix issue with editor window splitting not being restored
(<45620b9e$1@news.povray.org>).
fix issue with file type not being set on initial save if 'save as' was
not used (reported many times, including <45602a08@news.povray.org> and
<46092c8a@news.povray.org>).
fix uv mapping issue reported in <45602a08@news.povray.org> and
<46092c8a@news.povray.org>.
note that the core issue here could have had effects in other places.
[Copy_Object was not properly initializing/clearing some fields that are
usually, but not always, copied by the object-specific copy function.
in particular it was not clearing llights].

tentative implementation for CPU and wall-clock timers using the POSIX
clock_gettime() function or getrusage() as a fallback; misc changes such
as code cleanup.
Note: On Linux at least, the per-thread CPU time is likely to be wrong,
i.e. equivalent to the process wall-clock time, due to how glibc
implements clock_gettime() with CLOCK_PROCESS_CPUTIME_ID or
CLOCK_THREAD_CPUTIME_ID (see http://sources.redhat.com/ml/libc-alpha/2004-10/m
sg00008.html).
Linux kernels >= 2.6.10 should implement those calls internally; however
I seem to get wrong results when the number of threads exceeds the number
of cores/cpus. Needs further testing and/or workarounds.
reorganize configure.ac to perform library checks before language
constructs and functions checks; add tests for availability of librt and
clock_gettime() for POSIX timers, as well as getrusage() and
nanosleep(); move again the variable expansion for directories after the
call of AC_OUTPUT.
fix PNG gamma issue reported in <45aa976e$1@news.povray.org> and
<45c11eed$1@news.povray.org>. If supported, the gAMA chunk is always
written, thus following the HDR (radiance) output behavior.
Restrict display and file gamma to be at least 0.001
activate interframe pause thanks to change 4345 (closes bugzilla bug #22)
and add basic signal handler
change a number of instances of POV_EXCEPTION_STRING() to be POV_EXCEPTION()
with error code and string.
cease use of longjmp in png error handlers.
note that this change throws exceptions from 'extern C' functions. if you
have told your compiler that this does not happen, be sure to change that
setting for png.cpp.
remove embedded LF in message generated for #error.
add 'file modified' indicator to filename shown in main window caption.

add feature notification for when auto-reload results in files being auto-save
d.
some vfe changes to assist resolution of the 'pause after render' problem.
unix: add support for --benchmark (works together with +wt) and print
built-in features with --version
sanitize a few unix HTML files and port the lastest 3.6 changes
(w3c conformance, folded menu entries, improved keyword index)
sanitize a few generic HTML files
port the latest changes in the 3.6 build system to 3.7
workaround the "1 thread busy after completing" issue reported in
<45dda26c$1@news.povray.org> by replacing a wait event with polling.
------------------------------------------TODO
------------------------------------------TODO
fix vidcap handling of video source pins that are not RGB8 (it now ignores the
m).
disable RTR support on Win64 for now.
make sure pause button state reflects frontend state when pause/resume fails.
include version ID and system time in crash dump filename.
open explorer window with crash dump file selected after a crash dump.

fix issue with sys output file extension on windows (<455a0770@news.povray.org
>).
fix 'Subset_Start_Frame not working' issue (<web.454b67a8defacc9bf2985afc0@new
s.povray.org>).
remove local index vectors from bsp tree build code to avoid slowdowns due to
heap locking. on win32, this roughly doubles build speed for complex trees
(e.g. isocacti.pov).
Some display-related improvements.
Do not close the display window between the frames of an animation.
Use PACKAGE_NAME and VERSION_BASE for the window title.
Fix unwanted pause_when_done if the render is canceled.
Decrease the GetStatus() wait time from 1s to 250ms.
fix for BSP missing objects and speckled rendering (cornell.pov gave a good
example of both).
fix infinite loop in radiosity pre-trace code that would occur with small
values of pretrace end.
add temporary workaround to distribute radiosity pre-tracing amongst all
threads. this needs to be removed once we work out the best way of co-ordinati
ng
the worker threads during pre-trace.
Fix missing definition for FILENAME_SEPARATOR that caused run failure with
absolute filenames (reported by Warp).
enable multi-threaded radiosity. includes some basic locking on radiosity
cache, but see note in source.
radiosity is still a WIP.
fix bug that stopped radiosity from being activated when it should have been.
implement clockless animation support for real-time raytracing.
some more RTR changes. windows capture code now supports options as follows:
width=nnn
height=nnn
double-buffer=yes|true|1|no|false|0
skip-initial=nnn
gamma=fff
if omitted, defaults are:
width and height
double-buffer
skip-initial
gamma
the first found pin in the video capture device graph

on
0 frames (i.e. off)
1.0
it is possible to specify just the width or height, in which case the code
will default to the first found pin with that size, and won't care what the
other dimension is. specifying '-1' as a width or height is also a way of
saying it is a "don't-care". if the requested size is not available, the
render will fail.
skip-initial is the number of frames to skip before returning from the
initialization. this is needed on some webcams that need a number of frames
to perform their setup (such as auto exposure and auto white-balance). this
matters mostly if the vidcap input is being used for something other than
real-time rendering.
double-buffer and gamma do what their name imply.
example specification:
image_map {sys ":vidcap:width=640:height=480:double-buffer=0:skip-initial=5
:gamma=2.2" map_type 1}
add double-buffering to video capture implementation.
some preliminary RTR support. still a WIP.
fix issue caused by failure to clear ray interiors during focal blur sample lo
op.
see <web.45424a798f1b3f6c1bd6cd0c0@news.povray.org>.
implement video capture. still need to add options parsing for setting e.g.
resolution etc.
fix issue with trace returning an incorrect intersection point in some
circumstances (see <web.45367d932f1ac4de72d86b490@news.povray.org>).
The issue was caused by the noise function using a different noise generator
during the parse than afterwards, since f_noise3d passed a NULL pattern to
Noise(), which tells noise to use the default noise generator. However this
is not assigned prior to parse completion.
The fix was to give the VM access to the actual noise generator via
scenedata, so that it may be passed to Noise(). In the process I took the
opportunity to get rid of the global gNoiseGenerator, since its main reason
for existance is to allow Noise() to work when it isn't passed a noise
generator explicitly (via tpat). Noise() - and also a few other functions
that used to take a TPATTERN * - now directly accept the noise generator
instead.
fix material assignment issue (see bugzilla bug #21).
improve handling of debug messages in vfe.
fix crash reported in <web.453677b9876cd74e72d86b490@news.povray.org>.
Change 4261 on 2006/10/17 by thorsten@host27i
Adds stat for camera count as well as variable for sending camera index to
View::StartRender (however, does not implement selecting that camera yet)
change default file gamma from 1.0 to 2.2
Change 4258 on 2006/10/14 by chormann@chho
correcting 'FileGamma' and 'DisplayGamma' to 'File_Gamma' and 'Display_Gamma'
in warning messages
work around an issue caused by apparent resource starvation within windows.
this would show itself as non-updating editor windows when switching tabs or
focus - usually when running several instances of POVWIN - and is caused by
CreateCompatibleBitmap() failing. substituting calls to CreateDIBSection()
fixes the problem. NB I not been able to replicate the error on systems that
do not have windowblinds installed, though I cannot say definitively if that
is the cause.
add support for 'pause when done' (closes bugzilla bug 5)
set background color in parser

changes alpha handling for rays not going straight to the background
fixes 'Initial_Frame is ignored' issue (bugzilla bug #20).
improvements/fixes for the install script:
- fixing problem with the install log (uninstall now works after user instal
l)
-
added warning about existing povray executables.

some changes in the text messages.
changed a few -f tests to -r
preparation for different target platforms
(TARGET_PLATFORM and TARGET_PLATFORM_NAME - AMD64 version commented out)

improve temp file handling under windows vfe platform implementation.
code now uses its own subdir under the windows temp dir, and also keeps
track of temp filenames handed out so as to delete them on exit in case
the core code doesn't do so. also now automatically permits read/writes
in the temp dir when I/O restrictions are turned on.
change WorkThreads INI option to Work_Threads for consistency.
change bounding method command-line option from +b2 to +bm2 for the same reaso
n.
fix major (e.g. 100x or more when rendering menger.pov) slowdown when using
BSP bounding, an orthographic camera (or any camera with non-constant origin),
and large numbers of slow objects. this was due to InitRayContainerState() not
having BSP support written for it yet.
also added BSP support to CheckCameraHollowObject().
add ability to close edit tab by middle-clicking on it.
Improve parsing of POVWIN-specific command-line filenames containing single
quotes.
Add /EDITDLLPATH command-line parameter which allows the user to override the
default DLL locations.
Changed edit DLL filenames to include 'd' for debug builds; e.g. cmedit32.dll
becomes cmedit32d.dll.
NOTE: the above change means that if you are debugging POVWIN and haven't
built and installed the debug DLL's, the editor won't load. Either build and
install the debug editor DLL's (codemax and cmedit projects), or copy
cmedit32.dll and povcmax32.dll to cmedit32d.dll and povcmax32d.dll
respectively, and place them into the default POVWIN install bin dir.
Ditto for the 64-bit ones if you're using Win64.
add SEH and minidump generation to windows code.

some code for experimental vidcap support.
add 'beta_feature_flag' which works like 'experimental_flag' but also warns
feature may go away entirely.
the vidcap code is an outgrowth of a real-time-raytracing experiment done
for IDF fall 2006, where a live image from a webcam was mapped onto a moving
curved reflective surface in real-time. the original code was a quick hack;
this is an attempt to provide it in a more usable framework that doesn't
break standard use of POV as I think it's worth further experimentation.
currently this feature only works with image maps but there's no reason why
it can't work with other things that use images. the implementation returns
a pov::Image which is updated either continuously or when a UpdateImage()
request is made. no double-buffering is used in the windows implementation
yet.
to implement this on other platforms, define the macro POV_VIDCAP_IMPL in
your syspovconfig.h file. the value of this macro should be the name of a
class which has a default constructor. it should also implement the methods
Init(), UpdateImage(), and WaitFrame(). see syspovimage.h in this submission
for an example, as well as the other files in the windows rtrsupport
directory.
fix for error line/col reporting.
change default number of threads to number of CPU's (was number of CPU's * 2).
add ability to specify thread count from render menu. NB this value is not sav
ed.
tweak process priority for normal priority selection.
fix for bugzilla bug #15 ('non-terminating unix POV-Ray').
Fix problem with photons in grenadine.pov
It turns out that somehow when rendered with +b2 (BSP tree partitioning),
we end up with LOTS of photons in the exact same spot (locaton
-0.865566,1.846830,-0.464796). The code finds the average density of
the scene by sampling points, and whenever it would sample that point,
it would compute a density of infinity (because it would reach the maximum
number of photons, and return a zero-radius surface area for those
photons).
The current fix is to make the system ignore samples that give zero-radius
(infinite density) results.
The "real" fix will be to figure out why we end up with over 100 photons
in one spot when rendering with BSP, but not when rendering with the old
block partitioning.
changed density file fix (change 4195) to use 'size_t' instead of 'long'.
Fix nasty heap overwrite in BVH code. See <web.44e5a00bfcc26e0fc717c9af0@news.
povray.org>.
This bug caused delayed crashes and would not show up in debug mode.
It's been in the codebase since at least version 3.5, if not earlier.
fixed the density file size limitation by changing 'int' to 'long' for
various index variables in DF3 reading, pattern evaluation and data structure.
See <web.44f40e4698b0d9e4b399450c0@news.povray.org>
fix "Crash when assigning materials" issue reported in <44f596fa$1@news.povray
.org>
[docs] [unix] fix navigation problems (malformed <a name></a> tags); add
'id' attribute together with 'name' and post-process their values for better
w3c conformance; workaround to missing images (gif->png) when building the doc
s
using the default "skip ta" makedocs option.
fix broken RLE Targa (+FC) output causing program abort (pixel overflow)
fix PNG output: corrupted file (missing IEND chunk) and potential memory leak
benchmark.cpp fix.
gamma changes, revert to beta.10 behaviour with some tweaks for more
extensive version checking.
In particular, specifying -MV3.7 or later via an INI file or the
command-line is taken at higher precedence than a #version 3.6 (or
lower) in the scene file when it comes to assigning the default state of
gamma correction (on/off, not its actual value if on). the value used
when it is on is determined by either Display_Gamma (if given) or
DEFAULT_DISPLAY_GAMMA otherwise. Similar steps are taken for the new
File_Gamma option.
The actual value of assumed_gamma is not passed on; this prevents its
use for anything other than turning gamma on or off (which is what the
majority of scenes did with it). Those scenes that (mis)used
assumed_gamma to adjust the scene appearance outside of the needs of the
user's actual display gamma will need to either be altered to suit, or
to be run with an adjusted Display_Gamma and File_Gamma.
NB users are warned that assumed_gamma support will be removed entirely
in a later 3.7 revision.
Adds gamma correction to file output. Need to determine if gamma
correction of alpha channel makes sense (3.6 and earlier manipulated
gamma in some strange way when merging filter and transmit). Further
added DEFAULT_ASSUMED_GAMMA macro to provide full backward compatibility
features for assumed_gamma (includes a strong warning).
Changes display gamma to consider assumed_gamma for legacy scenes and
issue extensive warning messages to inform users about the change and
how to fix their scene file
Adds "WorkThreads" INI option and "WT" command-line option to set
MaxRenderThreads
fix media photons (gather); also refactor some photon shooting code
implementing most of the functionality of old unix.cpp in a new
UnixOptionsProcessor class. This provides options processing for the
standard options as well as for the display subsystems.
This adds to the Unix frontend:
- io-restrictions
- povray.ini file processing
- help display
Further minor tweaks.
Adds FileGamma option
fix default blend map destruction issue.
fix object count when no bounding is used, rendering empty file leaves stop
icon, and winpov exit command not working issues as reported in
<442df1da$1@news.povray.org>.
fix photon memory issue referred to in <web.444b4f4ed5b924f08b9c27240@news.pov

ray.org>.
don't send mem usage stats as they are not accurate. have to fix this before
release.
make render failure messages a little more informative.
ensure first texture is supplied when parsing tiles declaration.
add exception translation (native windows to pov_base::Exception).
reconfigure backend to report some exceptions more clearly.
fix issue with ray interior being removed during evaluation of area lights.
fix issue with intersection min depth being too coarse (e.g. the liquid in
the glass in balcony.pov did not render).
check for zero-sized area light array parameters.
fix sombrero.pov bug reported in <web.442c3cd3ccb62fd8c7294af50@news.povray.or
g>.
improve error reporting when exception is caught in renderbackend.
also add range-checking of start/end column/row against render width/height.
bugfix for printing of max depth stopped nodes per node.
make sure parse and bounding times are included in stream output.
implement debug output to stream.
fix render percentage error when a large number of pixels are being rendered.
a few other tweaks.
change default BSP child access cost to 5.0.
tweak index insertion to massively speed up build of large trees
(e.g. abyss.pov build was 45s now 3s).

more changes to BSP tree reading.
small but important fix to BSP tree traversal - fixes occasional missing
object which could occur where the ray origin lay exactly on the splitting
plane.
BSP tweak, seems to speed things up a little.
also implement more robust support for reading externally-generated BSP trees.
should fix startup problems reported for initial release of beta.12.
some fixes to bounding and object count statistics. fix typo in attribute name
.
no longer use intel's math library (too much hassle for too little gain).
fix bug where some feature advice dialogs would be shown off-screen.
fix spheresweep copy bug reported in <43fbaf97$1@news.povray.org>.
fix 'aa incorrectly reported to be on' issue reported in
<43fc75f9$1@news.povray.org>.
Adds progress and stats reporting for BSP bounding
Fixes camera inside media/interior mostly lost bug
add means of setting BSP cost-function constants via INI file.
this is possibly temporary.
fix bug in BoundingTask::SendFatalError that was hiding real cause of
some errors.
some fixes for BSP code.

now works much better. code changed to read more like Eric Haine's
article so I can follow it more easily.
still work to be done to improve it.
fix debug message output.
AA method 1 block artifact fix (see <43ebe0bc@news.povray.org>).
also correct some jitter option issues and add slight optimization if
jitter is turned off.
NB it is still technically possible that block-boundary AA artifacts
could occur but they are much less likely.
fix bug in generation of lit intervals for media.
fix "light doesn't pass through transparent image_map" issue
(<43a97c75$1@news.povray.org>).
Fix 'trace fails with no_image object in union' bug reported in
<43f57a9d$1@news.povray.org>.
fix issue where cancelling a render may not work if all CPU resources
are committed to a render.
Adds smarter handling of bbox test for trivial objects
(boxes, spheres, etc)
Adds new BSP code
Threading control uses condition variable
Changes platform-config include file logic
Misc tweaks to error messages
Enables parser stats (incomplete)
Fixes generic timer bugs
a few fixes for the new-style povwin render window.
fix 'unrecognized file format' warning when HDR output is selected.
fix flipped image HDR reading bug (<43e8190e@news.povray.org>)

fix dispersion bug (long render times).
(re-)implement display retention and bitmap preservation during animation.
fix to image filename generation and rendered pixel counting.
add LF to lineoutput.
infer input directory from input file path if not supplied.
fix gamma assignment in PNG output.
version 3.7.beta.11a.
change Cone_Tolerance to 1.0e-9 as per suggestion from DKB.
hack fix into findfile stuff to accomodate relative filenames.
fix a few problems in option parsing WRT unrecognized keywords.
also mark Buffer_Output and Buffer_Size as superceded keywords (generates
parse error but doesn't stop render).
fix delayed crash caused by double-free of POVMS data.
work around crash when All_File is turned on.
a few misc changes.
provides for output gamma correction.
second part of gamma changes, still have file output to do.

improve responsiveness by using events for control thread waits
(esp. useful on fast animations).
fix input image file default type selection.
first part of gamma correction changes.
some speedups for BSP tree iteration.
fix for truetype objects within CSG.
Adds bounding method setting
SceneData stores output file type for use
this gets rid of the visual artifacts in bsptree tracing. still
need to optimize the bbox tests and more.
one bsp fix; helps somewhat but some issues still remain.
temporarily make bsptree a void* for faster rebuilds.
Intersection test with bounds for BSP tree like for BVH
Adds experimental BSP tree tracing
Unified handling of file names and paths as UCS2
find file now looks in current dir.
fix logic in output filename generation code.
some perl modules (+ example and generator) for helping
makefile generation.
a few tweaks to improve error display location in source files.

fix cancel state in windows frontend.
Adds Path class
Adds stream to file redirection
TaskQueue now processes one Task per call
File searching is now done by frontend
Fixes misc typos
fix some memory leaks in radiosity code.
tiny but important fix to BSP cost function.
Changes BSP cost algorithm to work almost right
Adds exception handler support to Task class
Fixes comments and semicolons in misc places
Adds a missing method to renderbackend
Adds failed state for view
fix uninitialized variable.
make default parse or render fail error less confusing.
fix crash in read_image_file.
add visual bounding volumes to bsptree dump.
a fix and more debugging stuff for bsptrees.
Completes BSP cost function (needs testing)
Adds automatic recursion limit to BSP building
Changes BSP code to use multiset

some fixes to bsptree bounding. this checkin does not fix the issue
with duplicate keys in the min/max sets.
windows changes - remove rerun handler.
add stack walker, radiosity progress, display gamma.
also misc fixes.
Adds gamma correction support to display
Adds
Adds
Adds
Adds
more frequent stop-checking to all render tasks

two tiny radiosity speed optimisations
progress reporting for radiosity
radiosity progress output in frontend

fix issue causing acne in e.g. cornell scene (with or without radiosity).
[SHADOW_TOLERANCE was not being taken into account in blocking object intersec
tion tests].
radiosity now working a lot better.
add Render_Block_Size INI option (+BS as command-line option).
fix crash caused by resource exhaustion (too many threads); refer <4303d267$1@
news.povray.org>.
address state issue referred to in <web.42af2f04951c51e46a3607400@news.povray.
org>.
tweak editor handling of missing files.
prevent multiple message-box display when switching focus and a file is modifi
ed or updated.
Mosaic preview now computes pixels rendered just like regular rendering,
which will cause the counters to loop for each preview step but they will
otherwise be correct. More information may be added latter for more accurate
progress reporting
Fix output file reporting issue reported in <web.430dc75ff23d654e726bd13c0@new
s.povray.org>.
few other minor tweaks.
ImageProcessing::WriteImage() now returns the name of the file it wrote.
Adds dispersion (still to be tested)
Fixes misc little issues
Attempt to fix a mosaic preview related pointer problem
fix render window re-display problem.
ensure local povray.ini search location is in source file dir.
add handler to throw std::bad_alloc on out-of-memory during operator new*.
misc changes to vc.net project file.
use FileMappedImageAllocator in windows project.
improve error reporting when image allocation fails.
handle out-of-memory condition when calling Image::Create().
a few fixes for mosaic preview.
radiosity fix.
Adds support for file-mapped image memory
Requires FILE_MAPPED_IMAGE_ALLOCATOR to be defined to be a standard STL
allocator that will be used when file-mapped image is required.
Adds support for mosaic preview.
focal blur bugfix.
Force finding free grid places in focal blur

Fixes of by one error in focal blur code
Fixes trace depth returning for radiosity
First version with radiosity sort of working (it is a "bit" too dark)
Concludes some major reorganisation:
All dependencies on global variables in the radiosity
code have been identified. However, the code cannot work
as is until the variables are passed along properly.
Vector and color classes had a rather serious (but easy
to overlook) bug that did never cause any problems before
because the features were never used before.
Misc little tweaks to previous changes
Mostly compiling major reorganisation of tracing, photons and radiosity
Media has been decoupled from tracing fairly cleanly
Media has been mostly decoupled from photon tracing (but not completely)
Radiosity has a structure better separating data and operations (but doesn't
compile yet)
Misc header dependencies have been removed
Misc changes preparing for radiosity
Cleans up quality settings use
Cleans up max trace level and adc bailout use
Cleans up dependencies on output file name in backend
Cleans up dependencies on output file type in backend
Reverts to set in block tracking
Adds fixmes to various places
Adds operators to colour classes
Adds warnings for non-longer available global settings
Fixes misc dependencies on global stuff or marks it
fix AA method 2 crash reported in <430358ed@news.povray.org>.
animation handling tweak for windows.
a bit more work on crackle.

Adds back buffering of samples to AA method 2 (should be as fast as in 3.6 now
)
implement per-thread crackle cache.
Adds parsing task queue
Moves bounding into parsing task queue (bounds don't for each view change)
New bounding location needs testing!
add HDR file support (RGBE).
exr support now uses the supplied streams and thus the correct filenames.
adds EXR file support using OpenEXR library.
very rough first pass, no options supported yet.
currently input and output file names are hard-coded; this has to be fixed.
Should fix an animation clock jump error
temporary change to SMALL_TOLERANCE just for beta.7. Need to change it back la
ter.
windows output stream changes.
fix version number display.
bump version to 3.7.beta.7.
Adds clock extraction to backend and clock use parser
animation support under windows, first pass.
needs core code support for clock to work.
make render cancellation more responsive in the presence of a large number of

threads.
fix continue code, also change logic a bit.
also the old behaviour of skipping a render if a completed output file is
present is not yet implemented.
get code from last few changes building under windows.
fix a few bugs in continue code. this is a WIP as continue still won't work un
der
certain skip list conditions.
Adds basic animation support
Makes misc pointers smart
Adds continue-trace feature. Currently consumes about 16*pixels bytes for
continue-trace file. Compression with zlib probably should be added as an op
tion.
Fixes a bug in reading of message objects
Tweak to file ids
Adds backend support for continue trace
Adds partial frontend support for continue trace
Replaces POV_RAND with a new pseudo-random engine that is thread-safe
as it just generates a predefined sequence of random numbers. This may
cause visual differences in some places. However, noise tables are still
initialised using the old random number algorithm, so there should be no
visual difference when rendering *plain* noise.
core code changes required to build with gcc on linux:
- backend/povray.cpp: changing "boost\version.hpp" to "boost/version.hpp" co
mmenting
hardcoded input file parameters.
- base/pov_err.h: some small, hopefully uncritical changes to make it compat
ible to gcc.
fix for problem with C99_COMPATIBLE_RADIOSITY
fix memory leak in photon code introduced in change #3804.

csg merge fix from Massimo Valentini.
quadric bounding fix from Massimo Valentini.
add windows thread startup/cleanup support.
set ideal processor for each thread.
fix bug reported in <428de855@news.povray.org> re:sunsethf.pov.
work around SMP bug in trace related to lighting code altering lightsources du
ring render.
for now each thread has its own copy of the lightsources. the lighting code sh
ould perhaps be
fixed to treat lightsources as const, in which case this workaround can go awa
y.
add fixed allocator useful for stack-based stl collections, and modify Ray to
use it.
add some infrastructure support for call profiling (more to come).
fix bug in photon code related to previous fix (see #3785).
small but important fix for photon building that fixes one speed issue.
fix scattering media problem reported in <427ca163@news.povray.org>.
This was two separate bugs; the media was sometimes being evaluated twice,
causing the result to be too dark, and the aa_threshold was not being set
correctly, causing artifacts. This also fixes <427c0121@news.povray.org>.
parser now honors Split_Unions and Remove_Bounds options.
undo changes to SMALL_TOLERANCE and MAX_DISTANCE submitted in #3320.
This fixes the lathe artifacts bug reported in <427c0f95@news.povray.org>.
It also fixes the sphere_sweep issue alluded to in #3759.
Fix no_image and no_reflection issues reported in <427c1900@news.povray.org>.
fix area light orient issue reported in <427c14ef@news.povray.org>.

fix issue where a new clip statement would overwrite a previous one rather tha
n appending to it.
fix speed issue with quadrics by reverting to old bbox calculation method.
note however that this method is faulty in some circumstances (see comments in
quadrics.cpp).
fix a swathe of memory leaks.
add boost library to library usage list.
fix leak of transform memory in numerous shapes.
Note: some shapes (notably CSG) do not copy the source transform. Have to chec
k why.
fix indexed PNG alpha problem reported in <42765ef3$1@news.povray.org>.
fixes area lights.
fix crash during trace() of lathe reported in <42796797@news.povray.org>.
improve handling of cancel_render() a bit (provide retry).
other windows tweaks.
fix for max_trace_level calculation and display (see <42769105@news.povray.org
>).
Also apply texture list fixes from #3761 to shadow rays.
fix memory leak.
make code more responsive to cancel/pause requests.
fix speed issues reported in <42769f6d@news.povray.org>.
ComputeTextureColour() was tracing a full series of rays (potentially up to Ma
x_Trace_Level)
for each detected texture in multi-component objects (e.g. blobs) even when th
e multi_texture
flag was not set.

fix for shadow problem mentioned in <42769f6d@news.povray.org>.
(other issues from <42769f6d@news.povray.org> still remain outstanding).
fix sphere_sweep bug reported in <42773e51@news.povray.org>.
There still seems to be a minor accuracy problem that was not visible in 3.6.
fix 'inverting pre-declared union' crash reported in <42769b59@news.povray.org
>.
focal blur fix, part 2 of 2.
partial fix for focal blur problem.
fix omnimax camera bug reported in <42775c1b$1@news.povray.org>, plus several
other related camera issues.
fix for facets pattern crash reported in <42773fab$1@news.povray.org>.
fix recursive memory leak when a CSG declare is redefined.
fix render area selection.
Should fix partial render area problems
Should fix state errors in frontend due to missing information in backend mess
ages
fix CSG merge issue reported in <42645c3b@news.povray.org>.
also re-implement some of the TODO code in Link_To_Frame.
re-implement error message when photon file fails to load in photons.cpp.
add warning and better progress reporting to photons.
update to beta.3, set windows expiry date to 15 May.

hopefully final part of hollow media fixes.
misc other tweaks.
work in progress; some fixes for hollow object media issue.
add CheckCameraHollowObject() method to View (this needs more work).
various minor changes.
centralise handling of filter/transmit<->alpha conversion in Colour class.
add methods allowing colours and images to be initialised from iterators.
re-enable alpha display in render window for windows port.
fix alpha bug reported in <web.426402d627a031d914107e060@news.povray.org>
fix no_image bug reported in <web.426402d627a031d914107e060@news.povray.org>
pass render settings to trace task (more to do on this subject).
add basic RGBFT<->RGBA conversion support to image classes.
turn Test_Ray_Flags and Test_Ray_Flags_Shadow into inline functions to make de
bugging easier.
change default bounding threshold back to 3 as per v3.6.
fix alpha inversion bug in BMP, Targa, and PNG file reading/writing.
numerous changes to ensure that RGBA or GrayA images have the alpha channel in
itialised to 1.0, not 0.0.
NB there is still a difference in alpha output compared to v3.6 which I have t
o chase down.
fix for crash mentioned in <42689685@news.povray.org>.
This was caused by a trace() intersecting a blob where the threaddata's blob i
ntervals array had not been resized.
N.B. we need to check other objects that use cached arrays for the same behavi
our.
fix noise generator default issue reported in <426898db@news.povray.org>.
this was also causing differences elsewhere in the code (e.g. in the appearanc
e of the irid in the previous fix).
fixed irid problem reported in <42680b39@news.povray.org>.
Also fixed similar issue with DepositMediaPhotons.
We need to audit codebase to check for more of these (class Colour being passe
d by value).
partial fix for hollow media issue reported in <42680e58@news.povray.org>.
also tweaked ComputeShadowMedia() as it didn't seem to make sense when called

from TraceShadowRay().
fix for area light problem from Massimo Valentini.
make quick_colour work again as it should (more or less).
also fix problem where language version was being extracted from quality setti
ng.
misc windows changes, mostly related to using intel emt64 compiler.
changes mostly to ensure that math.h isn't included before config.h.
this is to allow config.h to optionally include a compiler-specific math libra
ry such as Intel's mathimf.h.
Change 3707 on 2005/04/19 by _abx_@_abx_
Build fix for MinGW.
CSG inversion bug fixes
Misc other changes
Change 3698 on 2005/04/18 by thorsten@SMP
Fixes shadow flag copying bug
Adds max trace level check and trace level incrementing to TraceShadowRay
I/O restrictions stuff.
fix crash reported in <4263125b@news.povray.org> and one related bug.
fix render quality options output.
change references to 'CPU(s)' to 'thread(s)'.
update render time output to include fractional seconds.
tweak output filename and path logic.
Fixes AA method selection and enabling

Fixes image percentage size computation
fix for BMP reading.
add 'bmp' token to parser.
file output should default to on.
add output file type '+FB' (bmp).
add macro to equate SYS file type to internal file type where supported.
Fixes AA method 2 brightness issue
Fixes rendering area bug
Fixes no-display crash
Fixes image closing bug
Tweak to some radiosity local vars
windows stuff: customise error/warning message handling.
restore ability to open error file in editor (note: missing column number).
introduce helper class for error/warning messages.
remove some old code.
Change 3672 on 2005/04/16 by nkopp@impulse
add initialization for lots of photon-releated variables
Timing information
Adds shadow ray cache stat
we now have a shadow cache again
AA method 1 and 2 fully functional now

Restores AA method 2
Temporary solution for removed identifiers
implement cleanup when parse fails.
update built-in benchmark.
make sure photon task exits promptly if requested.
allow exception to be passed to Error() and ErrorAt() for throwing.
clean up parser on parse error.
ensure language version gets set to MessageFactory when changed.
fix apparent bug in old tokenizer warning code.
Adds photon stats and rendering timing output
Enable radiosity in view
Adds version warning
Adds basic radiosity support code
Adds shadow stat counter and adds misc stats outputs
fix for another bbox issue.
fix the photon "shadow blocking" problem for both
media and surface photons
add some more stats back in.
Some changes to fix shadow bounding box test of shadowless objects
Adds back trace level statistic
Adds Cooperate call to photons (so building can be interrupted)

Adds back basic stats
Focal blur is back! Should work with AA, too now!
Fixed what seems like a bug in refraction, too.
small but important interior fix!
Noise generator global variable access no longer needed
Noise setting, focal blur, bounding for show-rays
mostly fixed media photons.
Adds splitting of unions
Adds image output support to Windows code
Adds image output support
Adds ComputeShadowMedia
Adds clipping to image output
more photon-related fixes
fix object copy bug
re-enable media photons
restore support for POT files.
eliminate globals and shared variables from parametric object.

remove global from fractal code.
temporary fix for problem where quadrics return clip
region smaller than clipping object even when original bbox
was larger (this is particularly visible when bounding slabs
are turned off).
also add support for multiple clipping objects back.
fix torus artifact.
further changes of photon
Adds rainbow
Some cutting on light tests in media
This at last renders media correectly
add platform-specific thread startup and cleanup macros.
note that this change expects that boost::threads is modified
for win32 to not catch exceptions.
Fixes to media lit interval computation
Re-enable photons afterlatest round of changes
fix for interior uninitialised variables.
Removes misc global variables and some general code cleanup
image filter fixes.

Adds fog support
temporary work-around to stop boost:threads catching access violation etc exce
ptions.
Unified image types for colour maps
Added methods to get and set whole colour maps
fix problem with blend maps
Simplifies AA method 1 code
ensure gammacorrect is specified when reading image files.
ensure image files are closed after they are read.
Another AA method 1 change. Note that this
method is currently not identical to AA method 1
from POV-Ray 3.6 as there are a few odd things
in that algorithm...
exception handling changes
more correct handling of inverse keyword for CSG objects.
Rays now carry various important flags.
Adds atmospheric media
Media code is basically complete
media (re)integration part two - cleanups and more cleanups
in particular now color and vector components are properly accessed
rather than using indices 0, 1 and 2!

more internal blob tweaks
Changes INTERIOR to Interior and various variables named Interior to interior
Also changes IMEDIA to Media.
partial cleanup of blob code
Adds back bound sphere code
Makes sort function Axis a template
Fixes use of max trace level and adc bailout
Eliminates a message "race" (no, not really,
but close) condition that prevented proper stopping
Three arrays in Trace are now pooled/cached as well
Changes Ray and IStack to be passed by reference hopefully everywhere
Tweaks to use of bounding code
Tweaks to camera ray interior finding
Enables bounding slabs again (as a temporary bounding)
remove half-pixel offset from CreateCameraRay().
Progress reporting for parsing and rendering
Isosurfaces are now multithread-safe
Extensive attempt to resolve all but one isosurface threading issue
What remains is the use of eval and it modifying max_gradient - while

the serious problems with this have been resolved, storing a new
max_gradient involves a max() call, which is of course not thread-safe
and could result in a higher max_gradient getting overwritten. However,
it seems only a slight chance this could have a very serious impact only testing will tell. Either way, it won't cause visual problems
but could result in incorrect max_gradient being reported to the user
in case of using eval. It can however cause a slight slowdown under
very odd race conditions. Note that the other reporting is not
thread-safe either, but that should not be a major issue either...
save povwin settings before each render.
remove lathe and SOR mutexes by creating thread-local shared bounding arrays.
stop the thread_specific_ptr in Task from deleting TaskData.
changes mostly related to temp file handling.
remove weighting from TraceRay.
Restore time statistics output to message display (temporary).
Initialise default thread count to nCPU's*2.
Allow number of threads to be specified on command-line with '/THREADS n' para
meter.
add progress bar.
Adds ability to pause parsing as well as proper return messages
upon a user canceling parsing/rendering
Fixes problem with function pattern contexts in parser
Disables duplicate deletion of light sources
Adds VM internal function thread pointer passing via context
Eliminates need for function VM mutex
Reorganises thread specific data

Adds exception class and helper macros (pov_err.h)
Moves task and task queue to support
Enables Pause/Resume of parser
Adds message factory for easier output abstraction
wrap windows code in namespace povwin.
windows preview display
POVMS now supports sequences of ints, longs, floats and types,
which makes transmitting i.e. blocks of colors much more efficient
than using POVMS lists!
Further finished transmission of pixel blocks
Parser now runs in its own thread rather than the
message receiver thread (which was just a hack)
Integrates the new render task queue into the rendering process
Adds render task queue and render task classes. These will
allow to create a queue of individual threaded actions, i.e.
first run a bounding task, then a photon task and then a radiosity
task, and then run a render task. It also allows to start multiple
of these tasks and wait in between for a set of tasks to be
completed.
Adds handling of pixel blocks to frontend
Image read/write now take an options block
Adds gamma and easier handling of colour maps
add BMP to new image code. note that portable BMP support is now part of the c
ore.
adds pgm and iff support for new image handling

jpeg support for new image handling
add PNG support for new image handling
add gif support to new image code
Adds universal indexed image support
clean up targa support a bit.
add targa support to new image code
Adds image class to base/image/
make photon code more object-oriented and more thread-safe
work around fact BCyl code uses many temporaries shared between threads.
massage bbox and mesh stuff to ensure shared bounding tree data is const.
add code for bounding trees.
remove global mesh queue.
some tweaks to mesh to remove a few globals.
Adds background/skysphere support back.
Removes plenty of stuff from "opts"

cleanup core header use in windows files.
Adds partial preview back
can now use fractal istack in threaddata.
Removed dispersion code as it cannot be repaired but needs to be rewritten
Added back camera ray creation code, now rendering works much better again
Lighting enabled
remove the need for the intersections array in the prism
object by merging the code from Intersect() into All_Intersections.
remove Sx, Sy, Sz, Sw globals from quatern and hcmplx code.
Note that there is a temp. global that needs to be removed once access to thre
addata
is available to the run-time fractal code.
get rid of Distance and Precision global variables from fractal code.
Turns RAY, ISTACK and INTERSECTION into the classes
Ray, IStack and Intersection. This makes several dozen
support and initialisation functions obsolete. There no
longer is a max_intersections ISTACK limit either. As such,
no more ISTACK overflows and thee global setting
'max_intersections' is no longer needed.
some work with Max_Trace_Level/Highest_Trace_Level and stats.
update code to not use global stats variable.
update shape code to accept thread data pointer.

implement thread-safe local POVMS support in windows code.
split reserved words global into its own file so it can be linked
separately from the core code by e.g. a UI for syntax highlighting purposes.
clean out old render thread from pvengine.cpp
modify core project to include sub-categories of back-end code
project file changes, and in pvengine
Some major reorganisation of files
first step in introducing new stats collection structure.
changes to avoid literal copying of base class members.
Changes methods&structs to classes.

Revision PovRay

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Revision PovRay

Caricato da

Copyright:

Formati disponibili

#---------------------------------------------------------------------------# Note: To view an original flyspray bug report (FS#xxx), replace the leading

# FS# of the bug ID with the URL http://bugs.povray.org/.

compilers. if support is needed for any of the above, it would be better to

minor indentation cleanup of various sample scene files

remove all dependence on codemax header files

integrate flohmuller branch to trunk

suppress what appears to be a duplicate version related message

minor fix to radiosity statistics (octree samples/node)

Changes between 3.7.RC6 and 3.7.RC7

stream each time we open for append,

Change 5791 on 2013/02/09 by chrisc@x8

show "25,50 [0.125,0.250]". this is to make it easier to work out

Fix for FS#267: Bug in "sor" primitive leads to random black

Change 5724 on 2012/11/01 by jgrimbert@smpdirect

Fix whitespace in screen.inc

Fixed problems with colored transparent backgrounds.

Changes between 3.7.beta.RC3 and 3.7.RC4

added source trees for boost (subset of 1.45.0)

Follow up to change #5443 to retain a TODO comment

- Moved the setting of qualityFlags into the constructor of the TraceTask,

- Subsurface scattering is disabled in all quality levels except +Q9

Change 5391 on 2011/01/19 by chrisc@x8

introduced by an earlier refactoring)

Change 5350 on 2011/01/05 by clipka@cli-pc-xp64

updated insert menu files.

Change 5307 on 2010/12/28 by chrisc@x8

where Rp,Gp,Bp are colour component values pre-corrected for a display

Change 5279 on 2010/12/20 by chrisc@x8

Change 5256 on 2010/12/11 by clipka@cli-pc-xp64

Change 5216 on 2010/11/30 by chrisc@x8

scene is rendered using the File_Gamma INI file setting, or using

* PNG input file handling is not fully backward compatible.

was a fun time

Change 5196 on 2010/11/22 by jgrimbert@grimbert

Change 5195 on 2010/11/22 by chrisc@x8

Change 5180 on 2010/11/02 by chrisc@x8

Change 5166 on 2010/10/15 by chrisc@x8

Change 5154 on 2010/09/12 by chrisc@x8

object shall receive radiosity illumination) is currently NOT available.

Change 5099 on 2010/08/14 by jholsenback@jholsenback_aries

properly allow for libpng 1.25 AND 1.4.3

of threads for the whole pretrace,

pow ( Red_Amount, Gamma_Value )

* Previous versions of POV-Ray always expected straight (non-premultiplied)

- removed a few obsolete parameters and pieces of code

#for (I, 1, 100)

some photons changes:

texture { aoi texture_map { ... } }

Fix cone axis bug

Change 4899 on 2009/11/08 by clipka@cli-pc-xp64

where GAMMA is either a numeric expression specifying the approximate display

Change 4887 on 2009/09/10 by clipka@cli-pc-xp64

Some code refactoring.

------------------------------------------Change 4861 on 2009/08/06 by clipka@cli-pc-xp64

turns vain pretrace on/off

The postcondition in intersection tests had no means of taking SMALL_TOLERANCE

NOTE: this has changed the semantics of POVMS_ProcessMessages: previously, it

Change 4794 on 2009/05/27 by calimet@lavender

remove reference to uninitialized local variable causing radiosity stats to be

- slightly tweaked individual per-recursion parameters

If the optional 'once' keyword is present it must immediately follow the

fix sphere_sweep parse crash reported in <web.48bc447cc2ccad1e8510f03f0@news.p

fix str() crash reported in <web.4880f0adaf19f856c59235590@news.povray.org>.

additionally generate a warning message (as before).