jiblet Posted April 23, 2012 Posted April 23, 2012 I'm just trying to get VAC set up with Warthog (never tried it before) and I while it seems to be fine when I test the profile, it's not picking anything up when I actually play the game. I should note that VAC says "DCS profile is loaded and voice is on" when I hover over the icon, and I really am pressing the button so that it is listening for a command! Since it seems to work flawlessly in the test mode I can only assume I'm doing something really dense.
Fish Posted April 24, 2012 Posted April 24, 2012 (edited) I'm just trying to get VAC set up with Warthog (never tried it before) and I while it seems to be fine when I test the profile, it's not picking anything up when I actually play the game. I should note that VAC says "DCS profile is loaded and voice is on" when I hover over the icon, and I really am pressing the button so that it is listening for a command! Since it seems to work flawlessly in the test mode I can only assume I'm doing something really dense. Have you looked at this thread. If your still having trouble, post your profile and i'll have a look. http://forums.eagle.ru/showthread.php?t=79868 Edited April 24, 2012 by Fish Fish's Flight Sim Videos [sIGPIC]I13700k, RTX4090, 64gb ram @ 3600, superUltraWide 5120x1440, 2560x1440, 1920x1080, Warthog, Tusba TQS, Reverb VR1000, Pico 4, Wifi6 router, 360/36 internet[/sIGPIC]
CubPilot Posted April 24, 2012 Posted April 24, 2012 (edited) If you have a key set up in VAC to activate VAC it might be that you are letting go of the key too soon. VAC needs enough time to complete the command. It may also be a good idea to check that VAC System exe (or shortcut) is set to run as administrator if using Win7 (& maybe Vista). Edited April 24, 2012 by CubPilot [sIGPIC][/sIGPIC] Win7 Pro 64 | Asus Rampage III Extreme |Swiftech H2O cooled: CPU, Video, N. Bridge | i7 980X EE @4.5GHz | 16 GB DDR3 @1726 MHZ | AMD R9 290X 4GB DDR5 +EK H2O block+Backplate | BenQ XL2730Z 2560x1440 @144Hz | Samsung 850 EVO SSD 500GB | 2 - Samsung HD 1TB | Pinoeer BD-RW | ASUS Xonar DX 7.1 PCIe Audio | CoolerMaster Haf-X case | PC Power & Cooling Silencer 760W PS | HOTAS Cougar w/Evenstrain Mod | HOTAS Warthog | TM RCS Rudders + Mods | TM MFD's w/monitors | TrackIR5
GregP Posted April 24, 2012 Posted April 24, 2012 Are you sure that the key you're using as PTT is not already mapped to something else within DCS? A conflict like that might prevent VAC from working correctly.
Fish Posted April 24, 2012 Posted April 24, 2012 Are you sure that the key you're using as PTT is not already mapped to something else within DCS? A conflict like that might prevent VAC from working correctly. I agree, After trying the PTT key each way, the one with the least complications turned out to be the 'ARM' option, which is what i use now. Fish's Flight Sim Videos [sIGPIC]I13700k, RTX4090, 64gb ram @ 3600, superUltraWide 5120x1440, 2560x1440, 1920x1080, Warthog, Tusba TQS, Reverb VR1000, Pico 4, Wifi6 router, 360/36 internet[/sIGPIC]
CubPilot Posted April 24, 2012 Posted April 24, 2012 I got around any conflicts with DCS A-10C key assignments by using "F14" as the VAC mic switch. Then I used a small AutoHotKey script to map F14 to the UP position of the Warthog throttle. Doing it this way preserves the Warthog plug & play feature, no need for T.A.R.G.E.T ! In VAC Profile Activation Keys I set the first box to "None" next box to "F14" and ticked Default. It acts just like a mic switch, hold down to say the command (+ a bit of time for the command to complete), release to close mic when done. Load that AHK script just before A-10C and go fly. :D If anyone is interested in this method I can attach the files. [sIGPIC][/sIGPIC] Win7 Pro 64 | Asus Rampage III Extreme |Swiftech H2O cooled: CPU, Video, N. Bridge | i7 980X EE @4.5GHz | 16 GB DDR3 @1726 MHZ | AMD R9 290X 4GB DDR5 +EK H2O block+Backplate | BenQ XL2730Z 2560x1440 @144Hz | Samsung 850 EVO SSD 500GB | 2 - Samsung HD 1TB | Pinoeer BD-RW | ASUS Xonar DX 7.1 PCIe Audio | CoolerMaster Haf-X case | PC Power & Cooling Silencer 760W PS | HOTAS Cougar w/Evenstrain Mod | HOTAS Warthog | TM RCS Rudders + Mods | TM MFD's w/monitors | TrackIR5
Fish Posted April 26, 2012 Posted April 26, 2012 .......I got around any conflicts with DCS A-10C key assignments by using "F14"........ Used your idea in foxy. Worked a treat. (dident realise we have these keys F13-F24 available to us. nice find). Code from foxy BTN S4 /I Teamspeak /O /P USB(D69) rem hold F14 /R USB(U69) rem release F14 Fish's Flight Sim Videos [sIGPIC]I13700k, RTX4090, 64gb ram @ 3600, superUltraWide 5120x1440, 2560x1440, 1920x1080, Warthog, Tusba TQS, Reverb VR1000, Pico 4, Wifi6 router, 360/36 internet[/sIGPIC]
CubPilot Posted April 27, 2012 Posted April 27, 2012 (edited) Used your idea in foxy. Worked a treat. (dident realise we have these keys F13-F24 available to us. nice find). Code from foxy BTN S4 /I Teamspeak /O /P USB(D69) rem hold F14 /R USB(U69) rem release F14 Glad you got something useful from my post. I figure that the F13 thru F24 keys will be safe from ever being used by DCS for key bindings because they aren't on a normal keyboard (at least not that I'm aware of). I never thought of doing something similar in Foxy for the Cougar. Seems that you have expanded the "envelope" of using these keys. Edited April 27, 2012 by CubPilot [sIGPIC][/sIGPIC] Win7 Pro 64 | Asus Rampage III Extreme |Swiftech H2O cooled: CPU, Video, N. Bridge | i7 980X EE @4.5GHz | 16 GB DDR3 @1726 MHZ | AMD R9 290X 4GB DDR5 +EK H2O block+Backplate | BenQ XL2730Z 2560x1440 @144Hz | Samsung 850 EVO SSD 500GB | 2 - Samsung HD 1TB | Pinoeer BD-RW | ASUS Xonar DX 7.1 PCIe Audio | CoolerMaster Haf-X case | PC Power & Cooling Silencer 760W PS | HOTAS Cougar w/Evenstrain Mod | HOTAS Warthog | TM RCS Rudders + Mods | TM MFD's w/monitors | TrackIR5
Recommended Posts