Keybinding Conundrum Questions

I've tried resetting my Thrustmaster T-flight Hotas X to default settings multiple times now, but this only assigns the bare minimum, leaving the game practically unplayable.

  • Are we as players supposed to navigate/assign this myriad of keybindings before being able to play the game?
  • Should this be expected of new players?
  • I assume that Xbox and PS controllers are fully mapped as default (can anyone confirm this?), shouldn't this practice apply to PC controllers as well?

  • Now I've seen excellent player created keybindings, but surely FD should be supplying complete comprehensive default keybindings, imagery included - maybe even multiple choice, for all the controllers that they support across all platforms?


...I tend to sort out key bindings a bit at a time, rather than the whole lot in one go. Cos half the time I don't know what I need, and the other half I don't know what the bindings actually refer to. I do love my Warthog, but it's tricky sometimes, especially when I get...

"JOY24 is already bound to this, are you sure?"

How the hell do I know whether I'm sure? Where the hell is JOY24 anyway? If I knew where it was, I might remember what I bound to it...


Or is it just me?


[hotas]
 
I use the X52 default config and everything you need is binded. Keep in mind that you don't need to assign every bind, many things are completely optional or redundant.
 
Last edited:
I assume that Xbox and PS controllers are fully mapped as default (can anyone confirm this?), shouldn't this practice apply to PC controllers as well?

I found the default PS4 controller mapping horrendous, and made my own. There's a popular one that many players use, but I can't remember the name. Anyway point is, there's a lot of futzing around with bindings, even on console.
 
Last edited:
I've tried resetting my Thrustmaster T-flight Hotas X to default settings multiple times now, but this only assigns the bare minimum, leaving the game practically unplayable.

  • Are we as players supposed to navigate/assign this myriad of keybindings before being able to play the game?
  • Should this be expected of new players?
  • I assume that Xbox and PS controllers are fully mapped as default (can anyone confirm this?), shouldn't this practice apply to PC controllers as well?

  • Now I've seen excellent player created keybindings, but surely FD should be supplying complete comprehensive default keybindings, imagery included - maybe even multiple choice, for all the controllers that they support across all platforms?





Or is it just me?


[hotas]

In my experience, the default settings of controllers are sufficient to play the game... casually. They'll get you up and about easily enough, but a lot of the bindings are there for advanced users. I am in awe of what Aussiedroid has accomplished between his knowledge of TARGET's script and the sheer number of bindings that Frontier has added to the game. It made my old CH scripts look amaturish in comparison.

That reminds me, I really need to start experimenting with TARGET scripts myself. So many interests, so little free time with my PC.
 
I use the X52 default config and everything you need is binded. Keep in mind that you don't need to assign every bind, many things are completely optional or redundant.

I can't even navigate galaxy and system map with default Thrustmaster T-flight Hotas X settings.
 
I can't even navigate galaxy and system map with default Thrustmaster T-flight Hotas X settings.

On the X52 the default bindings for moving on the system map are the same like lateral thrust, the hat on the throttle. There are some binds for the galaxy map as well but it's easier to use mouse and keyboard for it, you can't search for systems without it anyway. Unless you are using VR.
 
This would require FDev to be aware of all (or most) controller types out there, of which there are many. Have someone sit down and design the key bindings to how they thought would be best. Create the graphics for said layouts. Deploy these layouts into the game for people to select. You then have variants of these controllers. Some people only play with a throttle while others will use the full hotas. This is all very valuable time for a Dev to do for very minor improvement to the game itself overall and would still result in people complaining about the keybindings their given for their x,y,z setup not being what they think is correct.

I was happy to get a base keybinding setup for my Thrustmaster hotas which I then have spent some time customising to my own liking. I think I would have spent more time learning and then re-binding a more complete setup if it had been provided.
 
This would require FDev to be aware of all (or most) controller types out there, of which there are many. Have someone sit down and design the key bindings to how they thought would be best. Create the graphics for said layouts. Deploy these layouts into the game for people to select. You then have variants of these controllers. Some people only play with a throttle while others will use the full hotas. This is all very valuable time for a Dev to do for very minor improvement to the game itself overall and would still result in people complaining about the keybindings their given for their x,y,z setup not being what they think is correct.

I was happy to get a base keybinding setup for my Thrustmaster hotas which I then have spent some time customising to my own liking. I think I would have spent more time learning and then re-binding a more complete setup if it had been provided.

Valid points all, but I'm only talking about the controllers that FD actually made presets for. I can choose Thrustmater T-flight hotas X as a default controller setup, only to find half (?) of the keys not bound.

And seriously, if you create a game this controller heavy, the least you can do is actually supply (at least one) complete controller configuration.

If I was a new player, and booted this game up and chose controller only to find that some worked and some didn't, why would I even bother to endure?

If I wasn't an old Elite die hard I would have given up on this game long ago.

There's a brilliant game here. Why does it have to be so inaccessible?
 
Valid points all, but I'm only talking about the controllers that FD actually made presets for. I can choose Thrustmater T-flight hotas X as a default controller setup, only to find half (?) of the keys not bound.

And seriously, if you create a game this controller heavy, the least you can do is actually supply (at least one) complete controller configuration.

If I was a new player, and booted this game up and chose controller only to find that some worked and some didn't, why would I even bother to endure?

If I wasn't an old Elite die hard I would have given up on this game long ago.

There's a brilliant game here. Why does it have to be so inaccessible?

Also a valid point. I feel it's more an 'err on the side of caution' situation. Provide a half-complete key binding mapping so that people can customise it to their content rather than a 'full' mapping that many people would have to learn, won't like and will then complain on forums about changing the default mapping.
 
T......... This is all very valuable time for a Dev to do for very minor improvement to the game itself overall ..........

They apparently can't even spare the manhours to incorporate a "Save As" button for the Options / Controls page. This simple thing would obviate many, many issues we read in these fora about bindings issues.

Some of the prioritisation in F D leaves me bemused.


V...
If I was a new player, and booted this game up and chose controller only to find that some worked and some didn't, why would I even bother to endure?

.....

They could always consult the manual ..... oh, wait .... :D
 
Last edited:
They apparently can't even spare the manhours to incorporate a "Save As" button for the Options / Controls page. This simple thing would obviate many, many issues we read in these fora about bindings issues.

Some of the prioritisation in F D leaves me bemused



EXACTLY!!! The game is 4yrs old?, & it's a great game - but surely by now, we should have the facility to save our bindings into the list of Presets. It would make life so easy :cool:
 
EXACTLY!!! The game is 4yrs old?, & it's a great game - but surely by now, we should have the facility to save our bindings into the list of Presets. It would make life so easy :cool:

I don't know why people want several presets, but if it helps it should actually be possible with a workaround. You could use the different default presets for different devices and simply hijack them (they are located in your game folder). You would need to bind everything in a editor and set your desired input device somewhere in the first few lines. Never tried it but I don't see a reason why it shouldn't work. As said above, don't know why you want that either though... ;)
 
Last edited:
I don't know why people want several presets, but if it helps it should actually be possible with a workaround. You could use the different default presets for different devices and simply hijack them (they are located in your game folder). You would need to bind everything in a editor and set your desired input device somewhere in the first few lines. Never tried it but I don't see a reason why it shouldn't work. As said above, don't know why you want that either though... ;)

The main reason is that "custom" binds files are the ones that get overwritten by the game on occasion (missing controller, some game updates, etc).

Having your binds named differently (which you have to do by manually editing at the moment) prevents the loss of your settings. If there is ever an issue with a missing controller for example, the game loads a default (KB+M or similar) and writes the error to a file "BindingLoadingErrors.log" where you can see the issue, correct it and go back to your "named" bindings.

Since I first changed my bindings names I have never had an issue with them.

BTW - I used to have separate bindings files for different controller use - a Logitech 3D stick for use in RES instead of my normal CHPro Fighterstick - I don't do that any more. I do still have two alternate controls "setups" one for normal use and one specifically for exploration where there is no need for certain functions (like target next sub system, next hostile, etc) so I can have exploration-specific settings on my controls. (I don't mix them up now but I did have issues at first. ;) )
 
Last edited:
  • Like (+1)
Reactions: mg0
The main reason is that "custom" binds files are the ones that get overwritten by the game on occasion (missing controller, some game updates, etc).

Having your binds named differently (which you have to do by manually editing at the moment) prevents the loss of your settings. If there is ever an issue with a missing controller for example, the game loads a default (KB+M or similar) and writes the error to a file "BindingLoadingErrors.log" where you can see the issue, correct it and go back to your "named" bindings.

Since I first changed my bindings names I have never had an issue with them.

BTW - I used to have separate bindings files for different controller use - a Logitech 3D stick for use in RES instead of my normal CHPro Fighterstick - I don't do that any more. I do still have two alternate controls "setups" one for normal use and one specifically for exploration where there is no need for certain functions (like target next sub system, next hostile, etc) so I can have exploration-specific settings on my controls. (I don't mix them up now but I did have issues at first. ;) )


Aha! - So it IS possible.. Para, could I PM you for assistance.... [ugh]
 
Thanks B&B. I really appreciate the kind intentions of folks around here, but my gripe remains the same. Looking at that "HUGE" list just confirms for me, that this is something that really should be mapped by default. If FD can't be bothered to map all the functions, why do they think players will?

I think most of them are, if you choose 'T-Flight' from the drop down menu. But it was such an odd mix of non-inverted and crossover controls, I changed a lot of them.
Not being able to navigate menus in the galaxy map was a big one. I managed to map that
 
There are many different joysticks out there. This would mean FDev would have to make a map for each and every one. And bindings are such a personal preference thing, especially in a game like Elite with so many of them. I know after playing the game this long, the first thing I would do with any pre-mapped bindings is scrap them. If you went out and bought a special controller for Elite it's probably assumed you're gonna be willing to figure out the binds. Gamepad pre-mappings need to be there for the pick up and play console crowd. And that's an option with the PC version too and an Xbox controller.
 
Last edited:
There are many different joysticks out there. This would mean FDev would have to make a map for each and every one.

I don't know, I think if they just covered the most popular products that would be enough. Let's say:

Keyboard only
KB+M
X52
X52Pro
X55
X56
T.16000M FCS HOTAS
T.Flight HOTAS X
Xbox controller

And bindings are such a personal preference thing, especially in a game like Elite with so many of them. I know after playing the game this long, the first thing I would do with any pre-mapped bindings is scrap them. If you went out and bought a special controller for Elite it's probably assumed you're gonna be willing to figure out the binds. Gamepad pre-mappings need to be there for the pick up and play console crowd. And that's an option with the PC version too and an Xbox controller.

I agree, and I do find it puzzling how many people seem to struggle with the bindings, it's not really that difficult. But each time I've had to setup a new control scheme I've always started with a pre-existing scheme as a base and then customised it to my liking - for my T.16000M HOTAS I started with one of the TM schemes which wasn't too bad (and it had an associated diagram which helped).

Still, this is certainly a quality of life area that FD could do with spending some time on, and kudos to GD for trying to get some attention to the issue. It's odd how FD are clearly somewhat aware that they need to make the game more "accessible" (to new players especially) - see the 'Help' screens that are now more common i.e. the FSS Help, and they added the "!" in the Controls menu to warn players of a new binding (which is a start even if it didn't always work) - and yet new players are still struggling with a control scheme that's had no significant improvements since the game launched unless you count breaking it down into expandable sections. A lot of the descriptions are missing or vague at best, we still don't have a 'Save as' function and we are still stuck with 'press [JOY 5] to abort' unless you have a gamepad or a X52 (I think).

I'm sure it's "on the list" but it's probably further down than it should be. Surprising, considering how many mini-rants you see on here and the Steam community.
 
Back
Top Bottom