Jean-Luc DUMOULIN Posted March 21, 2022 at 08:52 AM Posted March 21, 2022 at 08:52 AM Hello to the staff, hello to all For more than a year I have been using, on the recommendation of VatFrance, the Swift client to communicate on the Vatsim network. This was going smoothly until now when I was flying in US airspace. For several weeks, I can no longer communicate on the frequencies indicated by the air traffic controllers in their overflown spaces. This only concerns US controllers, everywhere else Swift works perfectly fine. Is this problem already known and do you have a solution for me to solve it? Cordially Jean-Luc [img]http://signature.cyberavia.org/DUMOULIN.Jean-Luc.png[/img] W10 + ASUS Z170 Pro Gaming|Intel Core i5 6500 3,20 GHz|16 Go DDR3 1070Mz|NVIDIA GeForce RTX 2080 Ti|Acer AL1716 + Samsung S22F350 (1) WD 1 To + WD 500Mo + SSD 840Evo 250GB + SSD 970Evo Plus 500GB Saitek Pro Flight+MCP Combo Link to comment Share on other sites More sharing options...
Andreas Fuchs Posted March 21, 2022 at 12:25 PM Posted March 21, 2022 at 12:25 PM Hi Jean-Luc, I suspect the issue lies with controllers using a channel with 3 digits after the decimal where the third digit is sometimes a "5", e.g. 121.725. For historic reason the third digit is ignored and set to "0", so clients may connect to text-channel 121.720, in the example. On your next flights, can you please test if this problem also exists with controllers that are using frequencies that have an official "0" as the last digit, e.g. 121.750 ? Does the problem exist on them as well? 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...
Recommended Posts