Martin Aviati Posted September 3, 2020 at 07:02 PM Posted September 3, 2020 at 07:02 PM Good evening, I just had an issue with the A320 neo in the FS2020 while flying on vatsim in FS2020. I had to contact Langen on 127.720 but I wasn` t able to enter the frequency in the cockpit. While I was trying to set it to "20" it alway skipped the number 20. I was only able to set it to "15" and "25". I assume I just found a new bug in the FS2020 A320neo. Is there any other way to contact a Frequency, probably with a shortcut I could type in the vpilot software? Probably like .freq 127.720? Sadly I had to abort my online flight because of that A320 neo bug. That` s the only problem I encountered today while flying on vatsim with the FS2020. The software is running without any performance issues now. I was able to see other traffic but of course just with the liveries which are already included in the FS2020. Best regards, Martin. Link to comment Share on other sites More sharing options...
Solution Andreas Fuchs Posted September 3, 2020 at 07:20 PM Solution Posted September 3, 2020 at 07:20 PM (edited) Hello Martin, no, this is not a bug. In the real world 127.720 does not exist. The fact that we are using those strange frequencies at VATSIM is due to the fact that we are still backwards-compatible with FS9 where radios only have 2 digits after the decimal: 127.72 . If we used 127.725, pilots with FS9 would not be able to tune this frequency. To accommodate these frequencies, normally your pilot client should be cutting off the 3rd digit. Alternatively you can manually set COM-frequencies with the so called dot-commands: https://vpilot.metacraft.com/Documentation#dot-commands In your case that would be .com1 127.720 Edited September 3, 2020 at 07:24 PM by Andreas Fuchs Cheers, Andreas Member of VATSIM GermanyMy real flying on InstagramMy Twitch streams of VATSIM flights and ATC Link to comment Share on other sites More sharing options...
Martin Aviati Posted September 3, 2020 at 07:29 PM Author Posted September 3, 2020 at 07:29 PM Hi Andreas, thanks for helping me out with that issue. Next time I wiill just use the frequency 127,720 or I will try the dot commands. Thanks for the "dot-command" link. That` s very helpful. Have a nice evening, Martin. Link to comment Share on other sites More sharing options...
Ross Carlson Posted September 4, 2020 at 04:51 AM Posted September 4, 2020 at 04:51 AM Just tune 127.725, vPilot will correctly match it up with the controller on 127.720. 1 Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Tobias Dammers Posted September 5, 2020 at 05:18 PM Posted September 5, 2020 at 05:18 PM Have encountered the same thing with Flightgear. Essentially, just set the last digit to whatever goes, and it'll work. Link to comment Share on other sites More sharing options...
Recommended Posts