Printable View
Hello everyone,
Today controlling on LSAS_G_CTR. Three pilots flying on MSFS2020 were not able to contact me. Apparently they cannot choose my frequency 134.325, but end up on 134.324 (See screenshot).
Any ideas what we should do ?
Thanks,
Luca
Attachment 5054
There should be a command in vpilot (.com1 XXX.XXX) I believe that tunes you into the desired frequency. Might be a SimConnect issue, I'm not sure.
I just tried dialing that frequency, it works without any problems... Otherwise I would also suggest the .com1 command.
I discussed with my friend who was flying on Thursday and he had the same issue. He said he didn't run any of the programs as admin. Idk if Marco does it too but that might be the reason.
I just remembered that some pilots were using the A320, not sure about the others
Have they tried 134.320?
Maybe a compatibility issue with 5-digits COMs from older FSs?
Have the same Issue with the A20N in MS2020... That's way I using the .com1 Frequency direct in VPilot.
Apparently the A20N is causing a lot of problems. That was also a part of the problem for the chaos last Tuesday event.
Isn't there somewhere a bug report tool for MSFS2020? I mean it is still in beta... (the sim just left alpha stage a few days before release...)
I've been doing like 6 flights already on Vatsim, no problems at all.Quote:
Originally Posted by Jonas Kuster
I've done a few flights already on Vatsim too with the neo. The knowing Issue in A20NX from my experience are:
- Amend Flight Plan delete Waypoints or make a new flight plan with other waypoints.
- Frequencies can't entered via FMC correctly. Workarround is com1
I've reported this things with an Zendesk Ticket..
Thank you Thomas !