Hello, I have a problem with a number of callsigns. Some of them aren't recognized by the FO, which leads to him not responding to ATC by himself. If I then ask him to "acknowledge ATC", he only reads back a basic "Roger 9022" (the callsign being Wizzair 9022 in that example). This at least satisfies ATC, so I guess the right key combination is pressed.

Until now, I've encountered this behavior with the callsigns Turkish, Wizzair and All Nippon. Lufthansa, on the other hand, works without a problem, so the connection between MCE and PF3 is given. I can provide the PF3 logs if required. Thanks!

So...nobody else is seeing this?

43 minutes ago, d.tsakiris said:

So...nobody else is seeing this?

Will run a test with PF3 as soon as possible.

I don't recall whether recorded voice packs have included "Wizzair". That could explain why he only utters the flight number. Try using a TTS voice.

Hi Gerald, thanks for your reply. I don't mind him using only the flight number, but he should recognize it when ATC uses the correct callsign.

Edited February 11, 20206 yr by d.tsakiris

On 2/11/2020 at 7:52 PM, d.tsakiris said:

Hi Gerald, thanks for your reply. I don't mind him using only the flight number, but he should recognize it when ATC uses the correct callsign.

Thanks for bringing this up. It turns out it was a self inflicted issue... Let me explain..

MCE looks up "pf3.ini" for the airline name which is a number.

We then have a file in MCE installation folder "PFE_airlines.dat" (which can be opened using Notepad) to translate the number to actual airline name.

Wizzair is expected at record 101

It was written as "Wizz Air" instead of "WizzAir".

Since Fo relies on PF3 caption to work out whether a message is intended for you (and reply accordingly), it didn't match.

Windows will probably prevent you editing the file directly. Therefore, copy the file to desktop, edit it and then replace original in MCE installation folder.

File will be updated in next release.

 

Okay, thanks!