![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Mike the Elder" wrote:
> Question: Can entrants ask for "+KC" (turn on cyclical animation)
> in the .ini file?
I too would be interested in this. Cyclic animations are always a nice way
to extend the viewability of a short animation with just 100 frames (= 3-4
seconds).
Also, it makes the timing of the frames more simple. For example, with +kc
on, the frames would fall on clock values 0, 0.01, 0.02, 0.03, 0.04 etc.
With +kc off, they would fall on 0, 0.0101010101, 0.0202020202,
0.0303030303, 0.0404040404 etc. It makes it more difficult, if you want some
specific event to happen right in one frame and not between two frames.
Rune
--
http://runevision.com
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Question: Can entrants ask for "+KC" (turn on cyclical animation) in the .ini file?
The main problem I have with it relates to how many other ini flags I might be
asked to support if I add this one (even though it might seem like a perfectly
sensible one for an animation competition).
How expensive is it to create a periodic clock yourself, I haven't thought too
much about this ...
(1-cos(clock*2*pi))/2
gives a periodic clock albeit nonlinear.
I'm inclined not to allow custom ini files (sorry), remember you have 512 bytes,
twice what previous competitions were allowed. What luxury. :-)
-------------------------------------
P a u l B o u r k e
http://local.wasp.uwa.edu.au/~pbourke/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Paul Bourke <pau### [at] uwa edu au> wrote:
> How expensive is it to create a periodic clock yourself, I haven't thought too
> much about this ...
> (1-cos(clock*2*pi))/2
> gives a periodic clock albeit nonlinear.
The last value is the same as the first value there, which is exactly
what +KC remedies.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Paul Bourke" <pau### [at] uwa edu au> wrote:
> > Question: Can entrants ask for "+KC" (turn on cyclical animation) in the .ini
file?
> The main problem I have with it relates to how many other ini flags I might be
> asked to support if I add this one (even though it might seem like a perfectly
> sensible one for an animation competition)...
> I'm inclined not to allow custom ini files (sorry)...
Thank you for taking the time to consider and reply to my request. I can see
your point about wanting to head off a proliferation of special requests from
the start. It turns out, in my case, (now that I've changed my mind about what
I'm going to do YET again) that all I need to do is replace "360" with "356.4"
at a measly cost of two characters. (For anyone working with radians, "6.22" in
place of "pi*2" is accurate to four places.) I wish Rune good fortune in finding
a concise solution to the problem of targeting a specific event to a specific
frame.
Best Regards,
-Mike C.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike the Elder nous apporta ses lumieres en ce 2007/11/29 13:03:
> "Paul Bourke" <pau### [at] uwa edu au> wrote:
> ....
>> Please forward any comments, complaints, suggestions either through this forum
> ....
> Question: Can entrants ask for "+KC" (turn on cyclical animation) in the .ini
> file? It's possible, of course, to adjust the calculations in the code itself,
> but that seems rather a Rube Goldberg approach.
>
> Thanks in advance for your reply.
>
> Regards,
> -Mike C.
>
The .ini file can be changed to always include +kc.
It make cyclical animations easier, and don't cause much change for non-cyclical
ones.
Just a suggestion.
--
Alain
-------------------------------------------------
Please hassle me, I thrive on stress.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Alain" wrote:
> The .ini file can be changed to always include +kc.
> It make cyclical animations easier, and don't cause much change for
> non-cyclical ones.
> Just a suggestion.
That was my thought too. That one frame in the end rarely makes an important
difference in non-cyclic animations, but it does indeed in cyclic ones.
In fact, the way frames are distributed in POV-Ray in non-cyclic animations
is odd at best. If you want your animation to last exactly one second with
30 frames per second, and you set +kff30, then each frame will in fact cover
1/29 second rather than 1/30.
I don't even know if I'll enter the competition though, so my arguments
perhaps shouldn't weight so much. It's just that I have an opinion about the
frame distributions that is based on my experience with animations. :)
Rune
--
http://runevision.com
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |