Announcement

Collapse
No announcement yet.

Guide to the voice package

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Guide to the voice package

    Here's a video with valuable guide to sorting out the keys in game - Copying binds to the game.
    In order to use the voice pack, you must copy the appropriate Keybindings file from the HCS folder:

    C:\Program Files (x86)\VoiceAttack\Sounds\hcspack\profiles\Binds

    and select the appropriate keybindings (go into the folder and select the actual keybinding file, rather than copying the folders) and copy-paste it into the Elite: Dangerous folder:

    C:\Users\YOUR_NAME\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings

    Now when you load up the game, go to Options>Controls and select the drop-down list at the top. You should find the keybindings in there!
    This video displays the in-game Keyboard & Mouse bindings used by our pack.

    Playlist guide on how to use Voice Attack
    Explanation of Voice Attack Profiles:

    Basic Profile: The basic profile - This is the profile you should start with, watch the help videos and become familiar with it - then you can move to the "Full House"

    Full House: This profile contains the add ons - GalaXapediA, Constellations, Quantum Theory, Commodities, Ships etc. It's the profile we recommend using once you have watched the help videos.

    Beta Profile (VSaSC): The Beta (Beta means it's experimental) profile is a full extension of the Basic profile, and is derived from the original Voidflakes Station and Ship Commands (VSaSC). While still in testing, it carries a great deal more commands, many of which are toggleable.

    The downside to this of course is that occasionally things get messed up, keypresses may confuse the panel lists and toggles, etc. This should only be used if you're savvy with Voice Attack or don't mind that it's a work in progress.

    Generally when things mess up, it's easily fixed simply by setting all ship systems to default and resetting the profile. This can be difficult and inconvenient while in stressful situations however, hence our wish to keep the profile in Beta for now, until we have it fully optimised and made easy to use by everyone - not just those who already know their way around the game and Voice Attack.

    Some of the additional commands and settings available in the Beta profile -

    1. The original VSaSC profile (menu navigation for stations and ship computers)
    2. Most functions are operated through On/Off toggles rather than single keypresses
    3. Request/Cancel Docking calls
    4. System Map and Galaxy Map calls
    5. Take Off and Landing calls
    6. Space goblins that will eat your ship
    7. More to come!
    Many of Astra's vocal responses conflict with the in-game computer's voice. While these are generally up to your personal taste to switch on or off, the list below contains the sounds that most conflict with Astra.

    Simply go to the in-game Options menu, then Audio, and switch these to the OFF position:

    Silent Running Engaged
    Silent Running Disengage
    Flight Assist On
    Flight Assist Off
    Landing Gear Deployed
    Landing Gear Retracted
    Cargo Scoop Deployed
    Cargo Scoop Retracted
    Heatsink Deployed
    Hyperspace Jump Initiated
    Supercruise Jump Initiated
    Many people are asking about some of the commands being disabled inside the profiles. They are supposed to be this way and do not need to be touched.

    DO NOT ENABLE OR DELETE THEM. This will break some aspects, or the entirety, of your profile.

    The double-bracketed commands, as well as a few others, are internal commands that are disabled so they cannot be called by voice. The voice-activated toggle commands show 'disabled' next to them simply because they are linked to the same keypress. This stops them from getting confused and inputting multiple times instead of only once, as required.

    Advanced users may alter the Keybindings category and the in-game keybindings to suit their needs, however this option is strictly available for people who know what they are doing.

    We take no responsibility for any mistakes you make doing this - that's why we have preset commands in the first place.
    Interaction Mode or the 2-Way S-Ai works in the basic and beta profile.
    TRIGGER FOR BASIC PROFILE “retract landing gear”
    TRIGGER FOR BETA PROFILE “run diagnostics”
    After the triggers are used, you can then use the on, off commands for it – which is
    “Interaction mode on” .
    “interaction mode off”.

    To remove the automated Interaction Mode feature, simply remove the following 3 lines from the very end of either "Run Diagnostics" and "System Checks" (Beta profile) OR from "Retracting Landing Gear" (Basic profile):

    Pause 0.03 seconds
    Set [interaction-mode] value to 1
    Execute command, 'ASTRA RANDOM COMMAND' (and wait until it completes)

    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!

  • #2
    I found an issue in the Beta profile where testing for a variable = 0 didn't always work if the variable had not been created yet. I therefore changed all the toggle variables to use 'has the variable been set/not set' as you can unset a variable when you want it to be the equivalent of 0. This has greatly improved the operation of commands at start up as there is no ambiguity concerning if a variable is 0, the variable simply is or isn't.
    All the variables that are used for random events or choice decisions are still the same as the setting of the variable is performed at the beginning of the command sequence so no ambiguity can arise.
    I hope this info is of some use.
    Last edited by WolfMax; 03-19-2015, 07:20 PM.

    Comment


    • #3
      just wondering but which version of Voice Attack/ HCS profile are you using? ie ASTRA Full house profile 1.6.3?

      Just curious as there are updates coming (soon™) that might fix this already for you.

      Thanks for the heads up though.
      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


      • #4
        Thanks for the reply Gangrel. The version.txt file says it is 1.6.3 and I'm using the 'Beta VSaCS' profile tweaked with some extra commands, which are:

        A request departure clearance which uses Text to Speech as the station control voice, randomly chooses a response for it to make then randomly chooses a voice to say it with (shame there are no mail voices to download from Microsoft), coupled with the launch and ascend commands.
        Commands to switch to and from the new 'Debug Camera' and to toggle the HUD off and on
        Commands to enable and centre an EDtracker head tracking device. It requires the EDtracker app to be running to process the hotkey to centre the view but uses EDs commands for on and off.
        Commands to setup Flight configuration and Docked configuration should things get a bit confused and a diagnostic command to report the state of the main toggle variables (cargo scoop, landing gear, hard points and docked).
        An Auto Pilot command, essentially the same as request docking except for use with the docking computer but which sets the landing gear toggle as ASTRA is not involved after the docking request is made.
        And some general timing tweaks and sound file adjustments but also cleaning up some commands which appeared to me to call another command which then called the first command again (looped ?). I don't know if I have found them all.

        How do I go about downloading the update when it is released?

        Cheers
        Colin

        Comment


        • #5
          You should receive an email telling you if there was an update or not.

          There was one on the 18th of March, for 1.6.4.
          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


          • #6
            Hi Gangrel, I didn't receive an email notifying me of the 1.6.4 update. I purchased on the 15th of March. I only just created this forum account now. Should the email updates be coming even if we haven't made a forum account or is it tied to his login?

            Also in order to redownload the pack I currently believe my only method is to follow the link in an email I received with my purchase. I checked out with paypal and don't seem to have a website account tied to purchases I have made. Is this part of the reason I can't find an easy way to login to the page to redownload and am also not receiving email updates? (Also of note: I just signed up to the newsletter which might solve half of my problem).

            Cheers!

            Comment


            • #7
              Oh. I have just found your new site. This answers some of my questions... creating an account their now. Will it link to my purchases?

              Comment


              • #8
                Well if I had waited 30 seconds to create the account the answer would have been clear. All my purchases are there waiting for me. Thank you very much! P.S. I love what you guys are doing here.

                Comment


                • #9
                  Just so you are aware: If you keep the original email, that link is valid and will get you the up to date version of the voice pack
                  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


                  • #10
                    I have some troubles using commands like "request docking permission", "cancel docking request", "afterburners" etc. so the VSaAC command in particular. VA recognizes them (green mark) and my binds are correct...
                    I have tried the latest version of VA 1.5.7.73 Beta and 1.5.7 also keyboard and hotas .vap of the the Astra/DARK 1.6.5 Beta (FullHouse)
                    I checked the keybinds ingame and in VA seems to be okay but there is no soundfile playing and no action taken so that I cannot tell what is going on.
                    I noticed that multiple keys like 1,2,3,U,TAB and some more are no longer functional when shortcuts are activated at VA.

                    Do you have experienced something like this before? Any Ideas what I could do?

                    Edit: I found something on the Interwebs... here is a link for people with similar problems.
                    https://forums.frontier.co.uk/showthread.php?t=142254
                    Last edited by JakeLikesCake; 06-08-2015, 12:31 PM.

                    Comment


                    • #11
                      Hi JakeLikesCake,

                      Is it just the sound files that are not being picked up, the actual commands work okay? This normally only happens if Voice Attack is having trouble locating the sound files. If you look inside any of the commands you're having trouble with (or the appropriate ((RS- SOUNDS)) for that command), you can click on the sound files then press edit - another window will pop up with a 'Preview' button. If you press this the sound should play. If a warning pops up saying it couldn't find the file, hit the '. . .' button and see if you can find the correct sound in the file-list. If you do, add it and hit 'Preview' again to make sure it works. It could just be a spelling error or misplaced file that's causing the problem!

                      If you've tried the above and everything is already in good shape, but you are still having problems with the sounds in-game, let us know and we'll give it a proper look! But in any case, we should be releasing the fully-fledged 1.6.5 update for ALL packs pretty soon, and this includes a few minor fixes for the packs already at 1.6.5 (this includes Astra, Jazz, maybe Midnight). We're hoping to have a lot of the problems across the board mopped up now

                      Comment


                      • #12
                        Originally posted by JakeLikesCake View Post
                        I have some troubles using commands like "request docking permission", "cancel docking request", "afterburners" etc. so the VSaAC command in particular. VA recognizes them (green mark) and my binds are correct...
                        I have tried the latest version of VA 1.5.7.73 Beta and 1.5.7 also keyboard and hotas .vap of the the Astra/DARK 1.6.5 Beta (FullHouse)
                        I checked the keybinds ingame and in VA seems to be okay but there is no soundfile playing and no action taken so that I cannot tell what is going on.
                        You need to ensure that EACH and EVERY time you load up the game, that for the beta profile you do the initiation commands. I just tried it without running the initialisation command and the same thing happened.

                        If docked: "Reset all systems;Run diagnostics;Check all systems;All systems check;Full diagnostic scan;Initiate diagnostic scan;Prepare all on board systems"

                        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"

                        I noticed that multiple keys like 1,2,3,U,TAB and some more are no longer functional when shortcuts are activated at VA.
                        I personally remove the shortcut keys from Voice Attack, it doesn't affect the controls when you press the keyboard, however stuff like F3 and F4 (for docked and inspace re-initialisation of the panels) won't work with a keypress and just with a voice command.
                        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


                        • #13
                          Hi Voidflakes hi Gangrel...

                          You are absolutely right and you already posted that here right on top... I didn't notice that part.
                          Sorry guys, anyway you saved me hours of time can't make it to reqest docking but maybe after the update.
                          Looking forward to check out upcoming packs.

                          Edit: Docking now works like a charm when VA is set to Active window instead of Elite dangerous (Client)
                          Last edited by JakeLikesCake; 06-08-2015, 09:22 PM.

                          Comment


                          • #14
                            HI Gys,

                            is command "initialize" or "System diagnostic" supposed to be recognized by Astra? Because it is not in the Full House HotaS BEta profile....

                            Comment


                            • #15
                              When docked : "Reset all systems;Run diagnostics;Check all systems;All systems check;Full diagnostic scan;Initiate diagnostic scan;Prepare all on board systems"

                              When in space: "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"

                              We don't actually have just "initialize" or "System diagnostic" buy themselves as a command.
                              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