OnCourse Software

RALF9636 wrote:

dmarch wrote:

That particular author (German pilot #1) took it upon himself to record 'Langen Rader' because, rightly or wrongly, the script at the time specified 'Dusseldorf Radar'. Had I spotted it back then I would have told him to change it.

Brave guy!

Sneaky I think

Hi,

quite an interesting topic!

From what details does PF3 select the call sign from the AI aircraft?

For example I have these entries in my customized aircraft.cfg:

[fltsim.XX]
title=OSP ATR 72-200 ASL Airlines Ireland EI-SLR
sim=ATR72
model=
texture=ASL Airlines Ireland EI-SLT
atc_airline=CONTRACT
ui_manufacturer=ATR
ui_type=72-201F
ui_variation=ASL Airlines Ireland EI-SLR
description=AI ATR72-200 by Oskari Syynimaa (OSP) :: Repaint by Elias Merino
atc_parking_codes=ABR
atc_parking_types=CARGO

The call sign to be used is CONTRACT. The airline was Air Contractors before and now is called ASL Airlines.

Where does PF3 take the info from? Will it work anyway if ASL Airline Ireland is not included in the airline list of PF3?

I think I haven't understood it well yet how the selection works.

The default AI uses the atc_airline entry.

All the information we use is taken from the AI Traffic tables supplied by FSUIPC

Hallo Dave,

trafficlook.exe gives me the call signs. Do you mean other tables?



Cheers

Yes, I said I read them from the AI Traffic tables supplied via FSUIPC not Trafficlook

Are these tables accesible to the user or is it exchanged only between these programs. I would like to see what is there to possible adjust my settings.

Thanks!

No you access it programatically.

I know there used to be a utility offered on Pete Dowsons forum for reading FSUIPC data but not sure if it's still available.

Trafficlook only sees shortened names, but in PF3/Logs/Atc_Chat.log the full names are logged.
I don't know right now if they are encoded like other logs, but if they are you can send the log to Dave.

If you have an airline that is not identified correctly, you can add your own mappings to Data/Callsigns_Map.dat
It currently contains:

Code: Select all Contract,102,15

So it already knows it in general, but there are some cases where AI traffic has other names, e.g.:

Code: Select all KLM,32,7 KLM Royal Dutch Airlines,32,7

The second line was added in PF3 to support KLM flights from UT2.

dmarch wrote:

No you access it programatically.

I know there used to be a utility offered on Pete Dowsons forum for reading FSUIPC data but not sure if it's still available.

Maybe in the FSUIPC SDK ?

Aibridge? This is available there, but not sure if this is the tool.