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.
You must log in or # to comment.
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.
The project equivalent of your mum sticking your drawings to the fridge 😊
Hey, you tried, most wouldn’t bother. You’re the top 1% of humans in that way
Whether it works or not, this looks incredibly fun! That’s a win in my book.
How much are you doing with “rolling your own” vs using off the shelf solutions? For example if you are deep into rolling your own which Bluetooth profile are you using?
So in this case it’s my own code to read the state of the controller and using the ble-gamepad library, which uses NimBLE under the hood. There could be some optimizations but getting to be under 10ms probably is going to use a lot of time I could just be playing games.
So you suspect the latency (enough of it anyway) is introduced in your translation code? I absolutely understand not wanting to go to the nth degree for optimization when this is a hobby project. Could you throw hardware at it? Not all ESP32 run at the same speed. Perhaps buy an oversized one that will execute your underperforming code faster?
There probably could be some optimization in the translation, such as passing the controller object as a reference when checking the state of the buttons, rather than doing two loops to read the state and act on it. But I doubt that is the source of the largest latency since this is compiled to run at 240mhz (I did some additional testing at 80 as well, about the same results). I’m using a d1 mini off alliexpress so not the highest quality but I wouldn’t expect a huge performance hit.
Where do you think the (the majority of the) latency is being introduced?
Without more testing it’s hard to say. I don’t want say it’s the hardware without proof, but would require a much deeper dive into esp32 and c++ than I want to do right now.
18.53ms is imperceptible to humans.
I think the concern is the stack up you get in latency between the controller, the computer, and the monitor.
That’s a valid concern that I didn’t consider.
I can absolutely notice a frame of lag at 60Hz. Good way to compare side-by-side is by using an emulator with run-ahead mode.
I read that people who play a lot of FPV shooters have higher than average reaction and perception time. 18ms is ridiculously fast though, I’d be surprised if someone could consciously register it. I know gaming monitors market latency in the 1.5ms range, so maybe elite gamers can perceive the difference. Someone else pointed out that there are concerns over latency stacking between all of the devices, and that’s a really valid point.
18ms is okay but for a lot of retro content, it’s running 60fps. That means it’s one frame is 50/3ms, aka 16.6666ms. Sub 1 frame is good enough, 18ms is not in my opinion.
I don’t play shooters, but I love both 2D and 3D platformers, where you can absolutely notice a difference.