From looking at the posts in povray.bugreports, it seems users have found a
few bugs in the current version of POV.  However, it seems the cause of just
about all these bugs have been found, and how to correct them in the POV
source files has also been posted.

I was wondering if the POV team were planning on releasing a minor upgrade
(something like 3.11 or 3.1b) that fixes these known problems - I would
imagine it wouldn't take too long to do this considering all the necessary
corrections to the source has already been given.  The most clear and
helpful post appears to be "List of bugs" in povray.bugreports - that
details just about all the current bugs, and how they can be fixed (or where
the fix was posted).

Any ideas if this "official" POV bugfix release is in the works, and whether
it will be released in the near future?



Matt

--
Author of the DataCloak file encryption utility:
http://www.btinternet.com/~bennett/datacloak.html

Post a reply to this message

Matthew Bennett <ben### [at] btinternetcom> wrote:
: I was wondering if the POV team were planning on releasing a minor upgrade
: (something like 3.11 or 3.1b) that fixes these known problems - I would
: imagine it wouldn't take too long to do this considering all the necessary
: corrections to the source has already been given.  The most clear and
: helpful post appears to be "List of bugs" in povray.bugreports - that
: details just about all the current bugs, and how they can be fixed (or where
: the fix was posted).

  This is a part of the article posted by Chris Young to c.g.r.r:

>         That said... we've got several bug reports we're working on
> right now.  I know there has been some frustration that we've not
> fixed them sooner and have not used your supplied fixes.  We deeply
> appreciate the fixes, keep 'em coming.  But some of the fixes are only
> partial fixes, some could have very serious side effects (such as
> changing the EPISLON value), and some have major impact on
> long-standing parts of the code (such as the averaged normal bug vs.
> the double-illuminate workaround).  Nearly ALL of the recent bugs have
> existed since 3.0, most since 2.2 and one since before POV-Ray existed
> (its a bug from the old DKB-Trace upon which POV-Ray is based.)
> Given our need for vacation and the age of these bugs, we've not made
> bug fixes a high priority but it is the next item on our agenda.  Look
> for POV-Ray 3.1b in a few weeks.

-- 
main(i){char*_="BdsyFBThhHFBThhHFRz]NFTITQF|DJIFHQhhF";while(i=
*_++)for(;i>1;printf("%s",i-70?i&1?"[]":" ":(i=0,"\n")),i/=2);} /*- Warp. -*/

Post a reply to this message