Announcement

Collapse
No announcement yet.

ASTRA Beta Profile doesn't work for me

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • ASTRA Beta Profile doesn't work for me

    I bought ASTRA a while ago, and I use it for Elite: Dangerous. However, I am limited to using the basic profile because the Beta will not work for me. Voice Attack recognizes my commands, but does not execute them or play the sounds. Moreover, when using the beta profile, certain keys on my keyboard become disabled, specifically the "U" key. I have searched the internet for a long time for an answer, but it appears I am the only one with this problem. Can someone PLEASE tell me how to get this to work? I have read the guides, watched the tutorials, read the forums, NOTHING has the answer! Please do not reference me to those things. If you would like to help, just tell me what to do. Thank you for your time.

  • #2
    For the beta profile:

    When you log into the game, you have to EACH AND EVERYTIME say one of the following commands depending on your "logging in situation". These will need to be said before you do anything else with your ship as they set up variables needed for the rest of the profile.

    If docked when loading in: "Reset all systems;Run diagnostics;Check all systems;All systems check;Full diagnostic scan;Initiate diagnostic scan;Prepare all on board systems" (or F3)
    If in space when loading in: "Reset Panels;System checks;Check systems;System scan;Check onboard flight systems;Software debugging;Run software debugging;There's a ghost in the machine, hunt it down" (or F4)

    This will setup the variables needed.

    Now, about the keypresses. The easiest way to do this (I find) is to just disable the shortcuts in Voice Attack, it is the 2nd icon that you just need to click. What this will do, is make it then just run the commands when you say the command, and not run the "Voice Attack" version of the command when you press the key.

    I *believe* that it was done this way to work around a couple of issues that were present when doing it the normal way (not passing through the keypress, so I believe it was double sending the command, one with the keypress directly, again with VoiceAttack).

    So, if you are not too bothered about Voice Attack not saying anything when you press the key directly, either disable the shortcut keys via the button on Voice Attack, or you can edit the profile so that each command only has a Voice Command linked to it.

    1) I reject your reality.... and substitute my own
    2) Not to be used when upset... will void warranty
    3) Stoke me a clipper i will be back for dinner
    4) Never tell Gangrel to do anything... he will probably get it wrong
    WARNING! Swedish wall-of-text hits you for bork-bork-bork damage!

    Comment


    • #3
      Originally posted by Gangrel View Post
      For the beta profile:

      When you log into the game, you have to EACH AND EVERYTIME say one of the following commands depending on your "logging in situation". These will need to be said before you do anything else with your ship as they set up variables needed for the rest of the profile.

      If docked when loading in: "Reset all systems;Run diagnostics;Check all systems;All systems check;Full diagnostic scan;Initiate diagnostic scan;Prepare all on board systems" (or F3)
      If in space when loading in: "Reset Panels;System checks;Check systems;System scan;Check onboard flight systems;Software debugging;Run software debugging;There's a ghost in the machine, hunt it down" (or F4)

      This will setup the variables needed.

      Now, about the keypresses. The easiest way to do this (I find) is to just disable the shortcuts in Voice Attack, it is the 2nd icon that you just need to click. What this will do, is make it then just run the commands when you say the command, and not run the "Voice Attack" version of the command when you press the key.

      I *believe* that it was done this way to work around a couple of issues that were present when doing it the normal way (not passing through the keypress, so I believe it was double sending the command, one with the keypress directly, again with VoiceAttack).

      So, if you are not too bothered about Voice Attack not saying anything when you press the key directly, either disable the shortcut keys via the button on Voice Attack, or you can edit the profile so that each command only has a Voice Command linked to it.

      Got it to work now, thanks

      Comment


      • #4
        Glad to hear it's all sorted
        1) I reject your reality.... and substitute my own
        2) Not to be used when upset... will void warranty
        3) Stoke me a clipper i will be back for dinner
        4) Never tell Gangrel to do anything... he will probably get it wrong
        WARNING! Swedish wall-of-text hits you for bork-bork-bork damage!

        Comment

        Working...
        X