Alain <aze### [at] qwertyorg> wrote:

> > Christian Froeschlin<chr### [at] chrfrde>  wrote:
> >> jhu wrote:
> >>
> >>> I've split up each line to be rendered by different cores and computers.
> >>
> >> I wonder if that actually increases the total time needed for radiosity?
> >
> > I think it does, but since I'm using 3.6.1, the overall time taken to render is
> > less. Also, because it's taking so long, if anything happens, I still have some
> > progress saved (more than if I hadn't split up the render), like when my
> > computer's PSU died a few weeks ago from probably too much rendering.
> >
> >
>
> You should REALY update to version 3.7. I've totaly stoped using version
> 3.6.1 about 2 years ago...
>
> Radiosity tend to be somewhat faster, even on only one core. You can use
> all of your cores using only one instance as oposed to needing as many
> instance as you have cores with 3.6.1. To use 4 cores with 3.6, you need
> 4 instance of POV-Ray, 4 instance of the source files and have 4
> instance of the parsed scene. This greatly reduce the amount of RAM
> needed and can save you from using the page file = MUCH faster!
> POV-Ray is only loaded once, as is the scene file.
> Also, aa is greatly improved and faster.
>
> With 3.6 and using radiosity, you always get discontinuities when you
> reconstruct your partial renders to get the complete image. It's also
> the case when you resume a render with +c. It's no longer the case with 3.7.
>
>
>
> Alain

I have 16 GB of RAM so that's not an issue. Discontinuities are also not an
issue when partial images are stitched together. Also, when is 3.7 coming out of
beta?

Post a reply to this message