Sniper2Spades Posted yesterday at 12:56 PM Posted yesterday at 12:56 PM During a mission departing from Nellis AFB with the A-10C II, I encountered a bug involving the aircraft's radios. After setting both radios to their respective tower frequencies, the ARC-210 radio automatically switches to the ARC-164 UHF frequency at a specific moment. Here’s the sequence of actions performed: • Set frequency 132.55 on ARC-210 • Set frequency 327.00 on ARC-164 • Requested taxi clearance on 327.00 (ARC-164) • After receiving taxi clearance, I requested takeoff clearance on 132.55 (ARC-210) At the exact moment I made the takeoff request via the in-game radio menu, the ARC-210 frequency was automatically overwritten and switched to 327.00, matching the ARC-164. I’m attaching both a video and a track file to illustrate the issue. Thanks Sniper radio_bug.trk 2025-08-20 14-41-23.mkv 1
Yurgon Posted yesterday at 01:37 PM Posted yesterday at 01:37 PM Excellent report! 30 minutes ago, Sniper2Spades said: At the exact moment I made the takeoff request via the in-game radio menu, the ARC-210 frequency was automatically overwritten and switched to 327.00, matching the ARC-164. I'm pretty sure that has to do with the game setting "Easy Communication". With this setting enabled, radios will automatically tune to the proper frequency when you initiate a radio call. So the ARC-210 doesn't actually match the ARC-164 here (well it does, but it couldn't care less which freq is set in the ARC-164 is my point ), it just switches to the UHF freq for Nellis Tower, because that's Tower's default frequency. It doesn't necessarily make sense that it tunes to the UHF freq when you've already dialed in the VHF AM freq, but Easy Comms is much older than the multi-mode ARC-210, which was a relatively late addition to the A-10C II (you wouldn't see this happening in the A-10C legacy module, where the front radio is another ARC-186, just like the aft radio). Also, when you pay close attention, on your second radio call ("Request takeoff"), you had pushed Mic Switch Forward and were talking through the ARC-210; the written message in the top right corner clearly reads "ARC-210" in this case. So, long story short, when you disable "Easy Communication" in the game's options, this will no longer happen. Or, to cross check, you can do the same sequence of events, but before you initiate the "Request takeoff" call, switch the ARC-164 to any other freq. The ARC-210 is still going to tune Nellis Tower on UHF, regardless of what's set in the ARC-164. 1
ED Team Solution BIGNEWY Posted yesterday at 01:49 PM ED Team Solution Posted yesterday at 01:49 PM You can find the easy comms option in the mission options 2 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Sniper2Spades Posted 23 hours ago Author Posted 23 hours ago Thank you, and sorry—I hadn’t fully understood the Easy Comm option. I’m sorry for wasting your time 1
MAXsenna Posted 19 hours ago Posted 19 hours ago 4 hours ago, Sniper2Spades said: Thank you, and sorry—I hadn’t fully understood the Easy Comm option. I’m sorry for wasting your time Just stop using and forget about it. It's a relic from FC level planes, and only works with those unless you have enabled easy comms. Learn the radios in the modules. It's fun and gives you a better understanding of how everything works. Cheers!
Sniper2Spades Posted 4 hours ago Author Posted 4 hours ago I've never used this option before. I think that, having run a test on an old mission where I had previously experimented with radio parameter settings using the X:cockpit functions, it was active. So it was my mistake not to check the options before reporting it. I had never considered it and didn’t understand how it worked simply because it’s called 'Easy'. I apologize again to those who spent time on this issue. 1
Yurgon Posted 4 hours ago Posted 4 hours ago 10 minutes ago, Sniper2Spades said: I apologize again to those who spent time on this issue. Why would you? It's an honest question and you wrote a super detailed report with all pertinent information available right away. The issue got squared away in no time, and if someone else happens to have the same question, chances are they find this thread when they search for similar reports. This is what forums are for. 1
Recommended Posts