|
![](/i/fill.gif) |
"MikeH" <Ama### [at] aol com> wrote...
> In MegaPOV, when you use the load_file option in radiosity settings, it
> still renders the radiosity preview step. This seems contrary to the
> point of saving the radiosity file and later reloading it - that is, to
> save render time. It's easy enough to 'fix', but was wondering if there
> was any reason why the mosaic preview step is done in that situation?
It does the radiosity step because it continues to calculate radiosity.
Radiosity calculation even continues to happen during the final render step
(unless you turn it off with the appropriate MegaPov feature). The
radiosity preview step will be faster if you've loaded data that you saved
already. We try to gather more to fill in details in case the camera has
moved, or to just improve the radiosity estimate. You can make the step
really quick by using a very large pretrace_start and pretrace_end.
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |