How come [self schedule:@selector(update:) interval:0.000001f] goes as fast as [self schedule:@selector(update:) interval:0.001f];
First one having 0.000001 as the time and the second one having 0.001. What's the lowest? Is this related to fps.
ccTime and schedule: how fast can it go?
(3 posts) (3 voices)-
Before the new CCDirector types you could set animation interval to something like 1/240. But DisplayLink director only supports up to 1/60 intervals now, so if you use it then 1/60 = 0.016 so your interval values go below the threshold...
Maybe with some other types of director you can still get lower than 1/60 but you need to test that or ask somebody else :)
Posted 1 year ago # -
Steve Oldmeadow
AdministratorIt depends on what type of Director you are using. If you use a DisplayLink director then it is tied to the video refresh rate which is 60Hz. Otherwise there is a lot that goes on in each iteration of the main loop which is going to limit the frame rate. Besides that, even if you could get 0.000001 it would rip through the user's battery like a hot knife through butter and seems kind of pointless when the video is only being refreshed 60 times a second.
Posted 1 year ago #
Reply
You must log in to post.