 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
According to POV-Ray Help it is not a good idea to save and load radiosity
data with 'save_file' and 'load_file' if scene objects are moving. I'm
wondering if this includes the camera. Can I reuse the radiosity data after
only moving the camera position?
If so, I can safe lotsa time with animations only involving the camera
position.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Apache wrote:
>
> According to POV-Ray Help it is not a good idea to save and load radiosity
> data with 'save_file' and 'load_file' if scene objects are moving. I'm
> wondering if this includes the camera. Can I reuse the radiosity data after
> only moving the camera position?
>
> If so, I can safe lotsa time with animations only involving the camera
> position.
No, that's not a good idea. In Povray radiosity data is only calculated
for the area visible so changing the camera view will lead to bad results
too.
Christoph
--
Christoph Hormann <chr### [at] gmx de>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
So 'save_file' safes time only in case of resuming aborted renders without
any scene changes?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Apache wrote:
>
> So 'save_file' safes time only in case of resuming aborted renders without
> any scene changes?
In fact it's 'load_file' what saves time of course, but yes, that's
correct. Of course it also helps when rerendering with changed render
parameters like antialiasing etc.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 29 Nov 2001 07:43:40 +0100, "Apache"
<apa### [at] yahoocom> wrote:
>According to POV-Ray Help it is not a good idea to save and load radiosity
>data with 'save_file' and 'load_file' if scene objects are moving. I'm
>wondering if this includes the camera. Can I reuse the radiosity data after
>only moving the camera position?
>
>If so, I can safe lotsa time with animations only involving the camera
>position.
The algorithm POV-Ray uses for global illumination does not calculate
diffuse interreflections for the whole scenes, as do true radiosity
renderers such as Radiance. It only calculates and stores what it
needs considering the camera field of vision. The result? Well, what
you're asking for is generally impossible.
There may be a workaround in some cases, though.
Imagine a room lit by a light bulb. The bulb is places so that it
illuminates most of the room directly, and radiosity will take care of
the rest. In other words, any point in the room is a ray "hop" or two
away from the light source. Therefore, you may place a spherical
camera coinciding with the light source and save the radiosity data,
then reuse it in a "fly around" or "turn around" type of animation. If
you use very high quality settings to gather radiosity data, it might
just work.
I haven't tested it but I intend to when I finish model ling my
current scene.
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3C05ECCC.591F00DC@gmx.de> , Christoph Hormann
<chr### [at] gmxde> wrote:
> In fact it's 'load_file' what saves time of course, but yes, that's
> correct. Of course it also helps when rerendering with changed render
> parameters like antialiasing etc.
I thought the radiosity data file is kept when interrupting a render so a
continue trace is always possible, which I am fairly sure worked in 3.1???
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
>
> I thought the radiosity data file is kept when interrupting a render so a
> continue trace is always possible, which I am fairly sure worked in 3.1???
>
Not in the windows version, with Linux it was possible in 3.1, don't know
about 3.5 of course. If it's also standard in the Mac version, it should
maybe be changed in WinPov.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann <chr### [at] gmxde> wrote:
: Not in the windows version, with Linux it was possible in 3.1, don't know
: about 3.5 of course. If it's also standard in the Mac version, it should
: maybe be changed in WinPov.
I agree with that. It worked that way in the DOS-version, it works that
way in unix and apparently in MacOS. Why it doesn't work that way in Windows
is a mystery to me.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If you calculate radiosity with a higher recursion level (eg. 3 or 4) then
povray calculates illumination of many hidden-to-the-camera surfaces as well.
It would be interesting to try doing this and then moving the camera to see
what happens.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3c06a3fe@news.povray.org> , Warp <war### [at] tagpovrayorg> wrote:
> Why it doesn't work that way in Windows is a mystery to me.
It should work. If it doesn't, you know what to do.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
