Newcomer / Intro Keyboard control of modules?

[Stealthie]

Simple one this, hopefully...

In the right-hand cockpit display there's the "Modules" tab, which you can us to select a specific module (lasers. FSD, life-support, sensors, shields etc) and enable/disable it.

Is there any way to assign the commands for enabling/disabling modules directly to keys?

As the new owner of a Vulture, I've suddenly realised this feature might be very useful. [where is it]

 

[Chris Simon]

Simple one this, hopefully...

In the right-hand cockpit display there's the "Modules" tab, which you can us to select a specific module (lasers. FSD, life-support, sensors, shields etc) and enable/disable it.

Is there any way to assign the commands for enabling/disabling modules directly to keys?

As the new owner of a Vulture, I've suddenly realised this feature might be very useful. [where is it]

No. no keybinds. But you can assign a priority to each module, controlling which ones will shut down, and in what order.

Or you can program a macro in Voice attack or hotKey

 

[CMDR Mr. Boombastic]

Old but still a very good tutorial on power management(setting priorities of modules) AND fire groups:

Spoiler

[video=youtube_share;oO1E9_sPtvg]https://youtu.be/oO1E9_sPtvg[/video]

 

[Chris Simon]

Thank you, Boombastic. I thought about putting up the link, but couldn't be oh, come on. how is that a swear word?.

 

[Stealthie]

Bah! [sad]

I'm okay with setting the priorities etc but I was hoping for keybinds because I was planning on using a USB mini-keyboard as a dedicated controller for those functions.

 

[Chris Simon]

Bah! [sad]

I'm okay with setting the priorities etc but I was hoping for keybinds because I was planning on using a USB mini-keyboard as a dedicated controller for those functions.

Yeah. A bummer. I don't have a problem with this particular thing, but as a flight sim enthusiast, I also believe that every function should be bind-able to a key/button/axis even if it means hundreds of entries in controls options.
Maybe one day.

 

[Brassik]

As Chris Simon said, Voice Attack will let you do what you want. VA is also a fantastic tool for this game, but that's another subject.

 

[Codger]

Yeah. A bummer. I don't have a problem with this particular thing, but as a flight sim enthusiast, I also believe that every function should be bind-able to a key/button/axis even if it means hundreds of entries in controls options.
Maybe one day.

Boy do I agree with this. But FD seems to want to limit keybinds for some reason. We always have to ask for more, and they often say no (like just recently with a keybind for requesting docking - a flat out no from Sandro).

 

[Stealthie]

As Chris Simon said, Voice Attack will let you do what you want. VA is also a fantastic tool for this game, but that's another subject.

A voice-command will allow me to map controls to a USB keyboard?

To explain a bit more deeply, I used to enjoy flight-sims. I never quite got into them enough to build a proper "cockpit" but I did go as far as hacking up a USB keyboard to make a "break-out box" so I can then build button-panels and connect them into the box to be detected as key-presses.

I'm currently running ED using a HOTAS and a little button-pad with 20-odd functions on it but I could easily make another panel with 8 (or whatever it is) extra buttons on it to control the modules directly too - if the game allowed for key-binding those functions.

Also, to digress, although I love the idea of VR, I think one of the biggest problems with it is that it impedes a user's interactions with stuff in the real-world.
I know some HMDs deliberately have openings at the bottom so you can look down to see what you're doing but that can detract from the VR experience.

 

[Chris Simon]

The trick with the Voice Attack (for voice) or Auto Hotkey (for key commands) is that elite lets the program to "move around the cockpit"

So what you would do if you wanted to program a command for turning the shields off (let's say they are second in the modules list, below the thrusters), you would simply write a macro that would do the program to go: Look right -> one tab to the right -> One click down -> Click (open details) -> Click (turn the module off) -> Once tab left (to "reset" the panel to starting position for another macro)

You would then program it under a key press or voice command of your choice.

You can do a similar thing to ask docking clearance, and other things that can't be bound.

And yes, if you are thinking of VR, you have to be sure to have all commands available either by tactile feedback or muscle memory. Or use the voice command app.

 

[Brassik]

If you are considering VR. I'd recommend VA 100%. You can basically cut out nearly all keystrokes. Have a look on You Tube for Elite using VA and some using voice packs. You'll see whats possible