|
|
In some commercial renderer I'm using, tweaking the BSP size and depth for every
scene is key to getting reasonable render times. In Pov it seems to take care of
itself, from reading what I could find about it. That would be great, but does
it? Or would we benefit from even more acceleration if we tweak every time? if
so, with which parameters and with what tools or statistics to set them? (In
the renderer I talked about, I use the diagnostic modes showing some blue to
red false color dynamic for BSP "size" or "depth", one at a time).
Post a reply to this message
|
|
|
|
> In some commercial renderer I'm using, tweaking the BSP size and depth for every
> scene is key to getting reasonable render times. In Pov it seems to take care of
> itself, from reading what I could find about it. That would be great, but does
> it? Or would we benefit from even more acceleration if we tweak every time? if
> so, with which parameters and with what tools or statistics to set them? (In
> the renderer I talked about, I use the diagnostic modes showing some blue to
> red false color dynamic for BSP "size" or "depth", one at a time).
>
>
If you mean "binary space partitioning", POV-Ray 3.6.2 don't use it. It
use a simple bounding boxes testing protocol.
The 3.7 betas do, optionaly, use an octree structure invoked by the
"+bm2" switch. You can use it from the command line or from an .ini
file. It can accelerate the tracing. The depth is dynamicaly set at
parse time.
Alain
Post a reply to this message
|
|
|
|
Alain <aze### [at] qwertyorg> wrote:
>
> The 3.7 betas do, optionaly, use an octree structure invoked by the
> "+bm2" switch. You can use it from the command line or from an .ini
> file. It can accelerate the tracing. The depth is dynamicaly set at
> parse time.
>
>
> Alain
Yes I did use it, and it did improve my render time. That's what I meant by "In
Pov it seems to take care of
itself"
I'm just wondering why they didn't do such autmatic tweak in commercial
software. And wonder how much we can trust it to adapt to every scene?
Post a reply to this message
|
|