Delay & latency of button repetition

Hi all,

anyone know where is the setting to change the delay of the button repetition on xbox pad ?
Example, for throttles increase / decrease, you have to push a button (B & A in my case).
To brutally decrease throttle you have to push (=1 step of decrease) and wait something like 0.8 sec and see continuous decrease until you stop pushing the button.
This delay is clearly too long in a landing sequence for example.

As in windows you can set up this setting for keyboard repetition, I hope in MSFS there is too.
But to be honest, seeing they take 4 years to fix active pause, I think it could take forever to have such an option.
Anyway, have you any idea in this way ?

You could probably be faster if you developed your ‘Nintendo thumb’ skills, i.e. ‘button mashing.’
I think the best gamers can probably do a button press every 0.1 seconds.

Yeah I used to be one of them but, again, during a landing sequence, that’s not recommended :slight_smile:

And a kit joystick + throttles + rudder is definitively too expensive for my use of MSFS ; and just don’t want 10kg of stuff on my desk >.<

No, there must be a way to set up this ■■■■ option.

For those who knows ; using trim on the Comanche is exactly what I’m looking for, smooth and continue progress of the course. They even thought about an acceleration if you stay pushed. A2A, Brillant.
Think about if A2A made MSFS 


Some external software should help here - like Axis and Ohs or FSUIPC etc - but perhaps a sledgehammer to crack this particular nut, although as it brings many other features it might be worth having a look at.

Have you any link please, cause I just can’t find any of these (except for FSUIPC but indeed, that’s a big, big hammer)

Hehe yeah it would be amazing. But would probably take them about 37 years :slight_smile:

1 Like

I didn’t see in your original post a reason that it’s not recommended. Can you explain?

What you’re trying to accomplish is quicker throttle response, right? Why would it matter unless the button ‘mashing’ somehow buffers the key presses, and you suddenly and unexpectedly find you’ve hit the button too many times, and hit Vs0.

My office computer has an issue where the USB controller gets wonky after it’s been idle for a while. I try to type ‘Wonky’ and end up typing ‘Wonnnnnnnkkkkkkkkkkkky’ (“C’mon ‘K’ key
you can do it!”) due to the keystroke buffering. I have to reboot the computer to clear it up.

Axis and Ohs is here:

I didn’t see in your original post a reason that it’s not recommended. Can you explain?

I think for the double enders for example, you can tap something like 50 times to get from zero, to 100% throttles. But for some reason, sometimes it’s faster ; I think that’s when my pad disconnect (because I’m AFK for example), step become larger.
So with this response, even if you don’t use all the course, consider tapping 20 times in a way, and reverse, you’re totally out of response time for bush landing in strong conditions. So I’m using long push to auto tap very fast and stop “somewhere” I intend to (approximatively).
If I was able to configure all of this, I think I could be more efficient.

But it’s true that in other aircraft, you just have to tap 15-20 times to get 100%, and so you could be in the delay.

If you have the Comanche (A2A), you could see the trim response and get what I’m looking for.

My office computer has an issue where the USB controller gets wonky after it’s been idle for a while

Maybe it’s something about the BUS shut off (economy mode) during a time without use, it’s active by default on W10 I think ?

I hope you find your answer. I use a Bravo TQ.

I turn ‘USB Selective Suspend’ in the power plan OFF on all my computers.
It’s something else, but thanks for the suggestion.