RE: [Algorithms] FPS Questions

[Tom F. <to...@mu...>]

Saccade - that was it - ta.

Except that if the graphics move fast, your eyes _will_ follow them (and
then "flick" back to the other side of the screen, inducing saccade). If
they don't, that's a sign of neurological problems - it's one of the
low-level reflexes that keep your eyes tracking moving objects, and it's
very hard to override without defocussing your eyes. The things you learn
when both parents are medics... :-)

Tom Forsyth - Muckyfoot bloke.
Whizzing and pasting and pooting through the day.

> -----Original Message-----
> From: Stephen J Baker [mailto:sj...@li...]
> Sent: 01 August 2000 17:17
> To: gda...@li...
> Subject: RE: [Algorithms] FPS Questions
> 
> 
> On Mon, 31 Jul 2000, Tom Forsyth wrote:
> 
> > Lower latency - that's what FPS players from higher fps 
> (excuse the pun).
> > They also say that you can spin faster and not have any 
> gaps in your visual
> > coverage of a room. I'll have to trust them on that - I 
> have no problems
> > scanning a room quickly on my fairly average setup, which 
> is probably going
> > at around 25-30Hz. If you spin too fast, your optical 
> shutters kick in (I
> > used to know what they were called - anyone?
> 
> Saccade.
> 
> > - they stop you getting confused by rapid head movements).
> 
> But I don't think that spinning the graphics around fast will
> induce a saccade - your eyes have to move to make that happen.
> 
> Steve Baker                      (817)619-2657 (Vox/Vox-Mail)
> L3Com/Link Simulation & Training (817)619-2466 (Fax)
> Work: sj...@li...           http://www.link.com
> Home: sjb...@ai...       http://web2.airmail.net/sjbaker1
> 
> 
> _______________________________________________
> GDAlgorithms-list mailing list
> GDA...@li...
> http://lists.sourceforge.net/mailman/listinfo/gdalgorithms-list
>