problems etting this to workpa

[UndyingPhoenix]

So ive read through most of the pdf, the getting started sticky post, and watched a few different tutorial vids on you tube but somehow i cant get VA to communicate with the game. i've also done the windows voice practice. talking to VA itself, all the commands work even when in game, to clarify the in game part, VA hears me and talks back but nothing happens in game. i have not changed any key binds from the non beta profiles (tried all 4 as well as 1 beta profile) and have never changed the in game bindings except for adding joystick controls, but still leaving original controls as they were. i installed VA before the voice pack, and as suggested did not change the path it installed to. also copy pasted whichever profile i had active into my ED bindings folder. tried to change where VA sends the info from "current active window" to the actual game window didnt work either. Am i missing something, or any ideas would be greatly appreciated, also if i haven't supplied enough info ask away and i will get it to you. would love to get this figured out.

also i just tried making my own test key bind with "gear down" using "standard key" and not "windows game (directx)" key but that didnt work either.

[UndyingPhoenix]

fixed it, guess from all that reading i was doing i skipped the troubleshooting part about changing the keystroke time up from .1

now i just have to rebind all the in game keys, or spend the time to make my own setup, since the preset profiles do not use the default keybindings from ingame

[Arn1e2040]

you can load the .binds file from the profiles folder I think... not done this myself as the only things I've had to bind myself are the engine power increments, super-cruise (which isn;t bound by defualt anyway) and re-bound the wing commands... everything esle seems to work... and as they develope the packs and update them, they shoudl get even better

It's a long process developing new packs, and they are only a small team doing this, so bug fixing can sometimes take a back seat to testing and other things...

[Gangrel]

You need to copy the .binds folders from the profiles folder to

C:\Users\<username>\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings

Then it will be selectable in game. I have actually renamed one of the profiles for me as "Voice Attack X52". Any changes that I make in game *WHILST* using that profile get saved to this. Makes life a bit easier

Also, since Voice Attack has updated to include categories and the abilities to *view* commands in categories, we also put all of our commands into a "keybinds" category. This can be used one of 2 ways.

1) You change your bindings in Elite Dangerous to match these ones.

2) You change the bindings in Voice Attack to match your Elite Dangerous ones.

There is option 3 which is "do both of the above".

We actually had bindings for a lot of the extra commands implemented before each beta patch went full release. And in some of these cases (Debug camera for example) it *LOST* its ingame binding. In beta it was ctrl+alt+space. When it went live, it was instead an unbound command. So we chose to bind it to F1. I believe that the wingman commands were not originally bound, so we bound them accordingly.

Sometimes stuff like this happens, but we do try to keep the overall lack of rebinding down to a minimum., If anything, we just add keyboard commands to where there were none. That is not to say that sometimes we *don't* end up wishing that we hadn't rebound stuff, but overall momentum and consistency between the packs is what is important overall as well. Some of the changes.

But we do say that at least you can change your keybindings in VA with minimal issues[1]

[1] Increase thrust being an exception apparently