Again, sorry for the delay, but I am really happy to report that the error didn't show on my flight today. I updated to version 3.2.1.0 and applied the patch for 3.1.2.2,  and the flight went flawlessly until we were told to contact approach. From that point onward, the FO didn't seem to know which frequency to dial in. When directed to contact approach, the FO just re-contacted the controller we were talking to already, without attempting to change the frequency. Later, when asked to set tower to COM 1, the FO asked for the frequency. I believe this behavior is not new, though.

But man, when the FO works correctly, as it did today for the most part, flights are a real joy!

On 4/13/2025 at 4:38 PM, d.tsakiris said:

Again, sorry for the delay, but I am really happy to report that the error didn't show on my flight today. I updated to version 3.2.1.0 and applied the patch for 3.1.2.2,  and the flight went flawlessly until we were told to contact approach. From that point onward, the FO didn't seem to know which frequency to dial in. When directed to contact approach, the FO just re-contacted the controller we were talking to already, without attempting to change the frequency. Later, when asked to set tower to COM 1, the FO asked for the frequency. I believe this behavior is not new, though.

But man, when the FO works correctly, as it did today for the most part, flights are a real joy!

From now on, when you have a minor issue related to Fo handling of PF3 ATC, I suggest you send the "Clearance.log" after the flight is finished and before it gets overwritten.

The log is at the heart of the interfacing. There could be new abbreviations introduced lately that the Fo isn't trained to handle causing this sort of issues. Like collecting frequencies to dial and such

Edited April 30, 20251 yr by FS++

On 4/30/2025 at 8:58 PM, FS++ said:

From now on, when you have a minor issue related to Fo handling of PF3 ATC, I suggest you send the "Clearance.log" after the flight is finished and before it gets overwritten.

Thanks, I zip all logs after each flight, so I still have the files in question and will send them to you via email

On 4/13/2025 at 4:38 PM, d.tsakiris said:

Again, sorry for the delay, but I am really happy to report that the error didn't show on my flight today. I updated to version 3.2.1.0 and applied the patch for 3.1.2.2,  and the flight went flawlessly until we were told to contact approach. From that point onward, the FO didn't seem to know which frequency to dial in. When directed to contact approach, the FO just re-contacted the controller we were talking to already, without attempting to change the frequency. Later, when asked to set tower to COM 1, the FO asked for the frequency. I believe this behavior is not new, though.

But man, when the FO works correctly, as it did today for the most part, flights are a real joy!

Latest version V3.1.3.1 should address this glitch. Download using same link as usual

So...unfortunately, I have to report that the new version seems to make things worse. The FO didn't know anything about the ATIS or tower frequencies at the departure airport. Later frequency changes were read back correctly to ATC, but after setting the next frequency, FO didn't make any attempt to contact the next facility - I had to ask each time. Ah, I believe the switch to approach worked - but then the sim CTD.

Due to technical issues, this time I don't have logs, but I will try do do another flight coming week-end.

Today's flight was similar. FO knew nothing about the departures frequencies. When advised by ATC, FO would sometimes dial in the new frequency, sometimes not. FO never attempted to contact after a frequency change. This time, I have (almost) all the PF3 logs.

I checked, and the PF3_MCE.ini is there, with Active=1. Something else I can look at on my side?

Today I might have noticed something regarding the issue with the FO contacting the next facility without changing frequencies first: I think this might only happen when the next facility doesn't have a name. So: "Contact Vienna radar" works, but "contact radar" doesn't. The FO reads both back the same way, but in the latter case he doesn't dial in the next frequency before. Does that make any sense? This was with V3.1.2.2.