|
![](/i/fill.gif) |
> Kenneth wrote:
>
>> I.e., a 'matching' value of pow(2,16) isn't possible. Which would
>> indeed result
>> in some black pixels, I think.
>
> in those cases, pow(2,16) would probably give you *no* pixels ;)
>
> Actually I think it is strange that adc_bailout would give you
> extra black pixels. I would have expected max_trace_level to return
> black only for the remaining part of the ray which was cut off. Then,
> if that rays contribution was already negligible, there should not
> be much difference. But if I read the docs right this is not how
> max_trace_level works?
When you reatch max_trace_level the ray return black.
A thing that can sometimes save you is when the ray have been split
trhough partial reflection.
In that case, it looks like that path(s) that stoped before
max_trace_level are retained and mixed with the black.
The result in 3.6 and 3.7 are not the same in that case.
Alain
Post a reply to this message
|
![](/i/fill.gif) |