Re: NSTimer causes events to be lost
Re: NSTimer causes events to be lost
- Subject: Re: NSTimer causes events to be lost
- From: Shaun Wexler <email@hidden>
- Date: Fri, 18 Mar 2005 19:51:06 -0800
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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