I can't prove anything but somehow I feel below can cause some kind of error
(crash, bad image, etc). I wonder about radiosity in animation. I have SCENE.POV
script with scene of animation with radiosity. Then I start two instances of
POV-Ray:
first: +KFF100 +EF50 +ISCENE.POV
second: +KFF100 +SF51 +ISCENE.POV
but during trace proces there is only one file SCENE.RCA. Is it good behavior ?
Both images are different - objects move. I don't use save/load feature of
radiosity but I can imagine somebody can. Shouldn't RCA file be named like
currently rendered image ? Of course I'm talking about 3.5.

ABX

Post a reply to this message

> but during trace proces there is only one file SCENE.RCA. Is it good behavior ?
> Both images are different - objects move. I don't use save/load feature of
> radiosity but I can imagine somebody can. Shouldn't RCA file be named like
> currently rendered image ? Of course I'm talking about 3.5.

  That's exactly how it works. It uses one file for the radiosity data tree.
When the rendering finishes, it deletes this temporary file.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

On 8 Apr 2002 13:13:28 -0400, Warp <war### [at] tagpovrayorg> wrote:
> > but during trace proces there is only one file SCENE.RCA. Is it good behavior ?
> > Both images are different - objects move. I don't use save/load feature of
> > radiosity but I can imagine somebody can. Shouldn't RCA file be named like
> > currently rendered image ? Of course I'm talking about 3.5.
>
>  That's exactly how it works. It uses one file for the radiosity data tree.
> When the rendering finishes, it deletes this temporary file.

but... is it safe when two applications write data to one RCA file ?

ABX

Post a reply to this message

so running multiple versions of the same filename (in the same path,
on the same machine, of course) with different data parallel will
work wrong ... Is this what you said?

Post a reply to this message

Jan Walzer <jan### [at] lzernet> wrote:
> so running multiple versions of the same filename (in the same path,
> on the same machine, of course) with different data parallel will
> work wrong ... Is this what you said?

  POV-Ray does not support parallel rendering. Thus collisions can happen.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

> but... is it safe when two applications write data to one RCA file ?

  POV-Ray is not designed to perform parallel raytracing.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

but it would be a "minor" change (in the next MegaPov, of course) to build
a hash 'bout the parsed Code, and its "variables" to have a unique identifier
for this File, one could append ....


... but thats probably just a silly idea (Hey, its early morning here, isn't it ? ;)

Post a reply to this message

On Tue, 9 Apr 2002 09:01:15 +0200, "Jan Walzer" <jan### [at] lzernet> wrote:
> but it would be a "minor" change (in the next MegaPov, of course) to build
> a hash 'bout the parsed Code, and its "variables" to have a unique identifier
> for this File, one could append ....

unique identifier is a name of current image becouse it contains number of
frame.

ABX

Post a reply to this message

On 8 Apr 2002 15:59:31 -0400, Warp <war### [at] tagpovrayorg> wrote:
> > but... is it safe when two applications write data to one RCA file ?
>
> POV-Ray is not designed to perform parallel raytracing.

so another thing to do for me in patching time

ABX

Post a reply to this message

what if someone makes use of some "external-parameters" such as current
time/date, to make a nice watch ? ...

... and maybe, he doesn't want an animation ... ? ... and he starts it
at different times while the first one is still running ...

So what is left, if the filename (and "frame") is the same ?

hence I said, that probably a hash of a memdump  (after parsing) is
necessary, to create a unique ID

Post a reply to this message