Here's what a UT AI aircraft like for an American Airlines B738. I took the following extract from its aircraft.cfg in the folder under FS9/Aircraft/Flight One AI 738[fltsim.34]title=F1AI738*AA *AA *00sim=F1AI_738model=panel=sound=texture=AA AA 00kb_checklists=kb_reference=atc_id=N123XX <<<<<<<<<<<<<<<<<<<; tail number used if no flight numberatc_id_color=0xffffffffatc_airline=AMERICAN <<<<<<<<<<<<<<<<<<<; airline radio callsignatc_flight_number=1000 <<<<<<<<<<<<<<<<<<<; flight numberui_manufacturer=Flight One AI Aircraftui_type=Boeing 737-800ui_variation=American Airlinesdescription=Flight One AI Boeing 737-800 Only for use as AI Trafficatc_heavy=0atc_parking_types=GATEatc_parking_codes=AALI highlighted the information of interest that FSUIPC uses from the UT2 compiled AI traffic.bgl file active in FS which uses these aircraft. It think it is similar for FSX. If you know what airline and aircraft type, check out the section in its aircraft.cfg. Open it in Notepad (you might want to back it up) and search for the airline name to get to the section of interest. You can then check to see if the two data lines are correct.Again, I have UT 2007, not the latest UT2.

Here's something you can try to diagnose the United problem while running FS and RC:With your current FSUIPC download a utility called Trafficlook.exe was included. I also see there is a beta version here:http://forums.simflight.com/viewtopic.php?...a010fdb3df6becfAfter starting FS, loading a saved parked situation where you know United aircraft are around, and optionally starting RC so you can monitor ATC AI chatter (not pre-recorded) Alt-Tab out of RC to start Trafficlook. It will in its own window display airborne, ground, or both AI in a table and might provide how United aircraft are reported by FSUIPC to RC.You can see if the response is correct for RC.

Just tried the Trafficlook.exe and it seems like the problem occurs because some of the flights call signs are "American" while others will be "American 1672" it seems for some of the flights the number got joined onto the call sign. I'm assuming that RC doesnt understand "American 1672" so it just says Alpha 1672. How this happens i have no idea.

All flights from UT2 do get a flight number appended -- when they get clearance (i.e. actually when UT2 loads their flight plan).UT2 works completely differently from all other AI packages. It injects each AI aircraft directly, via SimConnect. For those AI flights being started in the air, it provides a flight plan directly -- of course, else they'd need constant control (slowing down FS to a crawl). But those AI flights starting on the ground first have their aircraft model created with no flight plan, then, when their scheduled time arrives, their flight plan is provided.Because they aren't actually moving at the time they have no flight plan (and therefore no flight number), there should be no upset for RC (unlike TrafficBoard and other programs designed to show departure boards), but of course RC will not be able to provide the correct callsign until the departure is imminent.I'm not sure why it would call "Alpha" though, instead of "American".Note that the flight number within the Aircraft.CFG file is not relevant to AI flights with plans -- they acquire a flight number separately.RegardsPete

Yes, thanks. I refreshed my memory and it is in the AI flightplan. The ATC airline label in aircraft.cfg is used since the AI flightplan table (for compiling) refers to a specific aircraft as defined in an aircraft table file that points to the AI model in the FS aircraft folder when compiling the traffic file takes place - if it happens the same way as in UT 2005 and previous versions.This line should be checked (e.g. atc_airline=AMERICAN) to see if there is a problem. If there is then after fixing the UT2 compiling or whatever process it uses should be performed to enable the changes.Traffic Look shows that once an AI aircraft starts moving or arrives moving the flight number is included in the aircraft ID and excluded when parked so it is normal for the ID to show or not show the flight number depending on the AI aircraft status. I'm not sure how RC parses the aircraft ID. In Traffic Look check that there is a separation character between the airline name and flight number. Note it is normal for some airline names to have two words. I'd have to check in to the FSUIPC.SDK to see if the airline ID and flight number are returned as a combined value or two values.Anyway, it appears your problem might be AI flightplan specific possibly to the aircraft involved. Southwest uses mostly B737-700s. I'm not sure if they use an earlier model such as a 737-300. If they do use a model mix then your problem would occur at a specific time and location.The log made for RC includes the AI tables. It might help to narrow the erroneous event down to time and location. Once done, create a parked flight a few minutes before that time, load RC up with a flightplan that originates at that location, enable logging, and start RC and let it run until you hear the error. Alt-Tab back to RC and hit the QUIT button to stop the log. Zip it up and send it to jd as indicated at the forum top with description and time of what you heard so he can search for it.Sending a log is detailed at the top of this forum.

---------------snip-------------Note that the flight number within the Aircraft.CFG file is not relevant to AI flights with plans -- they acquire a flight number separately.RegardsPete

I'll do the log sometime soon. Today, I did a flight from KORD to KFLL and while waiting in a long line to take off I noticed that all the American flights landing and taking off were correct. However all the United flights were pronounced Uniform. There were a couple other flights that we pronounced by there letter, i heard an Alpha and another one i cant remember but they were not close to me so i couldn't see what airline they were. Seems like its only restricted to a few airlines or individual planes though.

I'll do the log sometime soon. Today, I did a flight from KORD to KFLL and while waiting in a long line to take off I noticed that all the American flights landing and taking off were correct. However all the United flights were pronounced Uniform. There were a couple other flights that we pronounced by there letter, i heard an Alpha and another one i cant remember but they were not close to me so i couldn't see what airline they were. Seems like its only restricted to a few airlines or individual planes though.

I guess the other thing to check is that you actually have the UNITED wav located in all the wav folders. From memory, it should just be a united.wav. Do you have that wav in all the wav folders?Subs

Just tried the Trafficlook.exe and it seems like the problem occurs because some of the flights call signs are "American" while others will be "American 1672" it seems for some of the flights the number got joined onto the call sign. I'm assuming that RC doesnt understand "American 1672" so it just says Alpha 1672. How this happens i have no idea.

i seem to remember something strange about american. not sure what was strange about it.anyway, i need a log, to see what fsuipc is seeing, and why it doesn't matchup with the callsignes in the c4.csv filein your fsuipc.ini file, what are your values for the two below?TCASid=FlightTCASrange=0if they aren't what mine are, change yours to match mine.and make a log, and send it to me. should be easy to find the problem. was it a pilot/copilot/controller not pronouncing american correctly? or was it a chatter pilot?jd

i seem to remember something strange about american. not sure what was strange about it.

It might be a good idea to check all the atc_airline= lines for all AMERICAN AI planes - after the AAL lawsuit fiasco, some traffic packages were forced to change the atc_airline= line from AMERICAN to MERICAN.RCv5 will take this into account but it may cause inconsistancies in v4.But as jd says, a log is still the best way to see what's happening.Subs

American actually seems to be one of the ones that works the best. On my last flight like I said before United seemed to be the major trouble maker, however the problem is not just as simple as united being the only one that doesn't work. It just seems to be the one that never works. I would have sent the log already but my computer decided to crash yesterday so I'm in the process of reinstalling everything now so hopefully i can send it in soon, I know I'm not the only one with this problem.

American actually seems to be one of the ones that works the best. On my last flight like I said before United seemed to be the major trouble maker, however the problem is not just as simple as united being the only one that doesn't work. It just seems to be the one that never works. I would have sent the log already but my computer decided to crash yesterday so I'm in the process of reinstalling everything now so hopefully i can send it in soon, I know I'm not the only one with this problem.

does your computer crash a lot? send a log when you can. it will be simple to find the problem. and all the others with this problem, please send me your logs too.jd

By problem I meant the conflict between UT2 and Radar Contact pronouncing callsigns. This is the first time my computer has crashed.

By problem I meant the conflict between UT2 and Radar Contact pronouncing callsigns. This is the first time my computer has crashed.

if ut2 did something funky with their names, we can re-release a c4.csv file to adapt to the funkiness. it's not like we don't have united recorded. for instance, if fsuipc sees the united ai as UAL, we can tell rc when you see UAL, call it united.without a log, i'm guessing. i'm waiting on a log from anyone with ut2, having problems with rc calling out call signs.jd

JD, did you get the log that i sent??Nick

JD, did you get the log that i sent??Nick

sorry. nothing here. did you send it to [email protected]? did you zip it up?

sorry. nothing here. did you send it to [email protected]? did you zip it up?

Yea, I just tried to sent it again so we will see what happens