"Bald Eagle" <cre### [at] netscapenet> wrote:
> I'm currently experiencing a major bottleneck in the radiosity-enabled render.
> It seems to me to be hanging up on the heightfield frame of the big round mirror
> on the left.
>
> I'll try to pore over the docs again, but I'd appreciate it if someone could
> suggest a quick (heh) fix to get past those sticky spots.  It went fairly fast
> until it hit that, and now it's 12 hours later and still struggling.
> WHAT is it _doing_??!
>
> Also, is there a _short_ concise explanation of this file that radiosity can
> generate?  If I suffer through this once, does it make subsequent renders vastly
> faster?
>
> Thanks!
>
> pretrace_start 0.08
> pretrace_end 0.04
> count 35
> nearest_count 5
> error_bound 0.5
> recursion_limit 3
> low_error_factor 0.5
> gray_threshold 0.0
> minimum_reuse 0.015
> maximum_reuse 0.2
> brightness 1
> adc_bailout 0.01

These settings are pretty low quality IMO, as you mention the files I am
guessing you are generation radiosity data with AA switched on?

You will get a big increase in speed by saving the rad data to a file with no AA
on this pass of your image, you can then load this data and use AA or I prefer
focal blur with a low aperture setting, and the image will trace much faster.

I usually use some variables to control radiosity a variable to control the
quality and another to determine if data should be loaded or saved. You also
have to use the command line switches +RF"filename.rad" to specify a file name
and either +RFO when saving or +RFI when loading data.

Most scenes I have uploaded to the scene files threads will have settings in
them you can copy. Not on my PC at the moment or I would provide an example.

Also I often use simple textures when saving the radiosity data again using a
variable to switch on/off test textures, you can save the data with a very
simple quick texture the use real textures for the final render.

Sean

Post a reply to this message