Hello,

 

I just picked up UT2 and am having an issue, which has been documented, but I can't fix.

 

When RC encounters Mesaba, it says MIKE.

 

I used TrafficLook to see what it was supposed to be. It was Mesaba Airlines.

 

So I checked c4.csv and the entry was:

mesaba, mesaba, Mesaba Aviation, 0,0

 

I changed it to:

mesaba, mesaba, Mesaba Airlines, 0,0

 

to match. But it still says MIKE every time.

 

Am I missing something?

 

Thanks!

"I used TrafficLook to see what it was supposed to be. It was Mesaba Airlines"

 

Does UT2 still return Mesaba Airlines once the ai starts taxiing to the take-off runway? It has been documented that UT2 does not assign the flight number until after it gets CD and ground instructions. Once the ai has a flight number added is it still returning Mesaba Airlines or just mesaba?

 

Look at this extended thread:

http://forum.avsim.n...timate-traffic/

 

especially page 2.

 

RC can not be responsible for inconsistencies in changing formats during a flight from UT2. I suggest that you check their forums to see if anyone else has comments.

 

http://en.wikipedia....Mesaba_Airlines states "mesaba" is the correct radio call sign and that's also what was stated up until its demise (folded into Pinnacle) as shown on flightaware.com flight tracking (for KMSP).

 

from the original:

mesaba,mesaba,Mesaba Aviation,0, 0

try changing it to:

mesaba airlines,mesaba,Mesaba Airlines,0, 0

Note that there are no spaces preceding commas and the only space precedes the last 0.

 

To cover all of the bases in will not hurt to create in rcv4\script\pilotscripts and rcv4\script\controller scripts a file called mesaba airlines.txt . The contents should be mesaba as a single line followed by a return. This is the reference to the mesaba.wav file in all of the voice folders.

Thanks Ron,

 

So I can be smarter, what are the 3 values in the .csv?

 

(1) (2) (3)

mesaba, mesaba, Mesaba Aviation

 

 

EDIT: Oh, and I put spaces. Will try it with those removed.

Thanks again!

Guessing since I don't have access to that information:

 

1) ai radio call returned from FSUIPC

2) script file name used

3) airline name as used in the General tab airline selection for the user aircraft.

 

I have no clue as to the two numeric parameters trailing those.

That was it!

 

Matching whatever UT2 is outputting in the first field fixed them all. Thanks SO much Ron!!

Thanks to user Scandinavian for pointing his fix out in the other thread.