Re: NSTimer causes events to be lost
Re: NSTimer causes events to be lost
- Subject: Re: NSTimer causes events to be lost
- From: John Pattenden <email@hidden>
- Date: Mon, 21 Mar 2005 13:13:11 -0500
I'm not running at 500fps, to get the animation to run at 30fps the
rendering code needs to be called about 500 times a second - then Cocoa
starts to lose its own events..
John Pattenden
ScreenTime Media
On Mar 18, 2005, at 10:51 PM, Shaun Wexler wrote:
On Mar 18, 2005, at 2:00 PM, John Brownlow wrote:
why are you running an animation at 500 fps (disclaimer - if indeed
that's what you're doing) ?
Best to render between frames, then swap during VBL. No faster than
max refresh. Dropping "occasional" frames is okay and usually will
not be noticed. If he's running a NSTimer, it won't fire any faster
than the NSRunLoop can service it, ie once every iteration. There's a
lot of overhead in that approach. If/when you have access to Tiger,
check out the VBL callback available in CoreVideo... ;)
The human eye pretty much craps out at 60fps and 25fps is TV
quality...
I take issue with that last statement. I think that the phosphors in
displays crap out, not the eye. Personally I can tell the difference
between 60 fps and 75 fps quite easily, and 100 fps looks noticeably
better to me as well. I've never seen higher than 120 fps, but at
that rate it really looks liquid. Maybe it helps to be fully
synchronized and frame-accurate as well? :-}
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden