I spent most of today researching the frame verbs. I found that SkipToFrame() and MoveToFrame() do almost the same thing. The only difference I could find is that SkipToFrame() does not update the current frame (retrieved with GetCurFrame()) of an object when it arrives at its destination.

Are there any other known differences?

Another thing: I saw in some custom cogs that you can tell an object to move to the next frame without waiting for it to reach the first. And I suppose that once it reaches the first frame, the object would go to the next.

Is there some rule for stacking move commands like that? I did some experimenting with door cogs, and I couldn't get the door to accept two move commands at once.

------------------
Incognito

One of my very early levels released had a troop transport move around a canyon using several frames. Here's what I found...

MoveToFrame() would make the transport move to the desired frame, via all middle frames from the current frame. ie: current frame is 3, desired frame is 10, would go 3,4,5,6,7,8,9,10

SkipToFrame() would make the transport move directly to the desired frame regardless of what the current frame is. ie: current frame is 3, desired frame is 10, would go, 3,10.

Raynar


------------------
... the Jedi I admire the most, met up with Darth Maul, now he's toast ...
Rbots - a project to develop a working Bot for Jedi Knight... download the latest development version here

The first trooptran cog I made (almost 2 years ago...), I made the mistake of parsing evry move. I finally realized that all I needed was 1 move command. I think most n00b coggers make that mistake.

------------------
Success is the inverse relationship between effort, gain, and loss.

Ahh. Thanks alot Raynar

------------------
Incognito