By making each frame of your animation as an explicit and separate
scene, you have more or less removed the possibility of changing the
amount of frames in your animation.

  Animations are usually made in a more abstract way in POV-Ray than
creating explicit individual scenes for each frame. This is usually
made with one scene file using the 'clock' variable.

  For example, suppose that you want to rotate a box 90 degrees around
the y axis during the animation.
  Your way would be to create a certain amount (eg. 30) .inc files, each
one of them containing a box rotated by a fixed amount. The problem with
this is, as said, that if you want to change the number of frames you have
a problem.

  The more abstract way of doing the same thing in POV-Ray is to
make just *one* scene using the 'clock' variable, for example like this:

camera { whatever }
// other scene settings here

box
{ <-1,-1,-1>, <1,1,1>
  pigment { whatever }
  rotate <0, 90*clock, 0>
}

  Then you can render for example 30 frames from this scene by using
the parameter "+kff30" (either in the options field at the top of
WinPOV or in the command line if you are using a command-line version).
  You will get 30 frames with the box rotating 90 degrees.

  The great advantage of this is, of course, that if don't want 30
frames but for example 40, you just change the option to "+kff40"
and POV-Ray will now calculate 40 frames instead of 30 (the box
still rotates 90 degrees during those 40 frames).

  The level of abstraction provided by the 'clock' variable makes it
easy to change the amount of frames the animation takes to complete.

-- 
#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