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

  • morbidfacination
    replied
    I had VA working with a trial of Ivona and everything functioned normally. Although it was a simple Button press command and a speech response. Here with "Conditions" and Parameters VA dosnt work at all in ED

    Leave a comment:


  • morbidfacination
    replied
    I leave it on active window. Putting it in notepad I can see for instance Full Throttle presses the + key. In game nothing happens, even tho its bound for Full throttle. If I say "System Map" for instance, the command just turns off Keyboard shortcuts in VA but thats all. no in-game commands functional. Uggh,

    Leave a comment:


  • Gangrel
    replied
    what do you have the "send commands to" dropdown set to? Try setting it to Elite Dangerous or Active Window.

    If you have it on Active Window then you can always test the commands are working by keeping Notepad as the active window

    Leave a comment:


  • morbidfacination
    replied
    Everything checks out in the bindings, but still not getting any actions within the game. Verbal command feedback, just missing keybind actions. im missing something simple, im sure
    simple im sure

    Leave a comment:


  • Gangrel
    replied
    Those commands are for the beta profile only.

    You can double check the needed keybinds in Elite Dangerous to make sure that they match up with the list linked here

    Leave a comment:


  • morbidfacination
    replied
    Originally posted by Gangrel View Post
    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.

    Just installed this ASTRA pack for the first time, and when trying to use any of those commands they do not exist in the profile. Am i missing somthing? 1.6.5 Full house, HCSPACKS- KB+M Bindings selected in game. Copy/Pasted the bindings to the proper windows folder. I get some verbal responses but no commands working in game. Runing as Admin also

    Leave a comment:


  • AstroKiwi
    replied
    I discovered what the issue is: If I use Astra and X55 from Sandcrack for the bind, the two won't work together for some reason. If I say Power to Weapons, the main menu in front of the cockpit scrolls down once. I changed to K and M bind​ and Astra works for some reason. At least for the commands I have given her (Power to Weapons, comms panel on etc)

    Leave a comment:


  • AstroKiwi
    replied
    Hello Gangrel,
    thank you very much for the exhaustive answer. I think I understand where the problem lies, which I did not pick up before. You said that whenever I do something with the joystick that I should not, instead of using the voice commands, things break down. Well, I guess that explains the problem - hopefully. Whenever I jump in the seat, the first thing I do is use the HAT button on top of the X55 to look around. That already breaks VA....doesn't it? I'll try tonight again and see if I can make it work! With the basic profile for the HOTAS.

    Leave a comment:


  • Gangrel
    replied
    Originally posted by AstroKiwi View Post
    Okay,
    perfect. Thank you. Not sure why in the Readme file I remember seeing the command "initialize". My bad.
    I have another question if I may ask: I have not been able to use Astra as of yet in Elite Dangerous: I have copied to the ED Directory profiles the HCSPack K+M and X55 Hotas bind files along with some others.
    Going good here. Just double check that you have *Selected* the correct control profile in Elite Dangerous before hand (i have made this mistake myself in the past).

    I understand the X55 Profile is user generated. Everything works on the Keybindings front for the Joystick (apart from a couple of buttons) but Astra does not work: if I ALT-TAB out of the game, I can see that VA has shut off listening sometimes, and I have to wake up Astra. Even then, Astra does not execute commands.
    Voice Attack *shouldn't* stop listening automatically without any input, although we do have a command for that ("Voice Control Off" is standard across all our profiles just in case you are wondering).

    Question is: should I start using the Keyboard +Mouse HCS bind profile under ED and them map the buttons manually to my X55 Rhino in ED?
    Personal choice here. Ironically all of the profiles are "user generated" (I came up with the X52 profile, and it is just stock X52 joystick with the necessary keyboard bindings layered over on top). We also have a FLY 5 profile (that I really need to poke to get included in the other packs).

    If there is already a setup for the X55 when you plug it in, you can always double check the keyboard bindings over here

    That is what i did when I setup my profile. I actually used the list to double check, and it gave me the flexibility of setting up the joystick as and how I Wanted it (which is always handy for the joystick as each joystick has its own range of sensitivity settings).

    Sorry for this questions, I am totally confused to the point that I am actually getting stressed about it
    ​
    PS: I should say that I also got the VA Beta and imported the Full House beta commands into VA, paste the bind file into ED Directory but still no luck. Press F3 on the keyboard when docked and no commands executed.
    if you are not hearing anything when you press F3 (or even F4) to initialise the variables needed, then something appears wrong in your Voice pack installation. This normally happens when someone installs Voice Attack in one directory, and then installs the Voice pack on another drive/unrelated directory.

    If you click the wrench on voice attack and look about 2/3rds of the way down, you will see Sounds Folder and Apps Folder. You can change those directories if you choose to, but the voice pack will *have* to be installed (or at least cut and pasted) into that sounds directory.

    Personally I would start off with using one of the "basic" HOTAS profiles. That will get you up to speed and help iron out any bugs (in this case, why does VA stop listening every so often). This might come across as rude, but the "beta" profile is more for the experience VA/ED user as it has more moving parts (and the docking request command, which most people seem to want to use).

    HOWEVER, because of these extra moving parts, it can be a little bit picky and sometimes go belly up in one fashion or another (typically when someone uses their joystick to do something instead of a voice command, and so as a result, various tracking parts break down. There is no easy solution for this). Which is why I am suggesting changing the profile that you use. The same basic range of commands are there, and in fact the basic profile is MORE than adequate for most people (the difference between normal and Full House profile is the knowledge base).

    Leave a comment:


  • AstroKiwi
    replied
    Okay,
    perfect. Thank you. Not sure why in the Readme file I remember seeing the command "initialize". My bad.
    I have another question if I may ask: I have not been able to use Astra as of yet in Elite Dangerous: I have copied to the ED Directory profiles the HCSPack K+M and X55 Hotas bind files along with some others.
    I understand the X55 Profile is user generated. Everything works on the Keybindings front for the Joystick (apart from a couple of buttons) but Astra does not work: if I ALT-TAB out of the game, I can see that VA has shut off listening sometimes, and I have to wake up Astra. Even then, Astra does not execute commands.
    Question is: should I start using the Keyboard +Mouse HCS bind profile under ED and them map the buttons manually to my X55 Rhino in ED?

    Sorry for this questions, I am totally confused to the point that I am actually getting stressed about it
    ​
    PS: I should say that I also got the VA Beta and imported the Full House beta commands into VA, paste the bind file into ED Directory but still no luck. Press F3 on the keyboard when docked and no commands executed.
    Last edited by AstroKiwi; 10 September 2015, 12:12 AM.

    Leave a comment:


  • Gangrel
    replied
    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.

    Leave a comment:


  • AstroKiwi
    replied
    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....

    Leave a comment:


  • JakeLikesCake
    replied
    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; 08 June 2015, 09:22 PM.

    Leave a comment:


  • Gangrel
    replied
    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.

    Leave a comment:


  • Guest's Avatar
    Guest replied
    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

    Leave a comment:

Working...
X