Elite: Dangerous PvE - Mobius

There are a few videos in this tutorial they will play one after the other so feel free to watch them all in order or skip around if you already know the topic on hand.

https://www.youtube.com/watch?v=hs-FJee ... Sh&index=1

Thanks for this man!

My Docking , setup for Voice attack , the ((RS-xxxxxx)) can be made by you within Voice attack , some I use are already apart of the ED version of VA

https://forums.frontier.co.uk/showthread.php?t=72984&p=1583982&viewfull=1#post1583982

As this topic is already here I'll not make another one. I bought VA with ASTRA voice pack, and right now I'm trying to get it to work but I ran across some problems.

I can't enable the FSD jump by voice, no matter what command I use, it starts to execute, but stops immediately. The same thing happens with landing gear. After I say "landing gear down", the blue square indicator for it only flashes once- as it's lowered and upped at once. Lights are the same cause.

Could you please post here your VA command config for FSD or landing, that I can compare it mine and made necessary changes?

Thx.

Make sure you have it pressing the key for long enough (like 100 or 200 ms).

This I already tried, set the press time for 0,5 sec, but to no avail. I'll keep trying....

I had something similar at one point and realised that I had 'repeat' set so was toggling a command both on and off again. Checked for repeat?

Ok, finally solved the problem. Long story short....I'm dumb carbon unit.

The thing was, that i tried to customize the pre-made full "something" profile only by adding my key-binds from the game. I didn't notice that for example "lights on" command has it's own "hidden/disabled" command as well ((in double brackets)) with the shortcut already defined. So when I said "lights on" my added key-bind got executed, but the "hidden/disabled" command got executed immediately after that, resulting in double key press, which turned the lights off. Deploying hardpoints, engaging FSD, practically every other command with matching key-binds was the same case. But everything is now corrected and I'm happy camper.