Search the Community

Want Radar Contact to recognize Airline Callsigns instead of simply calling airline aircraft by their respective N numbers? Here is what I did. Thanks to Pete Dowson over at FSUIPC for patiently pointing me in the right direction. You can find this on Page 7 Advanced Users Guide. For convenience, here it is... Before you edit, change, move, etc your FSUPIC.INI file ALWAYS make a copy of it first! Here are the changes you should make to FSUIPC.INI file that will enable not only Airline Callsigns but a few other facilities too. So instead of Boeing 7358K, you will now hear United Flight 4532 or Horizon Air 1232 etc. For instance, if you have experience flying in a typical traffic pattern performing closed traffic, a lot of Real World controllers will simply call you by.. "Cessna 56B" Instead of "N4556B". Something I had never heard before I made this change. TCASid: FSUIPC supplies data on the additional AI aircraft flying in the neighbourhood, for external TCAS or mapping programs to display. Normally such aircraft are identified by Airline and Flight number, if there is one, otherwise by the Tail number. However, other types of identification string can be chosen instead. In particular, the optional labels placed on the aircraft by FS in the scenery view only shows tail numbers, so if you want to match them up you’d want to set this parameter to "Tail". The utility "TrafficLook" can show these differences in its display. 　 The full list of options here is: Flight for airline+flight, or tail number, as available (default) Tail for tail numbers only 7 Type for the "ATC type", generally only the Make Title from the aircraft title (in the .CFG file), truncated to 17 characters Type+ for the type as above, truncated if necessary, plus the last 3 characters of the tail number Model for the model description 　 TCASrange: Sets the maximum range at which AI aircraft will be added to the tables for external TCAS applications. This defaults to 40 nm. A value of 0 turns off the limit altogether. FixedTCASoptions=Yes This can be added by the User if the above settings are to remain locked, unchangeable except by editing here, in the INI file. For Example: [General] TCASid=Flight TCASid=Type+ <- Not found in my original FSUIPC.INI, however it works well when added. TCASrange=40 FixedTCASoptions=YES 　 So what I simply did was change the lines in the [General] section of the FSUIPC.INI. In the .INI file you will see the TCASid=Flight line, as well as the TCASrange=40 line, along with MANY other commands within the [General] section. These lines will be a little more than half way down. I simply added the FixedTCASoptions=YES to my FSUIPC.INI file, and it has the outcome I was desiring to have. Now RADAR CONTACT uses proper Airline Callsigns instead of simply using N numbers on many occasions. I also have the TYPE+. This is the line that allows what is described above where RW controllers will simply state "Cessna 56B" Instead of "N4556B" instead of the entire lengthly Nnumber. I tested this on FSX Acceleration, Windows 7, with both FSXATC as well as Radar Contact 4. Works great, your mileage may vary. The only thing I DID NOT TEST was if this works without a paid subscription.