I was able to fix it by disconnecting my throttle and binding it to my stick. After that I reconnected it and everything works perfectly.
I'm using Saitek Pro Flight Combat pedals, and I'm having this problem too. I can bind yaw-left, but it simply won't even recognize the obvious action for yaw-right. (I can bind the toe-brakes to either yaw direction, but that's a very weird control scheme.)
Still seems bizarre that they're binding "directions" at all, rather than simply binding axes and letting you invert if necessary.
FWIW, I've spent countless hours playing Elite Dangerous with my setup and have NEVER had control problems like this.
Okay, I just stumbled across a workaround for this issue that actually works, and doesn't require any jumping jacks or hokey pokey with device unplugging. Just a little bit of thoughtful trial and error.
Basically, editing the configuration file :-)
So basically make a copy of your configuration file:
(in my case, having installed via Steam, this is where it is)
C:\Users\myname\Documents\STAR WARS Squadrons Steam\settings\ProfileOptions_profile_synced
Then go into the game, and mess around with the particular bindings you're trying to change. Each time you change them, compare the updated file to your saved copy. It shouldn't take long to figure out which key corresponds to the setting in question. A little bit of trial-and-error from there, and you can find the identifier for the axis direction the game won't let you bind.
In my case, I was trying to bind yaw left/right to my Saitek Pro Flight Combat pedals. In the game, these are joystick 3 (a.k.a. device 2 in the config file)
The corresponding settings keys were "ConceptYaw.6" (right) and "ConceptYaw.7" (left).
Binding the "yaw left" direction was do-able in game, and set the following lines:
GstKeyBinding.IncomStarshipInputConcepts.ConceptYaw.7.button 47 GstKeyBinding.IncomStarshipInputConcepts.ConceptYaw.7.deviceid 2
Binding the "yaw right" direction required manually editing the configuration file to set the following lines:
GstKeyBinding.IncomStarshipInputConcepts.ConceptYaw.6.button 46 GstKeyBinding.IncomStarshipInputConcepts.ConceptYaw.6.deviceid 2
Once I saved the changes, I restarted the game, and both yaw directions were bound correctly! (and yes, they both worked)
In other words, the bug that's driving us up the wall is in the settings screen, not the game itself.
That config file is super-confusing. The bit where it seems to be assigning device IDs looks like this:
GstInput.JoystickDevice1
GstInput.JoystickDevice2 CH Pro Throttle USB
GstInput.JoystickDevice3
GstInput.JoystickDevice4 CH Pro Throttle USB
So my throttle is listed (twice?), and my Fighterstick is not listed at all. In the actual bindings, no entry ever refers to deviceid 2 or 4, though. I see entries listed as deviceid -1, and some as deviceid 0, and some as deviceid 1. There doesn't seem to be much rhyme or reason to them. I have "roll" bound to my stick, and that entry is listed as deviceid -1. I have throttle bound to my throttle, and that is also listed as deviceid -1.
I'd love to bind yaw to the analog ministick on the throttle, but the in-game config won't let me bind anything to that stick, so I'm not even sure what button (or axis?) number it is. Given the number of possibilities, it seems like it would take weeks of trial and error to sort out. ☹️
For me, the config file trial-and-error wasn't very hard. It think its because the game did let me bind my pedals to yaw right (while ignoring yaw-left), but let me bind other things to yaw left. (though I get the two confused easily, because yaw-right involves the left foot)
Anyways, here's how my trial-and-error process went (or could be repeated):
The key is to make one change at a time, to either identify a specific config key, or identify a specific control axis. Now if the game completely ignores an axis in both directions, this whole thing will get much harder.
Regardless, this is a bug none of us should have to put up with, so I hope they fix it soon.
FWIW, none of that USB unplug/replug/do-the-hokey-pokey-and-turn-yourself-around stuff helped at all, in my particular case.
