EDIT: Microsoft has fixed this issue about 90-95%. There are still some stock airplanes whose radios do not work properly such as the C152. While the C152 can receive dual comms, it cannot only listen to COM1 or COM2. It’s like they’re both always on regardless of what the buttons indicate.
Currently, the radios don’t function properly in that there isn’t a way to monitor both COM1 and COM2 while on the PilotEdge live air traffic control network (X-Plane, FSX, FS2004 and P3D all work fine). This goes for G1000 aircraft, and airliners. A few of the steam gauge aircraft work, but you cannot transmit and receive simultaneously on separate radios. While the buttons exist on the cockpit panel, they don’t function correctly. This means there is no way to check an ATIS without asking to leave the frequency, nor can you monitor guard (121.5) while in flight.
It was actually functioning properly in several of the G1000 aircraft during one of the FS2020 silent updates about 5-6 weeks ago, but stopped working again soon after.
PilotEdge staff would be glad to work with you all on this issue.
You bring up a good point about monitoring 121.5. I don’t think any crashes trigger the ELT. Having a functional ELT would allow organized (multiplayer?) search and rescue teams. Random failures can be enabled before each flight. But there is no way to contact ATC with a MAYDAY. These features are not needed in MSFS but they are necessary IRL when things break badly. (Fire engines are modeled in many of the larger airports. But if a plane crash lands or skids off the runway,is there a response from the fire department? No!)
PilotEdge has fully implemented the guard frequency. Have an emergency? Call ATC on guard. Lose radio range coverage? Call ATC on guard. It’s all available on the PilotEdge network.
I would really like to see this fixed ASAP. While flying on the PE network it’s a total immersion killer to have to go look up the ATIS information by hand instead of just tuning COM2 to pickup the Arrival ATIS. Not to mention How easy it will be when flying through airspace with Bravos, Deltas, and Charlies all over the place. It would be a huge QOL improvement to have 3 other frequencies on standby.
The G1000 has no “BOTH” button, because it has separate MIC and audio buttons for both COM1 and COM2.
If you set COM_RECEIVE_BOTH via simconnect / fsuipc, the radios work fine in vPilot (vatsim) and likely PilotEdge client and IVAO equivalents too.
You can then just use the monitor buttons on the G1000 audio panel to select which radio to listen to (or both) and use the MIC buttons to select where you talk to (and of course the mic selector enables audio to that radio as well, so you cannot talk to COM1 and listen to COM2 or vice versa)
The G1000 should just enable the RECEIVE_BOTH simconnect variable when both audio buttons are active, so external apps that check it would be satisfied.
As an interim fix, when we wait on Asobo (and maybe if we can manage a patch to Working Title G1000) the pilot clients could implement this setting on their side, I think it should work.