There's a little bug in povray for windows (at least in 3.1a and 3.1d):

  For example, render a scene with max_trace_level 7. After rendering, one
line of the messages window says something like this:

Rays:             40317   Saved:                 0   Max Level: 7/7

  Now change to max_trace_level 5. After rendering, the same line will say:

Rays:             40317   Saved:                 0   Max Level: 7/5

  Obviously it should say 5/5, not 7/5.
  If you restart povray and render the same scene, the line says, correctly:

Rays:             40317   Saved:                 0   Max Level: 5/5

  The max level value will always change to higher but never to lower values
until you restart povray.

  This little bug will probably not annoy most of people, but if you are
watching that value to search for good max_trace_values while changing the
scene, you will get wrong results.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Mika wrote in message <36f8b290.0@news.povray.org>...
>  There's a little bug in povray for windows (at least in 3.1a and 3.1d):
>
>  For example, render a scene with max_trace_level 7. After rendering, one
>line of the messages window says something like this:
>
>Rays:             40317   Saved:                 0   Max Level: 7/7
>
>  Now change to max_trace_level 5. After rendering, the same line will say:
>
>Rays:             40317   Saved:                 0   Max Level: 7/5
>
>  Obviously it should say 5/5, not 7/5.
>  If you restart povray and render the same scene, the line says,
correctly:
>
>Rays:             40317   Saved:                 0   Max Level: 5/5
>
>  The max level value will always change to higher but never to lower
values
>until you restart povray.
>
>  This little bug will probably not annoy most of people, but if you are
>watching that value to search for good max_trace_values while changing the
>scene, you will get wrong results.


Why are there two numbers (Max Level A/B) present anyway?...
Since the second one always changes to the value you set in the scene, does
it matter that the first one does not appear to be correct?...


Matt

Post a reply to this message

Matthew Bennett <ben### [at] btinternetcom> wrote:
: Why are there two numbers (Max Level A/B) present anyway?...
: Since the second one always changes to the value you set in the scene, does
: it matter that the first one does not appear to be correct?...

  I have understood that the second value is the max_trace_level you have
set and the first value is the actual number of recursions povray had to
calculate at max.
  Ie. if the max level says 4/7 then it means that you have set
max_trace_level to 7 but povray only needed 4 (ie. if you change your
max_trace_level to 4 the image will be identical).
  For example, if your image has only one refracting sphere (no reflection)
and a plane, the max level should say 2/5.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message