9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] wtb: usb gamepad that works reliably with joy(1)
Date: Mon, 05 Feb 2024 21:40:17 +0100	[thread overview]
Message-ID: <D12E81C05EB03F3002585B27CEC79A7B@wopr.sciops.net> (raw)
In-Reply-To: <CC48BB4E20B1046BC5897CEE5759A079@gaff.inri.net>

On Sun Feb  4 23:57:05 +0100 2024, sl@stanleylieber.com wrote:
> logitech dual action and ps3 controller have acted sketchy, frequently
> babbling and crashing the whole pipeline.  sucks.
> 
> what controllers have you used, and which ones work best?
> 
> sl

So far only the most basic snes-style usb controllers I have have
worked consistently well.  I have a "Buffalo classic usb gamepad"
which works, including the turbo function, and I assembled this board
[1] except put snes and nes controller ports on it so i can just plug
in a real one and not destroy it.  These all probably use more or less
the same chips and will just work.  ps2 dualshock also works perfectly
(incl. analog mode) but with only one of two usb adaptors I have, the
other one mangles button events making it unusable.  The usb
controller of THEC64 [2] also surprisingly works fine.

I've tried xbox360, multiple nintendo switch usb controllers, 8bitdo
sn30pro, and get nothing; these would require more driver work.
There's a program for first gen xbox controllers in mischief's contrib
which iirc he got working.

For joy(1) et al I have convenience scripts which handle autoresizing
the window, enabling sound if possible, storing per-user saves etc.,
as others probably do too, but these are even more elements in the
pipeline, what exactly do you see happening?  Perhaps we could try to
make it more resilient.

Cheers,
qwx

[1] https://www.instructables.com/USB-SNES-Controller/
[2] https://retrogames.biz/products/thec64/

  parent reply	other threads:[~2024-02-05 20:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 22:57 sl
2024-02-05 18:58 ` mkf9
2024-02-05 20:40 ` qwx [this message]
2024-02-05 20:49   ` Kurt H Maier
2024-02-05 21:05     ` qwx
2024-02-10  4:15   ` sl
2024-02-10  5:19     ` qwx
2024-02-10  5:24       ` Stanley Lieber
2024-02-10  6:12         ` qwx
2024-02-16 16:43       ` sl
2024-02-16 16:46         ` sl
2024-02-16 17:10         ` qwx
2024-02-16 17:34           ` sl
2024-02-16 18:01             ` qwx
2024-02-16 23:40               ` sl
2024-02-17  0:55                 ` qwx
2024-02-17  1:33                   ` sl
2024-02-17  2:37                     ` Sigrid Solveig Haflínudóttir
2024-02-16 18:02           ` qwx

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D12E81C05EB03F3002585B27CEC79A7B@wopr.sciops.net \
    --to=qwx@sciops.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).