|
 |
Hello all,
Can I get an in-depth explanation as to why radiosity rendering slows
down so much as nearest_count is increased? From the POV-Ray 3.5 docs, and
my test renderings, it seems that nearest_count is simply interpolating
between samples, which hardly sounds compute-intensive.
Thanks,
George Pantazopoulos
Post a reply to this message
|
|
|
|
George Pantazopoulos <the### [at] attbi com> wrote:
> Can I get an in-depth explanation as to why radiosity rendering slows
> down so much as nearest_count is increased? From the POV-Ray 3.5 docs, and
> my test renderings, it seems that nearest_count is simply interpolating
> between samples, which hardly sounds compute-intensive.
POV-Ray has to find the required amount of samples close enough to the
current point. If there aren't enough samples, it can't interpolate and thus
has to perform regular sampling (ie. shoot rays).
By increasing nearest_count you are making it less probable that the
required amount of samples are found close enough to the current point.
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
