DeeJay's Voice Activaded Commands (VAC) Profiles
-
I’m a little lost in the setup process with VAC. I downloaded the demo and the English keyboard version of DJ’s profile, do you just keep the VAC program running in the background (similar to the TrackIR software) and do you have to setup anything in BMS? My headset is arriving tomorrow so I can’t test anything yet.
Thanks
-
Correct. Load the profile into VAC Builder then VAC System runs in the background and you don’t have to do anything to F4BMS.
-
I’m a little lost in the setup process with VAC. I downloaded the demo and the English keyboard version of DJ’s profile, do you just keep the VAC program running in the background (similar to the TrackIR software) and do you have to setup anything in BMS? My headset is arriving tomorrow so I can’t test anything yet.
Thanks
don’t forget to activate VAC each time before you start BMS, you do this by right clicking the VAC icon in your windows taskbar, then click “VAC on”. Unfortunately it is this way until they make an autostart feature.
-
Just use task scheduler to create an elevated shortcut which automatically loads up a profile and turns voice on. Then double-click the shortcut along with TrackIR and other software you start before F4BMS. Simples.
http://www.sevenforums.com/tutorials/11949-elevated-program-shortcut-without-uac-prompt-create.html
-
Just use task scheduler to create an elevated shortcut which automatically loads up a profile and turns voice on.
is this due to the elevated control part or due to scheduler programming part - or both?
could you please share how you did it this way? many thanks darkman!
-
Cool, thanks guys. Just got the headset and it works well after I trained windows using speech recognition. This is so cool. Scuby I think the profile I’m using is yours, thanks!
-
is this due to the elevated control part or due to scheduler programming part - or both?
could you please share how you did it this way? many thanks darkman!
Click on the link in my previous post #70 above and follow the tutorial. That’s what I used to work it out and it takes you step by step through the whole process. For reference I’ve called my task VAC (the profile is called Falcon 4 BMS) and there are some screenshots below if it helps.
When you get to the action for the task I’ve entered```
/c start “VAC” “C:\Program Files (x86)\VAC System\VACSystem.exe” Falcon 4 BMS,true![](http://i.imgur.com/N1RXf.jpg) My shortcut has the following code:
C:\Windows\System32\schtasks.exe /run /tn VAC
I have the shortcut on my taskbar, so I click on it once and it opens up VAC System, loads the profile (Falcon 4 BMS) and then turns voice on.
-
that works! thanks you are the greatest!
-
You can use the same approach to avoid UAC prompts. You’ll note on the first screenshot I have another task called FrapsSkipUAC which does this. I click on the shortcut to this and it starts FRAPS without the annoying UAC prompt.
-
Hi Tank here,
looking to get my VAC working, I have managed to setup both the profile within the profile builder and loaded it within the system, I have also toggled on the VAC voice on! So I have the little microphone on with both of the toggles….
I then launch BMS and go through to campaign to test… And nothing!
The only way I can get it to work is through launching BMS directly from the VAC builder under tools then - program setup selecting the EXE for BMS… and then selecting TEST which launches BMS, this then works all day long…
I am running trial version at present tried many things to get it working… I am missing a command line or something to get it to function…
VAC is cool when it works through test mode only but really want to launch it via BMS ICON…
thanks for your help or any comments, thanks again to wolf and scuby for there replies already… I do not have a antivirus or firewall preventing and I have ran speech training once, testing the builder all call signs work perfectly.
-
Hi Guys,
I would need your help here, as always…
I’ve just installed VAC and it’s all working fine with kukki’s profile, really nice and impressive!
The only thing I can’t get to work is to assign the UHF button on my Cougar (BTN21) to enable F11 (on which I assigned the PTT button)I’ve tried somehow to modify Darkman’s code:
@Darkman:Ron aka Shift_E (author of VAC) has finally cracked it and I’m up and running with VAC, in fact it’s working better than I had hoped.
I have comprehensively edited the file, removed a lot of duplication around wingman commands and generally made it more to my taste. I use Dunc’s excellent Dunc_DX keyfile so have chosen F8 as my arming key for VAC (as it’s not used for anything else) and have mapped this to my Cougar radio switch (pinky + IFF in/COMMS right). For those with a similar setup you just need to open up Foxy and add the following:
Add this to the bottom of your .tmj (joystick) file:
Rem ### Map F8 to COMMS right (IFF In) for Voice Activated Commands BTN T4 /I VAC /O /H DX22
Add this to the bottom of your .tmm (macro) file:
VAC = F8
If you do want to give this a try be my guest, click here.
Thank you again to Dee-Jay for sharing his template and getting me started on this.
to this:
in the .tmj:
Rem ### Map F11 to COMMS down (UHF) for Voice Activated Commands
BTN DX21 /I VACand also added this to the .tmm:
VAC = F11I guess this has to do with the T4 modifier that I don’t use.
I actually don’t know how to use Foxy but I gave it a try…Could you please give me a hand on this?
Thanks!
P-Cube. -
Now you’ve said you’re using Kukki’s profile, but you’ve not said which Cougar file you’re using so I’m guessing here based on what you’ve typed.
There is no T4 modifier in my file; T4 is the name of the button, in this case IFF in.
If you want to change Cougar button 21, aka button T3, then modify my code as follows:
BTN T3 /I VAC /O /H DX21 ```What this means is when button T3 is pressed it sends a DX21 code unless the S3 (pinky) button is held in when it will send an F11 keypress as per your macro file (VAC = F11). Now one other thing to note is that it will send **one** F11 keypress as I have VAC Profile Activation set to **Arm** in VAC Builder as I find that gives me the best results. So when you want to use VAC you use the shifted UHF button on the throttle to 'arm' VAC and then speak immediately afterwards. I find it very reliable.
-
Hi Darkman, thanks for your reply.
I´m using Dunc´s profile for the Cougar.
I´ve tried to copy your code in the .tmj but this is not working, here´s a copy of my .tmj file:Rem # Dunc_DX.tmj, version 1.0, 2011-08-17 Rem # To be used together with all other Dunc_DX files! Rem ### Make sure to use the correct TMM file: USE MDEF Dunc_DX.tmm Rem ### Disable any mouse functionality on the Cougar (e.g. microstick): USE ZERO_MOUSE DISABLE MOUSE Rem ### Map ALL Cougar buttons and hats to their default DirectX buttons: USE ALL_DIRECTX_BUTTONS Rem ### Just FYI, by using ALL_DIRECTX_BUTTONS, the following DX values will get assigned: Rem ### (this is purely Foxy functionality and has nothing to do with BMS) Rem # TG1 = DX1 (Trigger 1st Detent) Rem # S2 = DX2 (Pickle) Rem # S3 = DX3 (Pinky) Rem # S4 = DX4 (Paddle) Rem # S1 = DX5 (MSL Step) Rem # TG2 = DX6 (Trigger 2nd Detent) Rem # H1U = POV Up Rem # H1R = POV Right Rem # H1D = POV Down Rem # H1L = POV Left Rem # H2U = DX7 (TMS Up) Rem # H2R = DX8 (TMS Right) Rem # H2D = DX9 (TMS Down) Rem # H2L = DX10 (TMS Left) Rem # H3U = DX11 (DMS Up) Rem # H3R = DX12 (DMS Right) Rem # H3D = DX13 (DMS Down) Rem # H3L = DX14 (DMS Left) Rem # H4U = DX15 (CMS Up) Rem # H4R = DX16 (CMS Right) Rem # H4D = DX17 (CMS Down) Rem # H4L = DX18 (CMS Left) Rem # T1 = DX19 (Cursor Enable) Rem # T3 = DX20 (VHF) Rem # T2 = DX21 (UHF) Rem # T4 = DX22 (IFF In) Rem # T5 = DX23 (IFF Out) Rem # T6 = DX24 (Uncage) Rem # T7 = DX25 (DGF Override) Rem # T8 = DX26 (MSL Override) Rem # T9 = DX27 (Speedbrakes Open) Rem # T10 = DX28 (Speedbrakes Close) BTN T3 /I VAC /O /H DX21 Rem ### Now, BMS can handle exactly ONE function for each button/hat position for the UNSHIFTED position (without Pinky/S3), Rem ### and exactly ONE function for each button/hat position for the SHIFTED position (with Pinky/S3). Rem ### So whenever we want to have only ONE function for each position, we don't need to do anything here in the Foxy profile Rem ### anymore, we will cover that completely in the BMS keyfile. Rem ### All that we still need to cover HERE are special cases where we want to have e.g.: Rem ### a) more than one function at the same time, Rem ### b) toggle/alternate between different functions, Rem ### c) create functions that are not meant for BMS, but for other programs (e.g. TrackIR) Rem ### NOTE: Whenever we override one of the default ALL_DIRECTX_BUTTONS assignments, we need to make sure that we Rem ### manually add the DX mapping again for the positions that we NOT want to override (because they are lost otherwise). Rem ### For example, if we only want to override e.g. a SHIFTED position, we need to manually map the UNSHIFTED position back Rem ### to whatever DX mapping was there by default. See the TG1 below for an complete example. Rem ### Trigger 1st Detent SHIFTED (/I) should be used to toggle between padlock and 3D view. As BMS can not toggle, we need Rem ### to create the toggle here as usual, using /I to indicate that this should be for the SHIFTED layer, and then add the two toggle Rem ### positions with /T. Rem ### However, as we now did override TG1 for /I, TG1 for /O will be reset to "nothing" autmatically by Foxy. But we want to Rem ### keep the default DX assignment, hence we need to add it back manuall using /O /H and the DX mapping from the list above. REM ### Additionally, we will keep keep the state of TG1 UNSHIFTED in a logical flag for TG2 (see below). BTN TG1 /I /T Padlock_AA /T 3D_Cockpit /O /H {DX1 X1} Rem ### Trigger 2nd Detent SHIFTED (/I) should do nothing to avoid firing the guns accidentally while toggling between padlock and Rem ### 3D_cockpit view. Usually, we can map this in the BMS keyfile directly. However, as soon as we release the pinky switch, Rem ### BMS will immediately detect that TG2 is pressed and start firing. So what we do here is make sure that BMS only sees TG2 Rem ### when it has been reached by passing only over TG1 (and not Pinky+TG1) before. BTN TG2 ^ DEF X2 TG2 AND X1 BTN X2 /H DX6 Rem ### The Paddle should do two things at the same time: Rem ### a) the normal AP override (which is done by BMS DX assignment, hence we just use the default DX mapping from the list), Rem ### b) wheelbrakes Rem ### To make sue that both commands are done at the same time, we use the curly brakets to tie them together. Rem ### Because we did not override /I or /O, we don't need to do anything else here, the rest will be in the BMS keyfile. BTN S4 /H {DX4 Wheelbrakes} Rem ### Because we mapped the microstick (radar cursor) to use analog axis in the HOTAS CCP, the toe brake axis can only be Rem ### used with digital statements now. Hence we will simply issue and hold a "Wheelbrake" keystroke whenever either of Rem ### the toe brakes is pushed down more than 10%. LBRK 5 2 (0 10 100) ^ (/H Wheelbrakes) RBRK 5 2 (0 10 100) ^ (/H Wheelbrakes)
And the .tmm file:
Rem # Dunc_DX.tmm, version 1.0, 2011-08-17 Rem # To be used together with all other Dunc_DX files! Rem ### To avoid side effects, it is good practice to use SINGLE keystrokes for macros only. Rem ### So whenever possible, avoid doing things like "Shift + Key" and use only "Key" instead. Rem ### This macro file will ONLY contain keyboard mappings. Everything that will be mapped Rem ### by pure DirectX in the BMS keyfile will NOT show up here. Padlock_AA = 4 3D_Cockpit = 3 Wheelbrakes = k VAC = F11
I am using the ARM feature in VAC which is indeed more reliable than the others imo.
thanks again!
-
OK, now I understand what you’re using we can hopefully sort this out.
Dunc_DX already has shifted functions on the UHF/VHF buttons in BMS. So first of all you need to clear the shifted UHF/VHF functions inside BMS, so that BMS does not do anything here at all (and Foxy can do the actual work). To clear the functions simply change your current BMS keyfile lines:
AWACSDeclare 275 -1 -2 0 0x0 0 AWACSRequestPicture 276 -1 -2 0 0x0 0 ```to
SimDoNothing 275 -1 -2 0 0x0 0
SimDoNothing 276 -1 -2 0 0x0 0Now the AWACS stuff is gone and you're free to use the keys in Foxy. You've already changed your macro (.tmm) file so that's fine as it is. Go back to the original unmodified Dunc_DX joystick (.tmj) file in Foxy and add the following lines _after_ the end of the text (after the LBRK and RBRK lines):
Rem ### Map F11 to COMMS down (UHF) for Voice Activated Commands
BTN T2 /I VAC
/O /H DX21You can also now use the T3 (VHF) button with the S3 (pinky) button held in if you wish. I use it for TeamSpeak (as a backup for IVC) and you can set that up in TeamSpeak without putting any additional lines in Foxy. Just go to Settings > Options > Hotkeys and make sure you select Direct Input (drop down box in the bottom right corner) [http://img541.imageshack.us/img541/5536/teamspeakz.jpg](http://img541.imageshack.us/img541/5536/teamspeakz.jpg)
-
all right so I’ve modified the Dunc_DX key file located in C:\Falcon BMS 4.32\User\Joystick\Cougar\Dunc_DX and changed
AWACSDeclare 275 -1 -2 0 0x0 0
AWACSRequestPicture 276 -1 -2 0 0x0 0
to
SimDoNothing 275 -1 -2 0 0x0 0
SimDoNothing 276 -1 -2 0 0x0 0then imported the original Dunc_DX.tmj from C:\Falcon BMS 4.32\User\Joystick\Cougar\Dunc_DX to C:\Program Files (x86)\HOTAS\Files which I opened in Foxy and I’ve added
Rem ### Map F11 to COMMS down (UHF) for Voice Activated Commands
BTN T2 /I VAC
/O /H DX21after the lines
LBRK 5 2 (0 10 100) ^ (/H Wheelbrakes)
RBRK 5 2 (0 10 100) ^ (/H Wheelbrakes)but still no joy…
situation is now:
-When pressing UHF and saying “Tower Inbound” in basic handling TE (Balkans Theater) I get the comm screen poping up but the command isn’t recognized and the screen only pops up once. I tried by pressing and talking 1 sec later and other ways of talking and this is not a problem with the command not being recognized as it is working perfectly in the VAC Builder test phrase.Sorry for being a PITA Darkman but you’ve really helped me so far, don’t leave me! haha.
Thanks.
-
You need to modify your current keyfile, i.e. the one you are currently using in BMS > Settings > Controllers. It should be located in your \Falcon BMS 4.32\User\Config folder. Changing the original Dunc_DX.key file in the User\Joystick\Cougar\Dunc_DX folder will not change the file in your User\Config folder.
Have you downloaded the updated profile from Foxy to your Cougar?
Can you get the commands to work in Notepad? If you open Notepad and then press S3 (pinky) + UHF and then give the command 'Tower Inbound’ you should see the corresponding characters ‘t1’ appear in Notepad. If they do, the problem is in BMS (see above to check you’ve edited the .key file that BMS is actually using). If they don’t appear in Notepad then it’s a problem with VAC (though you say you’ve tested that) or your Cougar (see above to check you’ve downloaded the updated .tmj file to your HOTAS).
-
Thanks Darkman! it’s working fine now!
the only thing is that I would like to have is to not have to press pinky + UHF but only UHF.
what do I need to modify for this to work?thanks again!
-
Do you not fly multiplayer? I use the UHF transmit so much I can’t imagine mapping it to anything else.
First you need to clear the unshifted UHF function inside BMS. To clear the functions simply change your current BMS keyfile line:
SimTransmitCom1 19 -1 -2 0 0x0 0 ```to
SimDoNothing 19 -1 -2 0 0x0 0
Edit your current modified joystick (.tmj) file in Foxy to change the DX21 into VAC like below:
Rem ### Map F11 to COMMS down (UHF) for Voice Activated Commands
BTN T2 /I VAC
/O [b]VAC[/b]This way it will work whether you press the pinky button or not.
-
I don’t fly multiplayer, even if I’d like to but I’m affraid I’m not ready for this yet.
I didn’t have time to try your solution yet but will do it in the next couple of days, hopefully!
Thanks anyway for the help you provided!
-
bad news Darkman…
I couldn’t find the line
SimTransmitCom1 19 -1 -2 0 0x0 0
in the keyfile so I didn’t change anything.I changed
Rem ### Map F11 to COMMS down (UHF) for Voice Activated Commands
BTN T2 /I VAC
/O /H DX21in my foxy file to
Rem ### Map F11 to COMMS down (UHF) for Voice Activated Commands
BTN T2 /I VAC
/O VACbut when I send the file to the Cougar it gives me an error message that the cougar isn’t available.
After this error message, the Cougar go unrecognized by my system (it was working fine before the message) and I have to reboot it in order to get it back to work.
I have tried this several times and it gives me the same result.Any ideas?
sorry for being a PITA… :S