Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Game Controller Tester

Test any input device including gamepad, haptic, vibration, mouse, keyboard, touch screen, sensors · By POW Games

Polling Rate Bug and Custom Sample Count Suggestion

A topic by CODORÇO created 5 days ago Views: 13 Replies: 1
Viewing posts 1 to 2
(+1)

Hello friend, it's me again! I really like your program and use it a lot when making videos for my channel.

I noticed a bug on the Polling Rate screen: if you press the reset button and do not wait a few seconds before starting to spin the controller's analog stick, the final polling rate value increases significantly.

Also, I noticed that the number of Samples is currently set to 500 in the latest version. When testing 1000Hz controllers, the test ends after barely two spins of the analog stick, which is very fast. Would it be possible to add a custom option for the user to choose between 500, 1000, or 2000 samples for the test? That would be very useful.

If possible, I would love to see a test to analyze the analog stick resolution someday. Many current controllers are coming with very high-resolution analog sticks, and some of my channel subscribers are asking me for tests of this kind.

There is a software called "Stick Analyzer" on GitHub that does this, but it would be much more practical to use a single piece of software for all tests, and your testing software has a much friendlier interface.

I really appreciate your work! I bought the APK on Android and the version for Windows here. Congratulations on developing it! Cheers.

This message was translated by AI, so there may be some errors.
Developer (1 edit)

Thanks for your continued support CODORÇO. 

I see the bug. The polling rate (Hz = per second) is calculated like this: samples / (time - nextSecond) / 1 second. So, it needs a full second to pass before the calculation is accurate. I'll fix it somehow - good catch!

Total sample changer = very good idea. 1000Hz gamepad = wow! I hadn't considered this; my gamepads are all very low Hz. 

Analogue resolution is also a very good idea. I'm wondering how to calculate this. Currently values come in from 0 to 32767. Do you think recording the minimum distance between current and previous readouts would be enough? I'll take a look at Stick Analyzer.

I'll get to work on this right now, you should see these things in the next update in a few days.