minimi66 Posted April 9, 2015 Posted April 9, 2015 Hi, I've just got back into DCS A-10C and DCS World in general after a couple of years away from it due to being busy with other things. In the process of getting everything set back up again i have hit a problem with getting Fish's VAC A10C profile to work via my TM Warthog Throttle Mic Up button (3) and using the AutoHotkey WH_DCS_A-10_VAC_PTA.exe script posted by CubPilot? Basically, when testing in VAC Builder everything works perfectly other than the odd misunderstood phrase here and there. However, in A-10C when i key the PTA button and say a phrase from Fish's accompanying manual of usable phrases (as per his profile) the result is that i get kicked into the F5 Nearest Aircraft View and no radio message gets sent to my Wingman. Not sure whether this is a VAC or VAC Profile issue or an in-game Controls > Options problem. I am pretty mush using all the default HOTAS and Keyboard commands and haven't changed very much at all and nothing to do with Comms or View Commands. Any assistance or ideas would be appreciated? Many thanks. :thumbup: Windows 10 Pro 64-bit - Intel Core i9-13900K - 64GB Corsair Vengeance RAM @ 3200 MHz - ASUS TUF GAMING B660-PLUS WIFI D4 - Zotac NVIDIA GeForce RTX 4090 - 2TB INTEL NVMe SSD (Windows 10) - Samsung SSD 970 EVO Plus 1TB (DCS) - Crucial CT1000 1TB NVMe SSD - WinWing F-16EX Stick - WinWing Orion Throttle Base with both F-18 & F-16C TQS Throttle Grips - Saitek Pro Rudder Pedals - Logitech G-910 Keyboard - Logitech G-502 Lightspeed Mouse - Logitech G-533 Headset - Occulus Quest Pro VR - TrackIR 5 with Track Clip Pro
MadDog-IC Posted April 12, 2015 Posted April 12, 2015 Hi, In the process of getting everything set back up again i have hit a problem with getting Fish's VAC A10C profile to work via my TM Warthog Throttle Mic Up button (3) and using the AutoHotkey WH_DCS_A-10_VAC_PTA.exe script posted by CubPilot? Basically, when testing in VAC Builder everything works perfectly other than the odd misunderstood phrase here and there. However, in A-10C when i key the PTA button and say a phrase from Fish's accompanying manual of usable phrases (as per his profile) the result is that i get kicked into the F5 Nearest Aircraft View and no radio message gets sent to my Wingman. Any assistance or ideas would be appreciated? Many thanks. :thumbup: Sounds like it isn't sending a radio command first before the F-keys for the actual radio commands, commands should look like these below: ie (Tower 1 Inbound should have commands like) L-Alt + Numpad+ (Send by Top radio) F5 F1 F1 (Flight Engage Bandits should have commands like) L-Alt + Numpad- (Send by middle radio) F2 F2 F8 (Contact Jtac 1 on a FM channel should have commands like) L-Shift + Numpad- (Send by bottom FM radio) F4 F1 If there is no proceeding radio command as to what radio to send it via, this will cause it to issue F-keys that will now be seen as different view modes instead: Check: The 3 radio transmittion keys are bound in game, as I think I had the issue that L-Alt + Numpad- was assigned to something other that the radio within the DCS controls page for the A-10c. What keys are actually being sent by the vac voice command, should look similiar to my examples above What keys is the script looking for and/or sending. Regards, Ian. Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV). DCS Tech Support.
minimi66 Posted April 13, 2015 Author Posted April 13, 2015 Hi, I fixed the problem on Friday. In the DCS Options > Controls setup the Communications Menu keystroke "\" was present for the keyboard as well as my Throttle Button 3 which i have set up in VAC to trigger the Comms Menu in game. I cleared the "\" keyboard keystroke and just left Button 3 as the only mapped control for the Comms Menu. Clearly the Comms Menu keystroke was not being triggered in game and when i spoke a VAC command it just generated the F1, F3 etc keystrokes which was why VAC was triggering External View commands and not comms messages. That fixed it and it all now works perfectly! Thanks for all the assistance on both the threads i posted about this problem on. Stu Windows 10 Pro 64-bit - Intel Core i9-13900K - 64GB Corsair Vengeance RAM @ 3200 MHz - ASUS TUF GAMING B660-PLUS WIFI D4 - Zotac NVIDIA GeForce RTX 4090 - 2TB INTEL NVMe SSD (Windows 10) - Samsung SSD 970 EVO Plus 1TB (DCS) - Crucial CT1000 1TB NVMe SSD - WinWing F-16EX Stick - WinWing Orion Throttle Base with both F-18 & F-16C TQS Throttle Grips - Saitek Pro Rudder Pedals - Logitech G-910 Keyboard - Logitech G-502 Lightspeed Mouse - Logitech G-533 Headset - Occulus Quest Pro VR - TrackIR 5 with Track Clip Pro
Recommended Posts