OnCourse Software

Welcome to our Product Support Forums

Callsign question

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 3 of 3  [ 24 posts ]
Jump to page « 1 2 3
Author Message
Dan77
Post subject: Re: Callsign question
Posted: Wed Sep 07, 2016 1:20 am
Offline
 
Posts: 766
Joined: Sun May 05, 2013 2:22 am
 
martinlest wrote:
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?
The mapped call sign for user aircraft is actually "Indigo Blue" so to get just "Indigo" you would need to edit the wav files which for each voice seems a great deal of effort and is not really recommended. In my own view since the correct call sign is IFLY, the phonetic call is actually more authentic, but that's just my opinion. If you do decide to do some file editing, be sure to back up the original files.

_________________

Dan


Top
Profile Quote
martinlest
Post subject: Re: Callsign question
Posted: Wed Sep 07, 2016 8:48 am
Offline
 
Posts: 1334
Joined: Sun Dec 26, 2010 3:33 pm
 
Quote:
since the correct call sign is IFLY, the phonetic call is actually more authentic
Yes, I suppose in this case, that is correct!


Top
Profile Quote
ThomasAH
Post subject: Re: Callsign question
Posted: Wed Sep 07, 2016 8:58 am
Offline
 
Posts: 986
Joined: Tue Dec 24, 2013 12:27 pm
 
martinlest wrote:
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 :)

_________________

[ img ]


Top
Profile Quote
martinlest
Post subject: Re: Callsign question
Posted: Mon Sep 12, 2016 2:48 am
Offline
 
Posts: 1334
Joined: Sun Dec 26, 2010 3:33 pm
 
Thanks Thomas.


Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 3 of 3  [ 24 posts ]
Return to “PF3-ATC at its best” | Jump to page « 1 2 3
Jump to: