|
![](/i/fill.gif) |
Jan Walzer wrote:
>
> Peak memory was about 340MB...
> Therefore I needed to lower the count to
> I tried it with count=196 but my memory didn't agree with this idea ;)
>
> Any ideas, how to tweak the rad-settings ?
> Other comments ?
>
> pretrace_start 0.02
> pretrace_end 0.01
> count 128
> nearest_count 10
> error_bound 0.05
> recursion_limit 3
> low_error_factor .5
> gray_threshold 0.0
> minimum_reuse 0.01
> brightness 1
Yes, lots.
1. Lower recursion_limit to 2 if possible. In most cases, higher levels
have no significant effect on the scene.
2. The best ways to save memory, IMO, are increasing error_bound and
reducing count (both of which will reduce render time as well). In your
case, count will need to be high to get smooth lighting, but unless you
need sharp, precise shadows, an error_bound of 0.3 is sufficient.
Alternately, you could leave those values where they are, but reduce
nearest_count.. of course, that will increase artifacting, which means a
higher count, which means you end up reusing the memory you'd save..
it's a tricky dance. Try changing the error_bound first.
3. Change the low_error_factor to 1. error_bound is already sufficiently low.
4. With an error_bound of 0.3, you can improve quality by using a really
low pretrace end, say 2/width or so.
5. For some reason, setting adc_bailout to 1 seems to slightly reduce
render times while having no visible effect on the scene. This is
counterintuitive, but give it a shot.
-Xplo
Post a reply to this message
|
![](/i/fill.gif) |