Re: Joysticks typical polling freq.

From: brain_at_jbrain.com
Date: Fri, 13 Dec 2019 09:00:22 -0600
Message-ID: <74c1d2ae-7579-4c88-a777-860522447ec4_at_Spark>
I can’t add much more than a hat has all eddy been stated but I will put in this note for paddles, if someone later searches for this.   The paddles use 512 cycles to take a reading so there will be absolutely no benefit to reading more than once every 512 cycles.  I agree that’s far too often but just noting the paddle hardware does have an upper bound.

Jim
On Dec 13, 2019, 4:41 AM -0600, Mia Magnusson <mia_at_plea.se>, wrote:
> Den Thu, 12 Dec 2019 04:47:09 -0600 (CST) skrev "Ruben App."
> <ruben_at_aparici.net>:
> > How frequently would the C64 in a typical ML game would poll or would
> > be able to poll considering the game logic, music and video, the
> > Joysticks ? 250Hz, 1000Hz, faster ?
>
> Are you asking from a software or hardware developer viewpoint?
>
> I.E. do you want to make your own joystick controlled software, or do
> you want to make your own hardware that acts as a joystick?
>
> As long as the joystick input is controlling something visible on the
> screen, there probably isn't much point in polling it more often than
> each frame, at least for games that will perform some action
> continuously when a direction is held or the button is held in it's
> active position. For software that does a one time action each time the
> user moves the joystick in a direction or presses the fire button,
> there at least in theory might be reason for polling more often. Not
> sure how often a real user might be able to wiggle the joystick or
> bounce on the fire button though.
>
> The hardware itself has more or less no limit except for how often the
> CPU can read the port registers - i.e. perhaps say about 100kHz or so.
> (with a SuperCPU you might be able to read the ports at 1MHz).
>
> --
> (\_/) Copy the bunny to your mails to help
> (O.o) him achieve world domination.
> (> <) Come join the dark side.
> /_|_\ We have cookies.
>
Received on 2020-05-29 23:54:22

Archive generated by hypermail 2.3.0.