In the docs, it says following:
6.1.3.4.2
...
final_frame
This identifier reads the value set through the INI file option
Final_Frame=n or the command-line switch +KFFn.

But, in effect, final_frame returns the last frame rendered.
For example this:
+KFI1 +KFF150 +EF19

would return 19 for final_frame, instead of 150.

Is this behaviour correct and described wrong in the docs, or
the behaviour wrong and described correct in the docs?

I'm using POV-Ray for Windows 3.5, on Win98, 1.4GHz Athlon, 768 MB RAM.

Any confirmations?


--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

Post a reply to this message

Oh, here's minimum source:

//+KFI1 +KFF3 +EF2
#debug concat("final_frame:",str(final_frame,0,0),"\n")

Put the comment into the commandline.

--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

> In the docs, it says following:
> 6.1.3.4.2
> ...
> final_frame
> This identifier reads the value set through the INI file option
> Final_Frame=n or the command-line switch +KFFn.
>
> But, in effect, final_frame returns the last frame rendered.
> For example this:
> +KFI1 +KFF150 +EF19
>
> would return 19 for final_frame, instead of 150.
>
> Is this behaviour correct and described wrong in the docs, or
> the behaviour wrong and described correct in the docs?
>
> I'm using POV-Ray for Windows 3.5, on Win98, 1.4GHz Athlon, 768 MB RAM.
>
> Any confirmations?
>
>
> --
> Tim Nikias v2.0
> Homepage: http://www.digitaltwilight.de/no_lights
> Email: Tim### [at] gmxde
>
>

Post a reply to this message

In article <3e8af461$1@news.povray.org> , "Tim Nikias v2.0" 
<tim### [at] gmxde> wrote:

> Oh, here's minimum source:
>
> //+KFI1 +KFF3 +EF2
> #debug concat("final_frame:",str(final_frame,0,0),"\n")
>
> Put the comment into the commandline.

It used to work this way in MegaPOV 0.x before, and everybody was fine with
it, so I guess the current behavior is what is desired, but I don't know.

    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

If it is the desired method, I think it would be
best to describe that in the docs. Additionally,
since POV-Ray is also used for animations,
it might be a consideration to add another two
floats. I've noticed that initial_frame also only
returns the number from Subset-Framing. So
perhaps it might be a good idea to add some
constant-floats which will return the actual
KFI and KFF values...



--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

>
> > Oh, here's minimum source:
> >
> > //+KFI1 +KFF3 +EF2
> > #debug concat("final_frame:",str(final_frame,0,0),"\n")
> >
> > Put the comment into the commandline.
>
> It used to work this way in MegaPOV 0.x before, and everybody was fine
with
> it, so I guess the current behavior is what is desired, but I don't know.
>
>     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

Tim Nikias v2.0 wrote:
> Additionally,
> since POV-Ray is also used for animations,
> it might be a consideration to add another two
> floats. I've noticed that initial_frame also only
> returns the number from Subset-Framing. So
> perhaps it might be a good idea to add some
> constant-floats which will return the actual
> KFI and KFF values...

IIRC those values can be calculated using values of clock related
identifiers. In particular using frame_number + clock +
initial_clock/final_clock + clock_delta.

ABX

Post a reply to this message

Hm, you're right, this should be possible. I'll
see if it'll work.
Nontheless, I do think that either initial_frame and
final_frame should return the actual values of
KFI and KFF respectively, or two new constant
float-identifiers should be introduced. To me they
seem to be essential for creating animation-includes.

Anyways, at least the Docs should be changed then.
Do I have to make a note in some other newsgroup
for that, I'm not sure sure...

--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

> Tim Nikias v2.0 wrote:
> > Additionally,
> > since POV-Ray is also used for animations,
> > it might be a consideration to add another two
> > floats. I've noticed that initial_frame also only
> > returns the number from Subset-Framing. So
> > perhaps it might be a good idea to add some
> > constant-floats which will return the actual
> > KFI and KFF values...
>
> IIRC those values can be calculated using values of clock related
> identifiers. In particular using frame_number + clock +
> initial_clock/final_clock + clock_delta.
>
> ABX
>
>
>

Post a reply to this message

On Sun, 6 Apr 2003 02:37:03 +0200, "Tim Nikias v2.0" <tim### [at] gmxde> wrote:
> two new constant
> float-identifiers should be introduced. To me they
> seem to be essential for creating animation-includes.

Isn't that you who said "I'm the kind of guy who wants to script his
own stuff"? It can be made via script, and with this thread it is already
documented for future references. Do not forget to post the code for less
experienced users.

ABX

Post a reply to this message

:-) Okay okay. I'll post some code shortly.

--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

> > two new constant
> > float-identifiers should be introduced. To me they
> > seem to be essential for creating animation-includes.
>
> Isn't that you who said "I'm the kind of guy who wants to script his
> own stuff"? It can be made via script, and with this thread it is already
> documented for future references. Do not forget to post the code for less
> experienced users.
>
> ABX

Post a reply to this message

Here's the code. It'll return the amount of frames of the
animation and set a variable if or if not the animation is cyclic.

#if ((final_frame-initial_frame)*clock_delta>=(final_clock-initial_clock))
 #declare Total_Frames=1/clock_delta+1;
 #declare Cyclic_Animation=off;
#else
 #declare Total_Frames=1/clock_delta;
 #declare Cyclic_Animation=on;
#end

Regards,
Tim

--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

> :-) Okay okay. I'll post some code shortly.
>
> --
> Tim Nikias v2.0
> Homepage: http://www.digitaltwilight.de/no_lights
> Email: Tim### [at] gmxde
>
> > > two new constant
> > > float-identifiers should be introduced. To me they
> > > seem to be essential for creating animation-includes.
> >
> > Isn't that you who said "I'm the kind of guy who wants to script his
> > own stuff"? It can be made via script, and with this thread it is
already
> > documented for future references. Do not forget to post the code for
less
> > experienced users.
> >
> > ABX
>
>

Post a reply to this message

On Wed, 9 Apr 2003 13:57:14 +0200, "Tim Nikias v2.0" <tim### [at] gmxde> wrote:
> #if ((final_frame-initial_frame)*clock_delta>=(final_clock-initial_clock))
>  #declare Total_Frames=1/clock_delta+1;
>  #declare Cyclic_Animation=off;
> #else
>  #declare Total_Frames=1/clock_delta;
>  #declare Cyclic_Animation=on;
> #end

Are you sure ?

This seems only valid when ( final_clock - initial_clock ) = 1

ABX

Post a reply to this message