POV-Ray : Newsgroups : povray.beta-test.binaries : FYI: radiosity changes integrated : Re: FYI: radiosity changes integrated Server Time
7 May 2024 17:55:25 EDT (-0400)
  Re: FYI: radiosity changes integrated  
From: clipka
Date: 17 Jan 2009 09:15:00
Message: <web.4971e6efbea0b42d1c9be6790@news.povray.org>
"TomAust" <aus### [at] aust-manufakturde> wrote:
> Hi,
>
> this image shows a detail of a building rendered in Beta29/30 and Beta30rad1.
> The whole rendering shows the complete building and has a resolution of
> W4500xH3000.
> Settings are equal except nearest_count and low_error_factor at the suggestion
> of clipka:
>
>  //nearest_count 1
>  //low_error_factor 0.5
>  recursion_limit 1
>
> On Vista64
> QuadCore @2.66GHz
> the rendertime was 23min with Beta29/30
> and 220min with Beta30rad1.

Are you aware that commenting-out the nearest_count setting gives you a default
value of 5?

Anyway, this starts to seriously bug me. From my test renders I had the
impresson that serious slowdown occured only at higher recursion_limit values,
not with single-bounce shots. Now all reports coming in seem to indicate
otherwise.

Blood-stained excrements of a male bovine.

I can imagine only one thing that could cause this difference in a single-bounce
shot: Effective trace depth.

What are your global trace_limit and adc_bailout values?

(Would you be willing to disclose the scene file so I could do some toying
around with it? If public posting is not an option, you might send it to
christoph <at> lipka-koeln <dot> de.)


> Full of hope
> TomAust

Yeah - I, too, hope to be able to find the cause of those slowdowns... obviously
they're more serious in practice than I expected, so the status quo is
unacceptable.


(BTW, the building looks strikingly familiar - I fancy that I've seen the
original somewhere in the south of Cologne... Zollstock maybe?)


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.