FSS Tuning axis needs a Reverse option

[spookyneo]

Hello Frontier,

As discussed in http://forums.frontier.co.uk/showthread.php/464523-Can-we-get-analogue-controls-for-FSS-tuning , could we get a Reverse option for the FSS Tuning axis ? The FSS Absolute Tuning has a Regular / Reverse option, but not the FSS Tuning axis.

Probably a small tweak that can be added quickly

Thanks,

Cmdr SpookyNeo

 

[glaukos]

I agree with you that there's no reason not to have this option for this one axis when every other axis in the keybinds does have the option. However, in the meantime, I've learned that you can manually get around this issue by clearing the keybind first and then re-setting the keybind by pushing your axis in the opposite direction from the way you pushed it when you originally set it. You have to clear the binding first though. It doesn't work if you just try to reset it without clearing it with Escape first.

 

[spookyneo]

I agree with you that there's no reason not to have this option for this one axis when every other axis in the keybinds does have the option. However, in the meantime, I've learned that you can manually get around this issue by clearing the keybind first and then re-setting the keybind by pushing your axis in the opposite direction from the way you pushed it when you originally set it. You have to clear the binding first though. It doesn't work if you just try to reset it without clearing it with Escape first.

Thanks, but I already tried that. For whatever reason, it does not work with your method on my mini-stick on my CH Throttle. However, your method works on my mini-stick any other axis, just not for the FSS Tuning on the opposite direction. [knocked out]

 

[glaukos]

Maybe its resting position isn't perfectly centered and is therefore sending an input for the opposite direction the moment you touch it. Maybe try holding it a little bit towards the other way before you select the keybind or set a deadzone outside of ED in windows or CH utility. Don't know if that will solve your problem, but just trying to suggest some things to try so you aren't stuck waiting for FDev to hopefully fix this.