Encoder overrun

[Bigjezzarino]

Hey proud owner of a new STECS and Gladiator here - thanks VKB

Just wondering if it’s possible to change the behaviour of the encoder(s) and make them stop sending pulses when I stop turning them.

I’ve got one assigned to the heading bug in MSFS and if I twist the knob quickly, it keeps pulsing long after the twisting has stopped.

It does this in vkbdevcfg too. I’ve tried assigning them to a new axis but it’s the same behaviour.

I believe what is happening is since the pulse is 50ms, and if I twist the knob quickly it might whizz past 20 indents, so it sends 20x 50ms pulses.

Trouble is, it keeps sending these pulses long after I’ve finished twisting.

I appreciate that with some bindings it might be preferred to have 1:1 indent to pulse, but in my situation, if I twist it fast, and stop twisting when the heading bug hits my heading, it keeps going and overshoots.

I have tried a shorter pulse, but they aren’t recognised 100% of the time. Any ideas? Ideally I’d love a way to set some kind of logic like this: (send a few pulses, and if encoder is still spinning fast, keep pulse on until encoder stops spinning)

[DeadWalking]

Hmmm. I am not sure what to try to combat that.
The only encoder I have to test is on my EVO, and it does not free spin in a way that I notice the issue.

[virgo47]

This is my issue as well. With STECS, it's easy to turn the encoder faster than it sends the info out. It is clearly visible with the config software as well, when I poll the buttons. It can run for seconds after I stop turning the encoder. I don't mind "lost" events that much, but I don't like it having action after I stop turning it. Is there an option to limit the buffer of whatever causes it?