>I might rename to *_photons.  However, if we keep it as save_file and
>load_file, then we could use the same keywords in the radiosity{} block (no
>need for new keywords) to save/load radiosity.

Good foresight... it actually crossed my mind (very briefly, so I ignored
it...)

>And yes, this could
>definately be done with radiosity (the radiosity octree can already be
>saved/loaded by POV for continued renders).

Aha... so why isn't that being done already? <Yoda>Hmmmm?</Yoda>

>The only problem with radiosity
>is that POV will usually calculate more radiosity data during the ray-trace
>pass.  This could be prevented if necessary, though.

Please, be my guest... prevent it... :)

>This feature (saving/loading the photon map) is also intended to help with
>network rendering possibities in the future.  It should be in the docs
>somewhere.  If not, I'll have to add it.


I haven't read the docs extensively, but I don't think I saw that. The
network rendering would sure be swell.

Post a reply to this message