Visual models on PilotEdge are selected based on the ICAO code, airline code and livery code for each aircraft. Up until now, the airline code had to be diligently entered by users at the time they connected to the network. For example, if you connected as UAL123 with an ICAO code of B733, but didn't enter UAL as the airline code in the connect dialogue, then you would be identified as a generic B733.
As of this morning, the server automatically sets your airline code in cases where it's able to extract it from your callsign. You can still specify your own airline code if you need, but other than that, it'll take care of it for you.
With the new X-Plane plugin release containing a massive number of new liveries, along with the HD CSL releases of the 737-800, MD-80, this is a great time to have this feature!
This is not platform specific (hence, a post in the Pilots forum). If you have a wide range of models for FSX/P3D, this will benefit from the change as well.
New server feature today: auto airline code
-
Keith Smith
- Posts: 9939
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: New server feature today: auto airline code
Keith does the mean if you are using fsx/p3d you no longer have to mess with manual model matching by editing config files?
-
Keith Smith
- Posts: 9939
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: New server feature today: auto airline code
No, that is not the effect of this change. The effect of this change is to automatically set your airline code on your behalf when you connect to the system.
The end result is that if you DO have airline-specific liveries on your drive, and they've been mapped appropriately (such as the VIP model set, ancient as it is, it's a good example, or World Traffic), then you will see those airlines represented more frequently. Prior to this change, if you were flying with a friend who was connected as UAL123 in a B738, but they hadn't set their airline code when connecting, then you would see them as a generic B738 instead of the United model.
The end result is that if you DO have airline-specific liveries on your drive, and they've been mapped appropriately (such as the VIP model set, ancient as it is, it's a good example, or World Traffic), then you will see those airlines represented more frequently. Prior to this change, if you were flying with a friend who was connected as UAL123 in a B738, but they hadn't set their airline code when connecting, then you would see them as a generic B738 instead of the United model.