X Input Tester - Game Controller Latency Test

[nomdeplume]

Came across this small program on github while idly poking around the controller world. It allows you to perform a highly variable test using 1000, 2000, and 4000 samples to determine a few metrics related to latency by measuring your Left stick movement throughout the selected period. It took me a few tries to start getting reliable results within an acceptable margin of error.

Maybe some of you find this fun and I have no idea if the program can be used in a way that gives extremely high or low results. Which can be fun in its own right.

For the broadest results please select the 4000 Samples test.

---

8BitDo Ultimate 2C Wired (claimed 1000 Hz polling rate under lab conditions)

XBOX360 Wired (known disconnecting issues - tested for fun)

Logitech F310 Wired

 

[Solaris17]

Those outliers look like the controller missed an entire sample cycle. Synchronization issue?

 

[nomdeplume]

Those outliers look like the controller missed an entire sample cycle. Synchronization issue?

Missed there was a reply in here.

Even with suspect behaviors outside of disconnecting. Xbox controller was the most consistent across the numerous times I ran this. Was good until it wasn't.
Logitech is cheap and not really good with W11 or many other uses it has limited support in. Not one bit surprised the basic Windows driver shows issues that were present during use.

2C outliers are basically imperceptible. Whereas the other two controller are very noticeable at all times on all inputs.

---

Edit: @Solaris17

Storms kept me from pursuing sync related issues last night. USB 2.0 port I had been using makes very little noticeable difference with the two older controllers. It is widely reported 3 meter C to C runs at 2.0 speeds and both older controllers were designed for that speed. Intended to explore Type C and USB 3 comparisons after getting 3 meter C to C and A to C cables.

Blue USB 3 Type A port - Ultimate 2C

Teal USB 3 Type A port - Ultimate 2C

 

[nomdeplume]

how can i increase deadzone and stuff for a local branded xinput controller?

All this does is test latency and level of error rates.

Technically speaking the only two reliable ways to impact deadzone are beating the crap out of the control sticks or through a firmware update.

 

[avidgamer121]

All this does is test latency and level of error rates.

Technically speaking the only two reliable ways to impact deadzone are beating the crap out of the control sticks or through a firmware update.

i found out that in windows controller calibration you can change the controller dead zone, so i deleted my reply. I actually want to decrease it to make left stick more precise.