Not quite sure what you are suggesting, in practical terms (sorry!). As an example, "Indigo" is in the drop-down callsign box for user aircraft, so the wav file is there to be used. How do I get PF3 to use this for Indigo AI traffic then? Can I add it to the callsign dat file - I am not at my FS PC as I type this, so cannot verify whether it is already in the dat file or not; if it is, then why wouldn't PF3 be using it to address Indigo AI a/c?.
(What do the two figures after the callsign indicate. e.g. Contract,102,15?).
I changed the callsign from IFLY to INDIGO in the AI aircraft.cfg files, but if I understand correctly, that won't actually make any difference in practice... So what are the steps I must take?
As Dan pointed out, "Indigo" is "Indigo Blue".
PF3/Data/pf3_callsigns.dat fills the drop-down callsign box and contains:
Indigo,614,22
PF3/Data/Callsigns_Map.dat is for mapping AI aircraft and contains:
Indigo Blue,614, 22
In PF3/captions.ini you see the "primary" names, in this case:
Pfac614=Indigo Blue
If you want to map iFly to Indigo Blue, just add this line to PF3/Data/Callsigns_Map.dat:
iFly,614, 22
To map "Indigo" to "Indigo Blue", use:
Indigo,614, 22
Regarding the numbers:
614 is part of the file name.
The wav files could be any of: PF3/Wav/Rad?/Pfac614?.wav
If the first German controller speaks this, it would be RadK/Pfac614A.wav
22 is the region (A=0, B=1, ..., W=22), W is US Generic.
So PF3 primarily uses US Generic voices for AI aircraft of this airline.
I hope this clarifies it more than it confuses
