This was my attempt to create a a SNES to Bluetooth adapter. It works but the average latency was 18.35ms, which I think is too much to be considered a good controller.
this post was submitted on 12 Mar 2024
173 points (99.4% liked)
RetroGaming
19129 readers
188 users here now
Vintage gaming community.
Rules:
- Be kind.
- No spam or soliciting for money.
- No racism or other bigotry allowed.
- Obviously nothing illegal.
If you see these please report them.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If anyone else was wondering, I found this neat data table of controller latencies to compare:
https://rpubs.com/misteraddons/inputlatency
It looks like 18.35ms is not really among the best, but there are still lots of products in that range.
I dunno if I'd say your project didn't work out... Maybe more like you succeeded but still have work to do. Do you think you'll try swapping the Bluetooth for a 2.4Ghz module or something and see if that performs better?
I use an 8bitdo sn30 pro. Apparently I haven't been using a good controller. Fooled me!
I wouldn't call that controller bad, just not optimal. For this, I would want to have it be under 10ms to publish the code and instructions.
I've had a lot of connection issues with that model
How so? It disconnects? Or won't connect to start?
Both, and I was literally right next to my phone
What phone do you have?
Samsung A53
Hmm I was thinking maybe an old phone but that's not that old.
Try charging while connecting. I've found that a low battery often seems like poor connection quality. The way it gives up when it can't connect is very similar to just the battery dying.
I have two of em-- They're pretty good! Definitely not perceptibly laggy or anything, at least to me.
Probably just outed myself as a casual.
Casuals unite! Fuck it I'm just trying to have fun lol!
It definitely could but the idea was to use only an esp32 rather than incorporating additional hardware.
Yeah, I get that. Do you have any sense of whether that's a limitation of the ESP32, or with your implementation?
It's really hard to judge without additional testing, I'm always more likely to blame my code than hardware. My guess would be something in the stack, be it my code or the library that puts it above a frame but that kind of investigation is more than I want a hobby project to be.
I think the esp32 maximum throughput is 700 kbps, so you might be able to get a better performance.
I don't have much experience with the esp32, but the first thing I would do is just a spoof program that sends simulated inputs, and see how's the latency without any other functionalities.
That will give you a good idea if the problem is your code or the stack (its not infaillible though).
Yeah one approach is that BLE-Gamepad library supports gpio pins as button inputs, so in theory I could get a baseline of what the Bluetooth stack of the library is by soldering the jst connector to connect the Arduino (that triggers the button presses and measures the result from the Mister SNAC port).
Otherwise I'd basically have to develop my own controller code to port onto various Bluetooth stacks for testing, but that seems like more than I want to do right now.