|
 |
In article <3611B04F.8B1B33ED@videotron.ca> , Stephane Hockenhull <pot### [at] videotron ca>
wrote:
>little suggestion: you might put a (one time, not for every rays :)
>warning in povray, so that when max_trace_level is reached, it says:
>"oups, max_trace_level reached, try raising it!"
You *will* see it if you look at the statistics after the image is rendered, near the
top, right is exactly this information!
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
Post a reply to this message
|
|
|
|
>
> >little suggestion: you might put a (one time, not for every rays :)
> >warning in povray, so that when max_trace_level is reached, it says:
> >"oups, max_trace_level reached, try raising it!"
>
> You *will* see it if you look at the statistics after the image is
> rendered, near the top, right is exactly this information!
yeah, someone else already told me :)... it's like finding a needle in a
hay stack and that's when povray doesnt turn (yeah, you can still go an
read it) the rendering/statistic page.
a C/C++ compiler gives you warnings in a special window so you're kinda
forced to read (and correct) them.
but now that I know this, i'll check the statistic first when I get some
weird results.
btw, I gotta thank all repliers.
--
Stephane Hockenhull
Rv[PotamSoft]
mailto:pot### [at] videotronca
http://pages.infinit.net/potam/
Post a reply to this message
|
|
