Thomas de Groot <tho### [at] degrootorg> wrote:

> Using +C works correctly on a render without saved radiosity data, as
> radiosity calculations restart again for the not-rendered part of the
> image and only for that part. So, what you may be seeing is not a
> complete re-calculation but only for the not-rendered region? That would
> be correct.
>
yes, that's the way it is if i don't save rad-data (either v3.62 or v3.7 rc5/6-
sometimes i deleted the v3.62.rca file to see the unrendered part again in
pretrace)


>  From your post I assume you do not save/read radiosity data? For very
> long renders using sslt in particular I think that would be necessary.
> with the pretrace value at 1 for the reading sessions as Clipka wrote.
>

but i did use v3.7 rc5/6 with radiosity_file_name="xyz", radiosity_to_file = on
and radiosity_from_file = on
and i think, this is the way to save rad-data, is it ?)
and even with that the pretrace (for the unrendered part) is starting all over
again, from pretrace_start-size to pretrace_end-size.

yesterday i did start a clean new render with v3.7 rc6:
radiosity pretrace completely finished after 11 hours. then 3 more hours gave me
18% of render. then i stopped.
today i continued with pretrace_start and _end set to 1 as suggested and as i
started the render, the image was as i left it, but povray was at 83%.
rendering for 11 hours gave me nothing... still 83%, still the same image.

well, maybe it is a point that really will take long to render, longer than 11
hours, but why the 83% ?
sorry, but i'm confused.
all other things work great, maybe i should just shorten the rendertime :)

Post a reply to this message