Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: DB9 joystick input via GPIOs #112

Closed
sajattack opened this issue Sep 13, 2019 · 5 comments
Closed

Feature request: DB9 joystick input via GPIOs #112

sajattack opened this issue Sep 13, 2019 · 5 comments

Comments

@sajattack
Copy link
Member

@sajattack sajattack commented Sep 13, 2019

There are so many GPIOs on DE10 Nano, surely we can spare 9 (or less) for low-latency retro joystick input?

@sorgelig
Copy link
Member

@sorgelig sorgelig commented Sep 13, 2019

There are no confirmed input lags. USB input lag for joysticks is usually 2-5ms while retro consoles query the joysticks once per frame, i.e. once per 16-20ms.
Input lag is commercial myth.

P.S.: DB9 Atari style joystick have 2 buttons max which is not enough for MiSTer.

@sorgelig sorgelig closed this Sep 13, 2019
@sajattack
Copy link
Member Author

@sajattack sajattack commented Sep 13, 2019

Ok, maybe lag was the wrong way to frame the problem, wouldn't it still be good to support classic joysticks?

@hmusta
Copy link

@hmusta hmusta commented Sep 13, 2019

Some retro consoles (such as the NES) may poll joysticks more than once per frame:
https://wiki.nesdev.com/w/index.php/Controller_reading_code#DPCM_Safety_using_Repeated_Reads

@sorgelig
Copy link
Member

@sorgelig sorgelig commented Sep 13, 2019

There are many USB converters for classic joysticks. So they are basically supported already.

@sorgelig
Copy link
Member

@sorgelig sorgelig commented Sep 13, 2019

Some retro consoles (such as the NES) may poll joysticks more than once per frame:
https://wiki.nesdev.com/w/index.php/Controller_reading_code#DPCM_Safety_using_Repeated_Reads

MiSTer has no such glitch as original joystick. And this trick is basically just to get the same - get the joystick data once per frame. Core can query the joystick data as fast as it wants - it won't make it slower or other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants