I'm using the wooting60he avr, and when using the gamepad mode it's locked to 250hz. Is it an issue with my configuration, or is the support locked to 250? I'm using the xinput option, and using xpad on linux if that's relevant. If it's locked to 250hz would there be any possibily of 1k hz polling rate for gamepad inputs? I've got a gamesir g7he which can do 1k hz polling rate on my system.
#gamepad polling rate past 250hz?
wanton ibex
knotty token
its locked to 250hz cause the original 360 controllers do the same
i think we had some internal discussion on raising this but thats about it
wanton ibex
Thanks for the answer
glad urchin
its locked to 250hz cause the original 360 controllers do the same
Is it on all boards?
knotty token
yes
remote copper
👀
lusty crane
Hello @wanton ibex, we just released test build 2.11.0-beta.0+crank-gamepad on the beta version of Wootility which cranks up the gamepad polling rate as high as possible. For your 60HE AVR, this means 1000Hz.
Please try it out and let us know how it goes!
- Use this link https://beta.wootility.io/?test-builds=true (this URL has Test builds enabled)
- Click on "Settings"
- Select "Updates"
- Select "Your keyboard"
- Press "Get Test Firmware"
- Press "Select Test Build"
- Select
2.11.0-beta.0+crank-gamepad
wanton ibex
It still seems to be 250hz unless I messed up something. Wootility shows update available, but I'm pretty sure it'd change the firmware to the non 1000hz branch.
lusty crane
@wanton ibex try 2.11.0-beta.1+crank-gamepad, mistakenly the increased polling rate only applied to ARM keyboards, my bad
wanton ibex
It works now. Thank you
cloud fiber
are you getting the full rate of 1000 with the newest patch ?
i am getting around 500
knotty token
around 500? thats not a polling rate. best to share screenshots or such
cloud fiber
that is due to how i am measuring. i was building a joystick tester and to test the rate quick and dirty i am just opening another thread that logs the received joystick data 2000 times per second to then check how frequently the data changed.
so how inaccurate my result is depends on how consistent i can provide movements that also need to exceed a speed that depends on the resolution of the adc. works out to less than 2% difference to the actual rate that i am logging on a joystick micro controller for a 16 bit axis but might run into the speed limit here.
that is why i did a quick sanity check using another program that also lead to around 500hz but i havent looked at what it is actually doing https://github.com/cakama3a/Polling
lusty crane
that is due to how i am measuring. i was building a joystick tester and to test ...
Hey not sure how you're logging exactly and what your exact keyboard model is. I haven't tested stick movement personally but I can confirm the buttons are definitely sending at full 1000Hz on 60HE+
Might update keyboard inspector at some point to add support for analog values like these so we can get to the bottom of it much easier
lusty crane
It works now. Thank you
Hey can you give us some feedback, how has using the test build been like for you? Does everything function as expected?
wanton ibex
It works perfectly in my experience. And its polling at 1000hz based of evhz reporting. Which also accurately reports my other devices polling rate. Thank you!
wanton ibex
Just wondering if the cranked polling rate will end up in the main branch? Cause it's 250hz in 5.1.0-beta3.
lusty crane
Just wondering if the cranked polling rate will end up in the main branch? Cause...
We're a little blocked up with some major updates, haven't been putting much focus on the smaller changes. Have you been using the test build all this time, noticed any regressions?
wanton ibex
We're a little blocked up with some major updates, haven't been putting much foc...
I have been using that test build with 0 issues
wanton ibex
Just wondering if the cranked polling rate will end up in the main branch? Cause...
It's still 250hz in the latest firmware release of 2.11.0
lusty crane
It's still 250hz in the latest firmware release of 2.11.0
wootility 5.2 beta we just released has a lot of changes happening at once so we opted not to include gamepad polling rate increase, but I'll personally make sure it reaches mainline wootility by the end of the year
lusty crane
hey @wanton ibex Wootility beta 5.3 with firmware 2.13.0-beta.7 contains both the USB polling rate increase from the test build and we also increased the resolution on the stick axes and triggers we report. Everything applies to AVR boards as well. Could you try out the latest beta and let me know how it feels for you?