3 hours ago, Lorby_SI said:

Hello Mark,

can you please send me an email? The address is on the last page of the manual. Then I will send you a link to a new LLTX version to check out, see if I am correct about the airline naming convention - you can do that a lot faster than I can. (I already made the change to the app itself).

Thank you - but are you sure that you are not confusing LLTX with some other app? 😊

Best regards

Thanks Oliver, email sent. I am on vacation so plenty of time to test.

Mark

Works fantastic with ProATC in live mode, never seen so much traffic en-route

26 minutes ago, SierraHotel said:

Works fantastic with ProATC in live mode, never seen so much traffic en-route

Hello Mike,

how does ProATC spell out the airline code / flight number / callsign when it plays the AI chatter? Same as for Mark? (which is: an airline name that consists of two parts is often not understood by the ATC program, and instead of the flight number it reads the first couple of characters of the second part of the airline name)

Best regards

32 minutes ago, Lorby_SI said:

Hello Mike,

how does ProATC spell out the airline code / flight number / callsign when it plays the AI chatter? Same as for Mark? (which is: an airline name that consists of two parts is often not understood by the ATC program, and instead of the flight number it reads the first couple of characters of the second part of the airline name)

Best regards

I have it set to all phonetic 

11 hours ago, Lorby_SI said:

Hello Mike,

how does ProATC spell out the airline code / flight number / callsign when it plays the AI chatter? Same as for Mark? (which is: an airline name that consists of two parts is often not understood by the ATC program, and instead of the flight number it reads the first couple of characters of the second part of the airline name)

Best regards

Hi Oliver,

I have tested the new LLTX version and sent you an email.

Thank you for the opportunity!

Cheers,

Mark

To add to the discussion I have had time to search the PF3 forums and have come across the following...

”PF3 gains it's AI data from FSUIPC and if the format or name is not recognised by PF3 you will get the first part of the name given phonetically rather than hearing the correct callsign.”

We might have been looking in the wrong direction.

Regards,

Mark

3 hours ago, mwa05 said:

To add to the discussion I have had time to search the PF3 forums and have come across the following...

”PF3 gains it's AI data from FSUIPC and if the format or name is not recognised by PF3 you will get the first part of the name given phonetically rather than hearing the correct callsign.”

We might have been looking in the wrong direction.

Regards,

Mark

Hello Mark,

I don't think that FSUIPC matters. It is just another bridge that the same information is crossing. It shouldn't matter if a program takes the FSUIPC detour or reads the same information directly from SimConnect.

Just to clarify: if I understand you correctly, then the same UTL aircraft model's information is spelled out differently by PF3 depending on how it was created (=by UTL or by LLTX)? So I will have to write yet another tool to find out how UTL is setting those same variables (or if it is setting them at all). Problem is, that I cannot know what PF3 is expecting, so it is bascially trial&error.

I ran tests yesterday in Simulator AI mode, where the same variables are set in exactly the same way, and default ATC calls them by their actual airline names. So it is not my airline database, I suppose.

Best regards