All of tht #declare stuff was in my POV file and not in the .INI file.
  In the POVRAY.INI file,i now have added:
; These animation commands work
Cyclic_Animation = true
clock = 0.027778 ; 1/36
final_frame = 18 ; final frame number (+KFIn)
final_clock = 10 ; clock value of last rendered frame (+KFn.n)

;// additional animation variables that do NOT work and cannot be set ANYWHERE
;clock_delta;       // clock step between frames
;initial_clock;     // clock value of first rendered frame (+KIn.n)
;initial_frame;     // initial frame number (+KFIn).
;clock_on;          // true if scene is rendered as an animation
; or  +KC

  Notes:
1) "initial_frame" is preset to 1 and cannot be changed.
2) If one sets clock=1, that turns animation on, but this is contrary to the
(documentary) assumption that clock goes from zero to one.
3) If one sets clock=0, animation is turned off; the *default* state which
explains why none of the samples work.

  As suggested from many others, i will first move this to my .INI file and then
try launching from it instead of the .POV file.
  The above example works for my case, but it is too eXplicit in that it fixes
program usage.

  Thanks!

  So, a _fix_ would be documentation that eXplicitly tells that in .INI file
must have these commands in it and that the .INI file be launched.
  Another _fix_ would to !remove! the incorrect verbiage concerning "variables"
that are NOT variable and CANNOT be set (and maybe are unusable).
  Oh, and put this info in the animation section of the help file so that an
idiot like me can find it!

Post a reply to this message

Robert Baer schrieb:

>   So, a _fix_ would be documentation that eXplicitly tells that in .INI file
> must have these commands in it and that the .INI file be launched.
>   Another _fix_ would to !remove! the incorrect verbiage concerning "variables"
> that are NOT variable and CANNOT be set (and maybe are unusable).
>   Oh, and put this info in the animation section of the help file so that an
> idiot like me can find it!

Yet another _fix_ would be to read the documentation carefully before 
claiming it to be broken. It does explicitly explain the concept of 
command line parameters and .INI files, and no addition to these 
explanations can prevent people from reading those added sections just 
as superficially as they do the already existing ones.

Sorry if this may sound rude, but that's how it is.

Post a reply to this message