Sniper2Spades

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.

Thank you, and sorry—I hadn’t fully understood the Easy Comm option. I’m sorry for wasting your time

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

Thank you so much, for your contribution to the community!!!

Confidently waiting for a plan

I also have two cubesim monitors. Before starting the lua file, do these checks: 1) monitor resolution settings in window 800x600 or 600x600 (I don't remember well) 2) the two monitors have a built-in video card that you can adjust both in terms of size and position (the size must be consistent with the one set in window); these adjustments can be made with the side buttons of the monitors