Xinput control test2/29/2024 ![]() ![]() If I were a controller company, I’d test in the exact same way and be confident in the results. I imagine if I was still in my NYC apartment, the results would be different…but these tests are about the controller, not the environment. It’s also important to note that the controller was about two feet away from the receiver (the same exact distance for each test) and I’m not in an area with a lot of wireless interference. While I’m sure most of us wouldn’t mind spending $20 to upgrade if there was a lower latency solution available, it’s nice to know existing solutions are totally fine. ![]() The results were within a half millisecond of each other, with the lowest total reading being 2.81ms and the highest 17.78ms, with the average being 8.5ms – About half a frame.Īs a side-note, it was pretty interesting that the BT4.2 receiver performed basically the same as the BT5.0’s. I was really curious to see if different bluetooth adapters showed different results, so I ran these 1000-press tests on a combo adapter, l ong-range BT5.0 adapter and standard range BT5.0 adapter Luckily, the button mappings retained from before I installed the tester, so I only needed to re-sync to the new adapter, not re-map. I ran the test for 1000 presses once again and saved the results. ![]() I then moved to bluetooth and also had to set it to XInput mode for it to be detected. The lowest reading was 0.34ms and the highest was 5.84ms, averaging out to 3.3ms. I then ran the test twice, both for 1000 presses each. Maybe I messed this up and you can just connect the controller via USB C-A cable without XInput mode, but that’s what worked for me. The controller was only detected when placed in XInput mode, by holding sync and B white powering on. I started with USB, as that was the easiest. This will work with any connection method – Basically, just connect your controller to MiSTer first, map the buttons in the main area, as well as the lag test core, then install the kit. And then you load a MiSTer core from lemonici that triggers the button press, then measures the time from when the button is pressed, to when it’s detected in the core. The Arduino connects to a PC running putty. I used the Arduino / SNAC method of testing, that I’d previously demo’d in two livestreams (below) with Louis from Zezretro The custom board connected to the 0.0ms latency SNAC port, as well as a button on the controller and an Arduino. But I’ll explain what I did and why I’m so confident in the results… While my results are 100% accurate, there might be other modes that perform differently, better connection methods, etc. I’m just a low-lag enthusiast, trying my best to help. More info after the links:įirst, it’s important to note I’m not a controller expert. That makes this controller totally playable for everyone other than pro gamers and it paired really well with the MiSTer’s upcoming N64 core! I didn’t test it for its intended use (Nintendo Switch Online), as I don’t subscribe to that, but at this price point, it’ll be a good choice for a wireless MiSTer controller, where the button layout makes sense. After purchasing the Bluetooth-based Brawler64 from Retro Fighters, the very first thing I did (as you can imagine) is lag test it! I used the MiSTer lag test kit I previously demo’d in livestreams and found some excellent results: The USB connection averaged 3.3ms of latency, while the Bluetooth connection averaged 8.5ms – both in XInput mode. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |