Rethink key binding UI
- Thread starter Jason S
- Start date
Its the first time we have had to use the key binding UI since day 1 really but I agree.
.
FD don't need to reinvent the wheel just look at how something like FSX does it with menus for flight controls, sim controls, map controls, Driving controls and also let us know when we have already bound a key within that menu (so if button 6 is landing gear and we select button 6 again for lights we get a warning its already bound - the landing gear button isn't just overwritten)
.
It shouldn't be two difficult to achieve?
.
FD don't need to reinvent the wheel just look at how something like FSX does it with menus for flight controls, sim controls, map controls, Driving controls and also let us know when we have already bound a key within that menu (so if button 6 is landing gear and we select button 6 again for lights we get a warning its already bound - the landing gear button isn't just overwritten)
.
It shouldn't be two difficult to achieve?
a +2 from me. I remember when i first got this game, That options page alone VERY NEARLY put me off the game before i had even done a training mission. I know it a bit better know, but man it is a Mess!
Last edited:
This is the reason tabs were developed.
And a +3 from meThe controls binding menu is truly atrocious. The sad thing is that other menus with a lot of items are almost equally as bad (take for, example, the outfitting - why not have tabs for different module types? We can already sort by them...)
Quoted for truth. As the list of outfitting items is only going to increase, they need to do something about it sooner or later.
Yeah, yeah, I know, the usual excuse. "It's early days, it'll get better over time"....
Last edited by a moderator:
@OP I agree with you. ^^
I've been criticial of the whole controls situation in the past and I'm happy to say things are a lot better. One area that is still not great is that for those of us with multiple devices it's basically impossible to tell in the UI which device is bound. A control may be bound to "Joy X" which could be a joystick, gamepad, wheel or anything else that's supported by the game. The distinction is clearly seen in the XML file but not presented in the UI.
Not only is that information not shown, half the screen is mostly unused apart from the short control descriptions so if they were moved to the top or bottom the bindings list could easily expand enough to include the controller names.
Not only is that information not shown, half the screen is mostly unused apart from the short control descriptions so if they were moved to the top or bottom the bindings list could easily expand enough to include the controller names.
Yup. With most HOTAS this is.. awkward.
It'd also be great if they added Hold/Toggle options for each on/off control (or else added a direct binding for it). As it stands, I have loads of flick switches on my HOTAS that I can't bind to things like lights. If I try I end up having to flick the switch to turn the lights on, flicking it off does nothing. Flicking it on again turns them off, flicking it on again does nothing..
These two changes - plus making it easier to select sections - would go a long way.
Yes, its poor but I don't see it as a priority though. Can't say as I go into it much after getting things set up
Yeah, the keybinding UI is like Ravenholm - we don't go there anymore.
That might be the case for you. It may also be a major hurdle for new users before they get to your position. Sure, it's not a priority and the range of available options is outstanding. The presentation however is rather inconvenient.
Last edited:
