OnCourse Software

Hello,


I have already read about how to make ATC in PFE use the correct callsigns in one of the "sticky" threads, but it's like a workaround how to use "Qantas" instead of "Qantaslink"

But what entry in the aircraft.cfg or in the folder names does the PFE ATC read to use the proper callsign?

For example:

With PFE running (I never use the default ATC anylonger) I never hear "Lufthansa Cargo"

My entry in the aircraft.cfg is following:

[fltsim.32]
title=FSP MD-11F Lufthansa Cargo
sim=fsp_md11
model=
texture=Lufthansa Cargo
atc_airline=LUFTHANSA CARGO
atc_heavy=1
atc_parking_codes=GEC
atc_parking_types=CARGO
ui_manufacturer=AI_Plane
ui_type=MD-11F
ui_variation=Lufthansa Cargo
description=For AI aircraft.By FSPainter,Hiro

When viewing the PFE installation folder I find "airline_icao.dat" and "callsigns_map.dat".

Both files contain "Lufthansa Cargo". Do I need to insert the ICAO code "GEC" anywhere in the texture folder or in the aircraft.cfg?

Are there entries that could irritate PFE to use the correct callsign such as the registry D-ALCE. These registries I use very often in the texture structure to differentiate from each repaint.

Would be really interested how PFE uses the callsigns.

Maybe one of the developers can help me here as well


Kind regards,

Axel

PFE reads the callsign information directly from fsuipc, it doesn't read the aircraft.cfg file.

Sent from my Samsung Galaxy S

Thanks Dave for the hint,

I think I will try to find something out about fsuipc then how it deals with callsigns.


Cheers,

Axel

I think that FSUIPC only uses the first few letters of a long callsign, thirteen characters I believe.

You can see what callsigns are in use using Peter Dowson's TrafficLook software, this will show you the callsigns as FSUIPC knows them.

So LUFTHANSA CARGO would be passed as LUFTHANSA CAR and maybe PFE can't cope with that?

Just a little thought - maybe the solution is to change the entry in Callsigns_Map.dat to match FSUIPC's output and be "Lufthansa Car"?

Or maybe I have gone completely in the wrong direction and all I have said is a load of old tosh! Sorry if I have.

John

I left this one a while awaiting feedback from Dave or Axel but all has gone silent. Inquisitiveness has got the better of me and I have spent several hours testing various permutations to get this to work.

The first thing I established was that AI aircraft with the atc_airline=LUFTHANSA CARGO entry in the aircraft.cfg were being read by PFE as: "LUFTHANSA CHARLIE ALPHA ROMEO" so it is indeed true that PFE is only getting thirteen characters from FSUIPC but it is not translating them correctly into the desired callsign.

I therefore tried changing the atc_airline= and also adding an appropriate entry to the Callsigns_Map.dat file . Many permutations did not work as I wanted, but I have finally found one that does:

LUFTHANSA_CARGO reads Lufthansa
LUFTHANSACARGO reads Lufthansa
LUFTHANSACAR reads Lufthansa
LUFTHANSCAR reads Lufthansa Cargo . . . . . . HOORAY!

I would describe this as a solution, not THE solution. I think this is something Dave needs to look at as it may also affect other callsigns. We shouldn't have to invent callsign names to make PFE work correctly.

To sum up, these are the changes that can be made in order to make it work:
in the aircraft.cfg file change
atc_airline=LUFTHANSA CARGO
to
atc_airline=LUFTHANSCAR

Callsigns_Map.dat file
find the entry that reads:
Lufthansa Cargo,703, 10
and add an extra line below it reading:
Lufthanscar,703, 10

John