Roacher Posted October 10, 2020 Share Posted October 10, 2020 Not sure if I'm doing something wrong but, when I call up any radio command other than to my wingman or the ground crew, nothing happens: no pilot voice; and no audible responses from ATC; JTAC; tanker; or AWACS. Again, my pilot can communicate normally with wingman/flight and ground crew, and even with the supercarrier (not authorized to land). With other modules, including the A-10C, the radio commands work as they should. Every now and then while getting on without full radio commands, the pilot will blurt out a radio command, such as "inbound..." as if it was caught in a pipeline or something. I've tried re-installing A-10C Tank Killer, and repairing DCS, but no joy. Link to comment Share on other sites More sharing options...
MAXsenna Posted October 10, 2020 Share Posted October 10, 2020 Not sure if I'm doing something wrong but, when I call up any radio command other than to my wingman or the ground crew, nothing happens: no pilot voice; and no audible responses from ATC; JTAC; tanker; or AWACS. Again, my pilot can communicate normally with wingman/flight and ground crew, and even with the supercarrier (not authorized to land). With other modules, including the A-10C, the radio commands work as they should. Every now and then while getting on without full radio commands, the pilot will blurt out a radio command, such as "inbound..." as if it was caught in a pipeline or something. I've tried re-installing A-10C Tank Killer, and repairing DCS, but no joy.@hornblower793 has found a strange issue when we use VAICOM, which seems similar to your issue. Try to changing the callsign in Mission Editor from Hawg/Boar etc (pigs names), to a something else like Colt etc. For some strange reason that fixed it for us. Would be very fun if this helps you! Cheers! Sent from my ANE-LX1 using Tapatalk Link to comment Share on other sites More sharing options...
Roacher Posted October 10, 2020 Author Share Posted October 10, 2020 What do you know!?! Hey, that worked, thanks for the help. Link to comment Share on other sites More sharing options...
MAXsenna Posted October 10, 2020 Share Posted October 10, 2020 What do you know!?! Hey, that worked, thanks for the help.Whoa! Cool, that means it's not only when using VAICOM, and we'll probably have a fix shortly. Thanks! Sent from my ANE-LX1 using Tapatalk Link to comment Share on other sites More sharing options...
Andartu Posted October 11, 2020 Share Posted October 11, 2020 @hornblower793 has found a strange issue when we use VAICOM, which seems similar to your issue. Try to changing the callsign in Mission Editor from Hawg/Boar etc (pigs names), to a something else like Colt etc. For some strange reason that fixed it for us. Would be very fun if this helps you! Cheers! Phew.. drove me crazy as well. Thanks very much for this. Now it works :thumbup: Link to comment Share on other sites More sharing options...
GunSlingerAUS Posted October 11, 2020 Share Posted October 11, 2020 Damn DCS. Anti-bovine trash. Bovine lives matter! Intel 11900K/NVIDIA RTX 3090/32GB DDR4 3666/Z590 Asus Maximus motherboard/2TB Samsung EVO Pro/55" LG C9 120Hz @ 4K/Windows 10/Jotunheim Schiit external headphone amp/Virpil HOTAS + MFG Crosswind pedals Link to comment Share on other sites More sharing options...
Recommended Posts