POV-Ray : Newsgroups : povray.beta-test : initial_clock / final_clock behaviour : Re: initial_clock / final_clock behaviour Server Time
29 Jul 2024 18:28:35 EDT (-0400)
  Re: initial_clock / final_clock behaviour  
From: Anders K 
Date: 21 Mar 2002 11:29:19
Message: <3c9a0a5f$1@news.povray.org>
> > But saying POV-Ray that it should only render a specific part of the
> > animation with Subset_Start/End_Frame also changes the value of
> > initial/final_clock respectively, which is not mentioned in the docs.
>
> This does _not_ change the values. [...]

You are right that it *shouldn't* change the values. The bug is that it
*does* change the values, which I can confirm. Try rendering this scene:
  #debug concat(str(initial_clock, 0, -1), "\n")
  #debug concat(str(final_clock, 0, -1), "\n")
first with +kff10, and then with +kff10 +sf4 +ef6. With +kff10, it outputs
  0.000000
  1.000000
as it should. But with +kff10 +sf4 +ef6, it outputs
  0.333333
  0.555556
which is wrong, since specifying a subset should not change initial_clock
and final_clock.

Anders

--
light_source{6#local D=#macro B(E)#macro A(D)#declare E=(E-#declare
C=mod(E D);C)/D;C#end#while(E)#if(A(8)=7)#declare D=D+2.8;#else#if(
C>2)}torus{1..2clipped_by{box{-2y}}rotate<1 0C>*90translate<D+1A(2)
*2+1#else}cylinder{0(C-v=1).2translate<D+C*A(2)A(4)#end-2 13>finish
{specular 1}pigment{rgb x}#end#end#end-8;1B(445000298)B(519053970)B
(483402386)B(1445571258)B(77778740)B(541684549)B(42677491)B(70)}


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.