Hi all,

I lifted the following from Alan Kong's post in
povray.announce.frequently-asked-questions.

......
3.1c               1/29/99 Chris Young
Fixed radiosity preview with odd screen size.
Reinitialized max_trace_level & radiosity_trace_level properly
Fixed token at end of file with no cr/lf or newline
......

Does this mean that in 3.1e, it'll be possible to halt a radiosity trace without
having to
restart POV?

-----------
Andy

Post a reply to this message

In article <36e296b1.0@news.povray.org> , "Andrew Cocker" 
<and### [at] acockerfreeservecouk> wrote:

> I lifted the following from Alan Kong's post in
> povray.announce.frequently-asked-questions.
>
> ......
> 3.1c               1/29/99 Chris Young
> Fixed radiosity preview with odd screen size.
> Reinitialized max_trace_level & radiosity_trace_level properly
> Fixed token at end of file with no cr/lf or newline
> ......
>
> Does this mean that in 3.1e, it'll be possible to halt a radiosity trace
without having to
> restart POV?

No, it is the other way around. On platforms that don't terminate between
each render you would get some unexpected results. This is fixed now and to
continue a render with radiosity will work a bit better now.


    Thorsten



You can observe at least the max_trace_level bug in the Windows and Mac
version of 3.1a: Create a scene and set do not set max_trace_level in that
scene In the statistics output you see something like "Max Level: 2/5" where
the 5 is the max_trace_level. Now change it to to some value other than the
default (which is 5), i.e. use 20. The you will see "Max Level: 2/20". Now
remove the max_trace_level again and you would expect "Max Level: 2/5" but
get  "Max Level: 2/20". In 3.1d this is fixed and you get as expected "Max
Level: 2/5". (I am not sure, but I think you can't see radiosity_trace_level
problem anywhere in the stats output.)

Post a reply to this message

Thorsten Froehlich wrote in message <36e2b1ed.0@news.povray.org>...
>In article <36e296b1.0@news.povray.org> , "Andrew Cocker"
><and### [at] acockerfreeservecouk> wrote:
>
>> I lifted the following from Alan Kong's post in
>> povray.announce.frequently-asked-questions.
>>
>> ......
>> 3.1c               1/29/99 Chris Young
>> Fixed radiosity preview with odd screen size.
>> Reinitialized max_trace_level & radiosity_trace_level properly
>> Fixed token at end of file with no cr/lf or newline
>> ......
>>
>> Does this mean that in 3.1e, it'll be possible to halt a radiosity trace
>without having to
>> restart POV?
>
>No, it is the other way around. On platforms that don't terminate between
>each render you would get some unexpected results. This is fixed now and to
>continue a render with radiosity will work a bit better now.
>
>
>    Thorsten
>
>
>
>You can observe at least the max_trace_level bug in the Windows and Mac
>version of 3.1a: Create a scene and set do not set max_trace_level in that
>scene In the statistics output you see something like "Max Level: 2/5" where
>the 5 is the max_trace_level. Now change it to to some value other than the
>default (which is 5), i.e. use 20. The you will see "Max Level: 2/20". Now
>remove the max_trace_level again and you would expect "Max Level: 2/5" but
>get  "Max Level: 2/20". In 3.1d this is fixed and you get as expected "Max
>Level: 2/5". (I am not sure, but I think you can't see radiosity_trace_level
>problem anywhere in the stats output.)



Ah I see....okay, thanks

-----------
Andy

Post a reply to this message