This is continuation of the other issue that I've been having with buttons not being recognized on my Warthog HOTAS. I've narrowed it down quite a bit. If I set the simple button press to repeat every 25 msecs, the button on the HOTAS is no longer recognized by SpadNext. If I make it a single press again, it is recognized. I have not been able to get any support, so if anyone has any ideas what could be happening I would sure appreciate the help!
Thanks
Current SPAD.neXt Release: 0.9.12.123
This forum has closed. Please join our Discord Community.
SPAD.neXt online services are no longer available for SPAD.neXt Versions < 0.9.11.5
25 msec repeater problem
Forum rules
If you have technical Problem, please open a ticket: https://www.spadnext.com/discover/how-to/get-help.html
Do NOT hijack other people threads, until you have exactly the same problem!
If you have technical Problem, please open a ticket: https://www.spadnext.com/discover/how-to/get-help.html
Do NOT hijack other people threads, until you have exactly the same problem!
- thedazman
- Betatester
- Posts: 1808
- Joined: 28 Mar 2015, 10:47
- Location: United Kingdom
- Contact:
- Status: Offline
Re: 25 msec repeater problem
I really wouldn’t recommend repeating button press every 25ms you’ll just flood the sim with 40 commands a second and then everything will just start to lag.
Shouldn’t cause the issue you are having but would keep repeats to tour bare minimum
Daz
Shouldn’t cause the issue you are having but would keep repeats to tour bare minimum
Daz
- c0nnex
- Site Admin
- Posts: 5469
- Joined: 10 Mar 2015, 21:52
- Location: Munich, Germany
- Contact:
- Status: Offline
Re: 25 msec repeater problem
What Do you mean by "not recognized"?
If it just does not light up in the UI, that does not mean it is not recognized, it just means it maybe toggled to fast for the UI to show it at all. UI has lowest priority.
To check if the button press is recognized (and repeated) use the datamonitor and monitor the button variable.
If it just does not light up in the UI, that does not mean it is not recognized, it just means it maybe toggled to fast for the UI to show it at all. UI has lowest priority.
To check if the button press is recognized (and repeated) use the datamonitor and monitor the button variable.