Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MovieClip animation timing => fps #237

Closed
Makio64 opened this issue Jul 30, 2013 · 3 comments
Closed

MovieClip animation timing => fps #237

Makio64 opened this issue Jul 30, 2013 · 3 comments

Comments

@Makio64
Copy link

@Makio64 Makio64 commented Jul 30, 2013

Hello,

Impossible to control my timing on a 3 frame animation witch I want slow ( 4fps : 4/60 ) with animationSpeed property, when I setup it to : 4/60 it play super fast.

Also I dont find in the doc the normal fps, we only have an animationSpeed property on 1.

When I anim I need something like myanim.fps=12 and the doc need to be a bit more clear : default value 1 & 1 == 60fps.

Thanks

@englercj
Copy link
Member

@englercj englercj commented Jul 30, 2013

The animation speed is in frames per animation frame, the default is 1 which will display one frame of your animation every frame of the application (so if it is set to one, you will flip through framerate frames in one second). By setting it to 3/60 you are saying you want framerate*(3/60) frames in 1 second. With a framerate of 60 that works out to be 3 frames every second. Does that help clear up what you are looking for?

@englercj
Copy link
Member

@englercj englercj commented Aug 19, 2013

Closing for now due to lack of activity

@lock
Copy link

@lock lock bot commented Feb 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants