Got bored, created an Elite Dangerous Controls template/worksheet . . .

[BlackSpaceCowboy]

I have a HOTAS and Voice Attack. I don't have to remember any keyboard buttons. Appreciate the effort nonetheless.

Do you use voice attack to control the Galaxy Map?

 

[Bran Tse Mallory]

Excllent Thank you and repped.




What a bloody good idea, have you inserted this oh-so common sense suggestion in the Suggestions section? (more rep for common sense).

Myself and at least one other CMDR have posted about this already. A new player to the game would be very confused with so many keys needing to be bound just to explore and also take screenshots.

Great job OP!

 

[JetsonRING]

I have a HOTAS and Voice Attack. I don't have to remember any keyboard buttons. Appreciate the effort nonetheless.

I think we can all agree (those of us that use them) the HCS voice packs are not 100% reliable. To overcome that and use them effectively most keys still need to be bound.

Hey, I actually liked that game...

Loved Falcon 4.0 but you gotta admit, the keyboard map was HUGE. o7

 

[Notwyn]

Hey, I actually liked that game...

Then you should checkout Benchmark Sims (BMS) they have updated Falcon 4.0. Very good flight sim for the F-16.

 

[ExoForce]

Compared old and new bindings, this is new (Hotas-X):

Spoiler

<!-- Analysis Mode and DSS/FSS -->

<PlayerHUDModeToggle>
<Primary Device="Keyboard" Key="Key_M" />
<Secondary Device="{NoDevice}" Key="" />
</PlayerHUDModeToggle>
<OpenCodexGoToDiscovery>
<Primary Device="Keyboard" Key="Key_O" />
<Secondary Device="{NoDevice}" Key="" />
</OpenCodexGoToDiscovery>

<ExplorationFSSEnter>
<Primary Device="Keyboard" Key="Key_Apostrophe" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSEnter>
----------------------------------------------
<ExplorationFSSCameraPitch>
<Binding Device="ThrustMasterHOTAS4" Key="Joy_YAxis" />
<Inverted Value="0" />
<Deadzone Value="0.00000000" />
</ExplorationFSSCameraPitch>

<ExplorationFSSCameraPitchIncreaseButton>
<Primary Device="{NoDevice}" Key="" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSCameraPitchIncreaseButton>
<ExplorationFSSCameraPitchDecreaseButton>
<Primary Device="{NoDevice}" Key="" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSCameraPitchDecreaseButton>


<ExplorationFSSCameraYaw>
<Binding Device="ThrustMasterHOTAS4" Key="Joy_XAxis" />
<Inverted Value="0" />
<Deadzone Value="0.00000000" />
</ExplorationFSSCameraYaw>

<ExplorationFSSCameraYawIncreaseButton>
<Primary Device="{NoDevice}" Key="" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSCameraYawIncreaseButton>
<ExplorationFSSCameraYawDecreaseButton>
<Primary Device="{NoDevice}" Key="" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSCameraYawDecreaseButton>

--------------------------------------------
<ExplorationFSSZoomIn>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_1" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSZoomIn>
<ExplorationFSSZoomOut>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_2" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSZoomOut>

<ExplorationFSSMiniZoomIn>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_POV1Up" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSMiniZoomIn>
<ExplorationFSSMiniZoomOut>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_POV1Down" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSMiniZoomOut>
-----------------------------------------
<ExplorationFSSRadioTuningX_Raw>
<Binding Device="ThrustMasterHOTAS4" Key="Joy_RZAxis" />
<Inverted Value="1" />
<Deadzone Value="0.00000000" />
</ExplorationFSSRadioTuningX_Raw>

<ExplorationFSSRadioTuningX_Increase>
<Primary Device={NoDevice}" Key="" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSRadioTuningX_Increase>
<ExplorationFSSRadioTuningX_Decrease>
<Primary Device={NoDevice}" Key="" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSRadioTuningX_Decrease>


<ExplorationFSSDiscoveryScan>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_4" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSDiscoveryScan>

<ExplorationFSSQuit>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_11" />
<Secondary Device="Keyboard" Key="Key_Apostrophe" />
</ExplorationFSSQuit>

<FSSMouseXMode Value="" />
<FSSMouseXDecay Value="1" />
<FSSMouseYMode Value="" />
<FSSMouseYDecay Value="1" />
<FSSMouseSensitivity Value="5.00000000" />


<ExplorationFSSTarget>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_6" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSTarget>

<ExplorationFSSShowHelp>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_5" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationFSSShowHelp>

<ExplorationSAAChangeScannedAreaViewToggle>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_4" />
<Secondary Device="{NoDevice}" Key="" />
<ToggleOn Value="1" />
</ExplorationSAAChangeScannedAreaViewToggle>

<ExplorationSAAExitThirdPerson>
<Primary Device="ThrustMasterHOTAS4" Key="Joy_11" />
<Secondary Device="{NoDevice}" Key="" />
</ExplorationSAAExitThirdPerson>

<!-- Analysis Mode including DSS/FSS Scan end -->

 

[dayrth]

Thank you,Thank you,Thank you,Thank you,Thank you,Thank you,Thank you,Thank you,Thank you.

 

[Sierra_Hotel]

Do you use voice attack to control the Galaxy Map?

Nope, HOTAS hat switches and stick. Only time I need to touch the keyboard is to type in a system name.

Loved Falcon 4.0 but you gotta admit, the keyboard map was HUGE. o7

First game I ever saw that included a fold-up keyboard map. Loved that game, considered getting the updated version.

 

[ExoForce]

Can someone confirm how many controllers ED supports at once? I recall that 4 was the last confirmation long time ago.

(I see usage for HIDMacros. Check it, it is epic utility. I do not use LUAmacros, former is good and validated.)

 

[Jukelo]

Yeah, I think the controls are really going to need a re-think, 3.3 only exacerbates the problem.

The goal must be to have consistent controls across contexts. e.g. zoom is zoom, regardless of what mode you're in. Orrery, Galaxy Map, FSS, Camera Suite etc. One keybind and done.

Yes and no. The good alternative to removing options here, is simply to allow the game to bind a same key or combination of keys to multiple functions - which in most cases it already does. This achieves the same result as forcing the same keys across contexts where the devs think it makes sense, when for some players it might not - especially with the wide range of setups players have and like to build for this game.

268 keyboard or button bindings, the rest is sliders and switches and that count does not include joystick axis bindings. Yes, it's ridiculous. We are apparently expected to memorize over 268 buttons/switches, more than 2.5 times the number of keys on a standard 101-keyboard which is approximately the number of buttons and switches a commercial airline or fighter jet pilot must remember. Falcon 4.0, anyone?

These days I play ED mostly with the Thrustmaster Hotas X - probably the worst joystick I have ever had to play with. Still I only use about 30 or so different button combinations (out of 12 buttons), and it covers everything, since those 268 bindings are all spread across different contexts which, as I pointed out above, can share bindings - and a good few of them are made redundant by simply binding an analog axis anyway.
I don't think 30 is too much to ask in a game like this.

 

[Alec Turner]

This is really handy. Can I point to this thread from my "Best of Forum" sticky thread Jetson?

You planning on keeping it up to date?

 

[Patrick_68000]

Thank you,Thank you,Thank you,Thank you,Thank you,Thank you,Thank you,Thank you,Thank you.

You are welcome, You are welcome, You are welcome, You are welcome, You are welcome, You are welcome, You are welcome, You are welcome, You are welcome.

 

[JetsonRING]

This is really handy. Can I point to this thread from my "Best of Forum" sticky thread Jetson? You planning on keeping it up to date?

Just copy the link . . . anyone with access to the link has access to the spreadsheet.

I am not sure about updating it, it took a few hours to complete the first time. We'll see. I have also decided to try and develop a Control Panel app for use on my Surface Pro 2 running Windows 10. Trouble is, I have to teach myself XAML and how to effectively use Visual Studio. I haven't written code since the eighties. So far all I have created is a "Main" page with 12 large and 18 small buttons. I figure the large buttons will point to sub-pages. Took a couple of hours just to figure out how to set the application's theme to "dark". Fun!

Not bad for my first day with XAML, stay tuned:

 

[Drelthar]

It is awesome isn't it.

I can probably think of some keybinds they are missing too.

Specific bind for shutdown pulse neutraliser for instance.

 

[Funny]

Especially when one considers that about 90% of the harder-to-decipher binds have no explanation as to what they actually do . . .

Please don't mention it... and there's even a self destruct button just to confuse you as to whether you need to bind it or not XD
Hint: don't...

 

[ExoForce]

Jettison all Cargo is next to the Silent Running on keyboard.
Admit it, we all did it in the beginning and wondered where is cargo.

 

[Wasp0]

Jettison all Cargo is next to the Silent Running on keyboard.
Admit it, we all did it in the beginning and wondered where is cargo.

NEVER Sir, Never i say!...................................................................................................................................................(Twice actually, quickly learnt to unbind this key)

 

[Alec Turner]

This is really handy. Can I point to this thread from my "Best of Forum" sticky thread Jetson?

DONE

Alec-s-best-of-the-forum-(and-elsewhere)-v2

 

[Steyla]

This is absolutely great. Thanks for doing that.

rep+

Fly/land safe

CMDR Steyla

 

[JetsonRING]

Jettison all Cargo is next to the Silent Running on keyboard. Admit it, we all did it in the beginning and wondered where is cargo.

I think if I add "Jettison All" a CMDR will be required to press the button 3 times for it to work, as in "You Sure?", "You Really Sure?", "You Really, Really Sure?".

 

[nexxo]

A list of key-binds for a computer game.

In a 490 row spreadsheet. [sad]