Edit: This was written before your solution. I could not find any script pf wav files for nor shuttle nor was it in my c4.csv file. You must have an audio update.

 

As far as UT2 is concerned they should have had the radio call correct in whatever database they are using. I referred to this list based on IATA and ICAO data:

 

http://en.wikipedia.org/wiki/Airline_codes-N

 

The following procedure below is for substituting what .wav files are available.

 

-----end edit------

 

Norwegian Air is not in any of my RC files. The closest you can come to is to modify the carrier data file so Mesa Airlines "air shuttle" call is used without creating lots of wav files by concatenating a chopped version of north and extracting shuttle and combining for each controller and pilot voice - a lot of work.

 

If you accept the use of "air shuttle" you can create a controller script and pilot script called nor shuttle to substitute the air shuttle wav available in each voice.

 

Make a backup copy of rcv3.dat and c4.csv in a safe folder.

 

Add this line to c4.csv (using notepad or wordpad saving as an MSDOS test type file and the cs4.csv file name is not changed insuring no extra spaces are added where the commas are involved and at the line beginning and line ending:

NOR SHUTTLE,NOR SHUTTLE,Norwegian Air Shuttle - Norway,0, 0

 

In the pilot scripts and controller scripts folder create a file called nor shuttle.txt. That file should contain air shuttle for its contents.

 

Let me know if that works.

 

It is important that all of the formatting is preserved. If you get an error copy back rcv3.dat into your RC folder and c4.csv into your rcv4\data folder to restore everything.

Norwegian Air is not in any RC files. The closest you can come to is to modify the carrier data file so Mesa Airlines "air shuttle" call is used without creating lots of wav files by concatenating a chopped version of north and extracting shuttle and combining for each controller and pilot voice - a lot of work.

 

If you accept the use of "air shuttle" you can create a controller script and pilot script called nor shuttle to substitute the air shuttle wav available in each voice.

 

Make a backup copy of rcv3.dat and c4.csv in a safe folder.

 

Add this line to c4.csv (using notepad or wordpad saving as an MSDOS test type file and the cs4.csv file name is not changed insuring no extra spaces are added where the commas are involved and at the line beginning and line ending:

NOR SHUTTLE,NOR SHUTTLE,Norwegian Air Shuttle - Norway,0, 0

 

In the pilot scripts and controller scripts folder create a file called nor shuttle.txt. That file should contain air shuttle for its contents.

 

Let me know if that works.

 

It is important that all of the formatting is preserved. If you get an error copy back rcv3.dat into your RC folder and c4.csv into your rcv4\data folder to restore everything.

Ron! I forgot to mention that I have chopped and edited existing sound files for Nor Shuttle, and yes it was a lot of work, really boring hehe..but I couldn´t live without it. Actually I have created some more missing callsigns, like Speedway, Swedestar, Flybird, Northrider B) . I had no problem with callsigns before in FS9 using WOAI, it started in FSX with UT2. Just because UT2 don´t use the callsigns in aircraft,cfg..

 

here is a link to the only custom made callsign that I´ve shared http://library.avsim.net/esearch.php?DLID=&Name=speedway&FileName=&Author=niclas&CatID=root

If UT2's aircraft.cfg is correct I wonder what data file they are using with the incorrect radio calls?

If UT2's aircraft.cfg is correct I wonder what data file they are using with the incorrect radio calls?

Very good question Ronzie. Anyway I took two shots from Traffic look. One with an WOAI ordinary traffic bgl and one with UT2 injected traffic. Also I took a shot of my aircraft.cfg showing the callsign there:

 

Callsigns by UT2 injected Traffic

 

Callsigns by WOAI Traffic.bgl

FYI there is a Norwegian call sign registered for military use;

Royal Norwegian Air Force / Royal Norwegian Air Force IATA Code:

ICAO Code:

NOW

ICAO Callsign:

Norwegian

 

not in RC though.

 

http://www.avcodes.co.uk/airlcodesearch.asp

The default FSX ATC understands and gets the callsigns correct. What is different in the way RC does it to only give us generic callsigns?

Not sure but it might have to do with the function of edit voicepack. If not in its data table maybe it uses speech synthesis of some kind..

 

FSX's speech data was created later probably than RC's voice recordings although there were several voice expansion packs offered for a short time after 4.3 was released.

 

RC gets its callsigns via FSUIPC ai returned tables as observed in Traffic Look. Maybe something outside of SimConnect deals with this as FSUIPC interfaces with SimConnect and should get the same data.

 

I don't know when RC4 voice data/recordings was frozen prior to its last release.

 

In reality, MS does not release all information in its SDKs. For FS9 the details of aircraft.cfg regarding ATC ids and airline name (is it a radio call or airline name) is not documented in the relative FS9 SDK.

 

RC uses the available IATA and ICAO airline tables at the time shortly after the feature freeze and recordings start followed by processing, a very time consuming process.

 

If the radio call is not in the tables RC gives you the phonetic spelling.

 

 

The default FSX ATC understands and gets the callsigns correct. What is different in the way RC does it to only give us generic callsigns?

Before when I had a missing callsign with WOAI (Traffic.bgl) I could easy check that in that aircraft aircraft.cfg and compare to c4.csv. Now with UT2 I can´t as it dont uses the callsigns there. For example when United Airlines gets an flight number the callsign is United Air. Look by yourself

 

 

 

Callsign "United" in Aircraft.cfg but is unused by UT2 and will not be recognized even with these lines in C4.csv: UNITED,UNITED,United Airlines Inc - USA,0, 0

 

 

 

 

The solution as I see it is to use Pete Dowson´s Traffic look. I will use it on my coming flights and when I here a phonetic callsign I will check and add that callsign in C4.csv.

 

 

I have a problem with RC using the generic callsigns for much of my AI Traffic such as Uniform instead of United, Juliet instead of JetBlue, etc. What could be the cause and the solution?

 

John

I have used the method above and for correct callsigns in RC4 for United and JetBlue you have to add these lines in C4.csv:

 

JETBLUE AIR,JET BLUE,,0, 0

UNITED AIR,UNITED,,0, 0

I wonder if something has changed with FSUIPC? Traffic Look is showing the correct callsigns, FSX ATC is getting it right but not Radar Contact that apparently gets its information from FSUIPC. I have noticed multiple times recently that the runway in use given me by RC is incorrect. For example yesterday, I was given 27 for my approach and all of the AI was using 34. Frequently I find myself facing departure traffic on arrivals around the world and have to use the Clear command in UT2.

 

I am going to find an older version of FSUIPC and see if it makes a difference, as an experiment.

I changed back to FSUIPC 4.09 and it was the same. Something else I noticed that is very odd. Sitting on the ground at KJFK, using FSX, RC and TrafficLook, an American flight was correctly called, JetBlue was Juliet and then another American flight was called "Alpha". TrafficLook showed the correct information.

There seems to be some conflict between RC and UT2. I find the correct callsigns with FSX ATC, UTFSX, and MyTraffic. I don't know what the solution is, if any.

For me there is no conflict att all with UT2 and RC..I´m using FSUIPC 4.84. You can´t compare default FSX , MyTraffic.. ai traffic in these packages is .bgl files and looks for callsign in each aircraft.cfg. UT2 injects the traffic in FSX and generates callsigns differenty. The solution is as I described in a previous post. It works like a charm and I have no more phonetic callsigns

 

Have you tried to put these lines in C4.csv as I described before?:

 

JETBLUE AIR,JET BLUE,,0, 0

UNITED AIR,UNITED,,0, 0

 

Before these lines was added I heard Juliet and Uniform and after I can hear correct callsign for these birds.

I see the difference in your C4 syntax and just briefly tried it bya quick paste to the file and it worked for JetBlue in the short time I had. I don't have time for more now but will continue to work it. My earlier attempt at changing the C4.csv file used a slightly different syntax similar to the existing and did not work. It should be the answer and will give thanks in advance.

 

John

The airline name between the two adjacent commas is what is shown for the airline selection dropdown as the user's aircraft in the RC general tab. Just in case you want that part.

Presently I have uninstalled UT2 and am running another traffic program. When I have the time to fix the RC file, maybe I will go back to UT2. Right now, I just want to fly with good traffic using RC.