Keyboard Map - List

Trying to find a printable or at least viewable list of keyboard commands for programming HOTAS. I've tried several different search terms but apparently haven't hit the correct one... or maybe there isn't one? Question is, why not? It seems this would be fairly useful but many online are older and does not contain as many commands as seem to be in the game setup. It appears some may be doing double duty but it would be helpful to have a complete list. Certainly appears to be a well kept secret.
Thanks.
 
I just use the list in the game. 🤷‍♂️
Programming with Thrustmaster T.A.R.G.E.T. The in game list is not helpful. I need to know what key binds have to be programmed to make the controls work. Updates have rendered the mappings available online marginally useless. Buttons don't behave correctly because the keys referenced are no longer correct.
 
Not completely sure what you mean OP, but the site edrefcard supports both up- and downloading binding files as well as printing them out.
-the site can be found here: https://edrefcard.slions.net/
I need a list of commands on the keyboard, either individual key presses or whatever combinations may be necessary to program the Warthog Thrustmaster with T.A.R.G.E.T. So far all that I have found are not entirely correct and when the buttons are programmed they do not work correctly. There doesn't seem to be an updated keyboard map.
i.e. next fire group, previous fire group, swtich modes... what keyboard keys or combinations of keys make those things happen?
 
I need a list of commands on the keyboard, either individual key presses or whatever combinations may be necessary to program the Warthog Thrustmaster with T.A.R.G.E.T. So far all that I have found are not entirely correct and when the buttons are programmed they do not work correctly. There doesn't seem to be an updated keyboard map.
i.e. next fire group, previous fire group, swtich modes... what keyboard keys or combinations of keys make those things happen?

You could have used the edrefcard tool to generate the default list. Here it is for the KeyboardMouseOnly preset:





yrjfpd-keyboard.jpg


Enjoy.
 
Thank you!
Tried to use that but keep getting:

Internal Server Error​

The server encountered an internal error or misconfiguration and was unable to complete your request.

Still do.... No idea why.
 
This is the best I could find as to being a recent list. There are a couple settings that don't have a key after the modifier - (Left Shift, Right Ctrl) that I have no idea about. Wish I could say this was 100% correct and complete but I can't. Fairly accurate so far although some keys had to be added in game.
Yes, you can print out your key binds after you create them but using Thrustmaster "T.A.R.G.E.T." or "Joystick Gremlin" needs a starting point.
This was copied from an image file found online. No idea who the original creator was but the image was too big to print out on a single page and was a bit fuzzy. You'll see why:) This should be a bit cleaner, easier to print and read.
 

Attachments

  • Elite Dangerous Key Binds.pdf
    58.8 KB · Views: 221
Programming with Thrustmaster T.A.R.G.E.T. The in game list is not helpful. I need to know what key binds have to be programmed to make the controls work. Updates have rendered the mappings available online marginally useless. Buttons don't behave correctly because the keys referenced are no longer correct.
Nonsense. I use TARGET as well. I've not once needed a reference card.

Just use borderless mode in the game while you're setting your mappings.
 
Nonsense. I use TARGET as well. I've not once needed a reference card.

Just use borderless mode in the game while you're setting your mappings.
How do you set the keys in target then? If you don't have a list of what keys work for what in game option, other than axis controls, how do you assign anything?
Do you just arbitrarily assign key combinations to whatever control and then set same in the game options? Is there no list of what key or key combination activates in game functions? i.e. the "list" I found has the letter "u" for deploy/retract hard points. If I assign that letter to a function in TARGET it works. What would happen if I simply picked the letter "a"? What may or may not be assigned to that letter already in game? I have no idea. I would think there was a default list of key bindings you could use.
I have TARGET working fine but I did use that list I found online to do it. Don't know if it's 100% accurate but it seems to work fine.
 
There is an authoritative list - just select "mouse and keyboard" as the control scheme.

Put the game client in borderless so alt+tab is seamless.

Look at the mapping in the game, then switch to TARGET and map that key to a button on the stick.

When you're done mapping keys, you can start the TARGET script*, go back into the game and map your joystick axes. You can also add secondary mappings or overwrite any mappings (like the fire key) with a button on the stick you haven't mapped (like the trigger), and get rid of mouse mapping to ship rotation axes. The name of the bindings file will change to "Custom" when you add a new or different mapping.

* Be aware that Windows 10 has some power-saving options that will turn the stick off a few minutes after you launch the TARGET script. I don't know if this is also an issue in Windows 11, but if it affects you:
  1. Download USBDeview.
  2. Right click on it and select "run as administrator".
  3. Find your stick in the devices list. It should be plugged in with TARGET not running - this makes it easy to find the device in the list, which can be rather long.
  4. Right click on the device and select "open in regedit". This is why you launch as admin - you can't do this otherwise.
  5. Expand the selected folder in the right-hand pane - it starts with something like 6&1aabb...
  6. Select the 'Device Parameters' subfolder.
  7. In the main pain, double click on the entry 'EnhancedPowerManagementEnabled' entry.
  8. Change the Value Data entry to 0.
  9. Hit return. Just to be sure!
  10. Restart.
Basically, when you run the TARGET script, the driver hides the physical stick from Windows. Windows, thinking the device has been removed, turns off power to what it thinks is an empty USB slot. You could be in the middle of docking/undocking/fighting when this happens, which might give you a really bad day. Changing that registry parameter prevents Windows turning the port off, meaning that the stick doesn't lose power.

You can, of course, edit the registry entry without USBDeview, but you'll need to know the VID of the stick.
 
Last edited:
Back
Top Bottom