Flight Sim Live Traffic Liveries (FSLTL) - Short Review

/

FSLTL ANA and JAL at Toyama (RJNT), Japan

Those who have used flight simulator for many years will recall the days when you flew alone, with no other aircraft except a few poorly defined airliners, or a Cessna or two parked at the airport. Flight simulator has come a long way since then, and today it’s possible to fly on-line with several other user-piloted aircraft, or at the very least have several well-made AI (artificial intelligence) aircraft in the sky around you.

As simulator AI evolved, so did the number of AI programs and add-ons that were available, with some packages providing real world airline schedules and user adjustable aircraft liveries. Needless to say as AI grew, so did the complexity in installing and running these programs. Unless you enjoy the complexities of software, I dare say that you want an AI package that works, is easy to use, and runs in the background, allowing you to fly the simulator and not continually have to tinker with AI. FSLTL is such a program.

This is a short review, meaning I am not going to delve into the intricacies of FSLTL. The developer has included a very easy to understand manual and a video; to rehash what is already written in the manual is counter productive to the product.

General

FSLTL (Flight Sim Live Traffic Liveries) is a free, easily configurable AI program that can be turned on or off at will and runs in the background. The program is VATSIM compliant and interacts with the default Air Traffic Control in MSFS-2020 and AI Air Traffic Control programs, such as Beyond ATC and Say Intentions.

FSLTL does not use imaginary flight schedules. Rather, it extrapolates flight data from FlightRadar 24 (FR24) and replicates these flights in flight simulator using the appropriate aircraft types and liveries. Therefore, when you see an airbus A380 taking off from Adelaide International (YPAD) the AI is reflecting the actual flight schedule of the real airline. The real time flight information from FR24 is pinged every 20 seconds so the replication is not exactly real time, but it is very close.

Although there is no reason to use other AI traffic, FSLTL has the capability to also incorporate AI aircraft models and liveries from third party providers (for example, Just Traffic). The aircraft type and liveries used by FSLTL come from a variety of sources with FAIB (FSX AI Bureau) creating many of the models and liveries.

FSLTL is updated from time to time with new aircraft and liveries.

Installation

Installation of the program is very straightforward. An installer (Fly-By-Wire installer) is downloaded to your computer from the FSLTL website. After running the installer, you select the components you want to use. You will need the Traffic Injector and the Traffic Base Models package. The base model package is quite large; therefore, be certain there is appropriate space in your computer to store the files. Both the traffic injector and base model package must be installed into the community folder of MSFS-2020. If you wish to install these items outside of the community folder then this can be done; however. the files will need to be linked to the community folder using a program such as MSFS add-ons linker.

Important Point:

  • FSLTL uses simconnect. At a minimum, VC++ Redist 2015-2022 x64 must be installed on your computer.

FSLTL Traffic Injector User Interface

Traffic Injector and User Interface (UI)

The traffic injector is the .exe file that starts FSLTL and injects the traffic into flight simulator. A shortcut can be made to this file and stored anywhere you wish: on your desktop, in the menu bar, or it be added to a batch file to automatically load when flight simulator is started. The base models package is only a folder with the various models. It requires nothing be done to it other than placing the folder in the correct location.

The traffic injector user interface (UI) can be accessed either by selecting the icon from the inflight menu system in MSFS-2020, or as discussed by a standalone .exe icon. Opening the User Interface enables the user, amongst other things, to streamline the program and control the number of aircraft being spawned at any one time, either in the air or on the ground. The UI also can re-spawn AI aircraft, set the distance that AI aircraft can be spawned, or remove AI aircraft during the final landing phase. This can be beneficial when landing in airports that have high density traffic.

In my simulator, I have the FSLTL .exe icon in the menu bar. After loading flight simulator and ProSim737, I click the icon and within 1 minute AI traffic has been spawned.

File structure to open the preference panel for FSLTL

Traffic Injector Preferences

The traffic injector user interface can be changed to suit individual preferences. This is done by opening the user interface configuration file located at %APPDATA%\ fsltl-traffic-injector and selecting the fsltl-trafficinjector-config.json file. The .json file can be opened in a text editor by right clicking the file. Once the file is open you will note the various preferences that can be changed and saved.

Frame Rates and Resources

With normal use, with the exception of hard drive space to store the base models package, FSLTL uses minimal computer resources and does not affect frame rates. If you decide to have the maximum number of aircraft at an airport, in flight at varying distances, and also use other third party AI traffic, then there is a slight hit to frame rates.

Aircraft Types and Liveries

FSLTL AI aircraft have been built using glTF models for better performance, reduced stutters, and CTD avoidance. Apart from the visual appeal of looking at a well constructed model, this improves AI ground roll during take-off and landing. it also enables the display of custom lighting, contrails, heat haze and other effects, including interaction with jetways and ground services.

The base model package includes over 1900 liveries and includes all major airline aircraft types and light aircraft. At the time of writing, military aircraft and helicopters are not included.

Downsides and Known Issues

There are several known limitations with MSFS-2020 that can cause issues with AI traffic. Thankfully, none of these shortfalls relate to resource usage and frame rates. FSLTL have listed the known issues in their on-line manual.

Pink Liveries

One particular problem that did occur to me, was that several AI models were displayed as checkered designs or were coloured hot pink (rather than the correct airline livery). Whenever this occurs, it is an indication of a problem concerning the aircraft’s texture folder, or the file has been corrupted.

In my case, the problem was that the aircraft type in question (the Beechcraft King Air) was not installed into MSFS-2020. In an effort to streamline my set-up, I had deleted various aircraft types and models that I did not use. Once I reinstalled the King Air aircraft type (not the various liveries) using the content manager, the pink colours disappeared and I was presented with the correct livery (in this case a Royal Flying Doctor Service livery).

If this issue persists, and you have the aircraft types installed into MSFS-2020, the next step is to determine where the problem lies. It is relativity easy to troubleshoot this problem.

  1. Open MSFS-2020 in developer mode.

  2. Navigate to the debug/console tab (at the top of the screen).

  3. Open console and check through the various listings.

You are searching for any listings which have been tagged in yellow. As you scroll through the listings, you will eventually find the aircraft type that you noticed the problem with (checkered design or hot pink colour). This is the aircraft file that potentially has a corrupted texture file. Note the aircraft type, and then navigate to the MSFS-2020 file structure (msfs/Official/OneStore/Asobo Aircraft folders/SimObject/Airplanes/aircraft folder in question/Textures).

Open the Asobo aircraft files and scroll through the listings until you find the folder that contains the files for the aircraft in question. Open the aircraft folder and check that the appropriate texture files are included. Each aircraft should have a number of texture folders. For example, texture, texture01, texture02 and texture03. Sometimes the texture folder (no number) is missing. If this is the case, delete the aircraft folder, run MSFS-2020 and allow the program to reinstall the aircraft from the cloud. This should resolve the problem.

Final Call

I have used this program since I began using MSFS-2020. Previously, I used a number of payware AI programs which always seemed to require me to tweak or tinker with airline schedules. These programs also had a relatively steep learning curve. FSLTL works out of the box and does exactly what it says it will do, with minimal fuss - and it will cost you nothing other than a donation to the developer if you like the program.

 
 

Adding Liveries to ProSim737 Flight Model

/

The livery for the JALTRANSOCEAN Air, which depicts a whale shark is spectacular.  Why would you not want to use liveries when some look like this.  The whale shark inhabits the waters that this particular airline fly to (southern Japan) (lasta29, Japan Transocean Air, B737-400, JA8992 (18266031709), CC BY 2.0)

Flight simulator enthusiasts enjoy flying the livery of their choice, whether it be a cargo carrier such as FedEX, or a livery from one of the many passenger airlines that fly the Boeing 737 airframe.  

Airlines have unique liveries that identify the carrier.  Often the design is specific to the country or to a particular motif unique to the airlines.  For example, QANTAS depicts a red kangaroo on its tail and Aeroflot always depicts the Russian flag on its tail wing.  Some liveries relate to airline branding, others can be nationalistic (those carrying flags on their tail wings), and others can be just for fun - such as Taiwanese airline's Eva Air 'Hello Kitty' livery.  Wikipedia has an interesting list of airlines that have liveries that relate floral emblems, animals, flags and the like.

Some software companies, for example PMDG, have developed livery add-ons that can be installed by a self-extraditable .exe file;  it’s only a matter of clicking the .exe file and following the prompts, and the information, textures and changes are automatically installed behind the scenes by the software.  

The ProSim737 flight model (developed by ProSim-AR) does not at the time of writing provide a self-executable file for add-on liveries; users must install liveries manually.  Thankfully, the steps to install a livery are generic, and have been more or less the same since FS9 and FSX.

This article will primarily address how to install an aircraft livery to the main aircraft folder in ProSim737 using Prepar3D (P3D). 

The process is very similar in MSFS-2020, however, a with a few extra steps will need to be taken (see later in article).

Important Points:

  • As of March 2020 there are a several different versions of the ProSim737 flight model, each generating a different folder name and a slightly different naming profile in the aircraft section in the aircraft.cfg.

  • Take note that liveries used in Version 2 visual models are not compatible with the Version 3 visual model. Check the livery information to ensure you are using a compatible livery for the flight model being used.

  • Note that older liveries use a different method to create the textures (not PBR) and will display with slightly less detail.

Back-up

Before proceeding with any amendment to the aircraft folder, make a backup of the ProSim737 aircraft folder BEFORE making changes.  It’s also wise to copy the default aircraft configuration file.  This can easily be done by right-clicking the file and saving as a copy.  The copy can reside in the same folder, as it will have the word ‘copy’ annotated to the file name.

It’s good policy to do this just in case a problem is experienced.   If a problem presents itself, it’s an easy matter of deleting the aircraft folder and replacing it with the original, or replacing the aircraft configuration file.

The Basics

We are interested in three components:  

(i)      The ProSim737 default aircraft folder;

(ii)     The add-on livery texture folder; and,

(iii)    The aircraft configuration file (aircraft.cfg).

Note that the default ProSim737 aircraft is installed via a self-executable file that installs the default 738 aircraft to the correct folder.

File and Folder Structure

The ProSim737 aircraft software installs the aircraft to the following folder: D://Documents/Prepar3D V4 Add Ons/ProSim-AR/Simobjects/Airplanes/ProSim737-800-2018 Professional. 

Important Points:

  • D:// may differ.  It depends upon what drive you installed ProSim-AR and whatever flight simulator platform you use.

  • The aircraft folder name may be different as this relates to what ProSim-AR call their newer released flight models).

One interesting livery is British Airways (BA).  All BA aircraft depict the Union Jack on their tail.  In the 18th Century, England had colonies throughout the world and it was often stated that ‘the sun never set on the Union Jack’.  With the loss of her colonies the sun definitely now sets on the Union Jack, however, it probably never sets on British Airways as there is always a BA aircraft somewhere in the world (Andrew Thomas from Shrewsbury, UK, G-DOCT Boeing 737-436 (cn 25853 2409) British Airways. (7610860068), CC BY-SA 2.0)

This folder falls outside the main P3D folder architecture, however, various files are automatically linked to P3D so they aircraft can be flown and seen in the game.  In my setup I have two drives, which is why the Prepar3D folder is located on D Drive rather than C Drive.  Your drive may feature a different drive letter.

Livery Texture Folder

An add-on livery is usually downloaded from the Internet in zip file format.  Once the zip file is extracted, you will see a number of folders and files.  At the very least there will be a texture folder, in which is stored the various bitmaps and images necessary to amend the default aircraft with that livery.   There may also be a thumbnail image of the livery and a ‘read_me’ file.

The ‘read_me’ file is important, as this often will contain the correct edits for the livery that need to be added to the aircraft configuration file.

Non-mipped Images

The developer of the livery may also have included additional folders such as non-mipped images.  Opening this folder will reveal an alternate texture folder.  

Textures developed from non-mipped images are displayed differently by P3D and often provide slightly better detail that standard textures.  This may be advantageous if you often zoom into the aircraft to view close-up detail.  There are many variables that affect the appearance of non-mipped textures, including graphic card settings, computer specifications, and P3D settings.  For most users, the use of non-mipped textures in not necessary.  However, ‘horses for courses’, so test and choose whatever is appropriate to your circumstances.  

Mip-Mapping

Mip mapping can be a confusing topic (the naming itself causing confusion). 

Basically, textures are created using one of two methods which generate textures that have been either mip-mapped or non mip-mapped.

With regard to the ProSim aircraft, the mip-mapped textures will always give you better performance, but less visible detail, whereas non mip-mapped textures will be sharper, crisper but will require more resources from your graphics processing unit (GPU).

Important P3D Settings

If using P3D and wanting to take full advantage of mip mapping (mip-maps), it is important to understand that mip-map textures are defined by the slider settings in P3D. 

The Texture Resolution setting in P3D has the most impact on how mip-map textures are displayed.  The maximum slider value is 4096x4096.  However, if the setting is set to a lower value (for example, 2048x2048), the highest resolution displayed will be that value (2048x2048).  If the aircraft texture us made from bitmaps that are 4096x4096, the 2048 setting will not enable the full resolution of the original bitmap to be seen; you will only see a second-order textures (textures at a lower resolution with less detail).

The same principle relates to the Texture Resolution slider setting that controls the vector-based scenery which simply regulates the largest mip-map to be called and displayed.

Another often forgotten variable, that can impact on both mip-maps and non mip-maps is the overall resolution the screen(s) being used.  A higher resolution screen will always display a better quality image irrespective of the mip-maps used.

Concerning frames rates (FPS).  Mip mapping has very little effect on frame rates.  However, using mip-maps will definitely ease and free up resources on the GPU.  Interestingly, this is in contrast to sceneries which can decrease frame rates considerably dependent upon the mip-mapping that has been used to create the scenery textures.  This is because the mapping affects a large area, whereby the mapping in the aircraft is minimal in comparison.

The Anti-liaising settings (AA settings) used in P3D can also have a marginal affect of how mip and non mip-mapped textures display.

Aircraft Configuration File

The aircraft configuration file is important as it contains, amongst other things, the necessary instructions to display whatever aircraft has been selected from the P3D aircraft list.  

The configuration file is set out logically with higher-level entries (top of page) identifying the various liveries that have been included in the main ProSim737 aircraft folder.  By default, the ProSim737 flight model installs a number of liveries to the aircraft folder and automatically amends the entries in the configuration file.

In the example below taken from the aircraft configuration file, the text that relates to the aircraft livery.  Bolded sections need to be edited for each livery.  If using the 2020 Version 3.42 flight model and Verson 1.55 visual model  see entries in blue (different folder naming).

  • [fltsim.XX]

  • title=Prosim_AR_737_800_PRO_2018_Virgin_Australia

  • sim=Prosim738_Pro

  • model=

  • panel=

  • sound=

  • //sound=cockpit

  • texture=VIRGIN

  • atc_heavy=0

  • atc_flight_number=209

  • atc_airline=Velocity

  • atc_model=737-800

  • atc_parking_types=GATE,RAMP

  • atc_parking_codes=VOZ

  • ui_manufacturer="Prosim_AR"

  • ui_createdby="ProSim-AR"

  • ui_type="737-800"

  • ui_variation="PROSIM_AR_Pro_2018_Virgin_Australia"

  • ui_typerole="Commercial Airliner"

  • atc_id=PS209

  • visual_damage=0

----------------------------------------

  • [fltsim.XX]

  • title=ProsimB738 PBR 2020 - Japan Airlines

  • sim=Prosim738_Pro

  • model=

  • panel=

  • sound=

  • texture=Japan Airlines

  • atc_heavy=0

  • atc_flight_number=887

  • atc_airline=ALL NIPPON

  • atc_model=737-800

  • atc_parking_types=GATE,RAMP

  • atc_parking_codes=JAL

  • ui_manufacturer="Prosim_AR"

  • ui_createdby="ProSim-AR"

  • ui_type="737-800"

  • ui_variation="ProsimB738 2020 Japan Airlines Livery"

  • ui_typerole="Commercial Airliner"

  • atc_id=PS209

  • visual_damage=0

Installing Textures to ProSim737 Aircraft

A: Copy the aircraft texture folder for the livery (from the download) and paste the folder into the ProSim737-800-2018 Professional folder located in simobjects/airplanes.

B: Open the aircraft configuration file (for editing). This file is located in the main aircraft folder.  Make sure you back-up this file or copy it BEFORE making changes.  This will enable to you to revert to the original file if a mistake is made.

C: Copy the aircraft details from the downloaded 'read_me' file and add them to the configuration file.  The correct place to add the details is below the last aircraft listed.  If the ‘read_me’ file does not have this information, then it will be necessary to add the information yourself.

By far the easiest method to do this is to copy/paste the last aircraft listing, and then re-name the segments accordingly.  In the example above, I have bolded the sections that need to be edited.

The most important edits are the texture= ?, title= ? and ui_variation= ?. These three entries directly influence whether you will see the livery in the P3D aircraft list and in the game.  It’s very important that the texture= ? be the exact name of the texture file in the aircraft folder; your livery will not be able to be seen if this is not done.  In some instances, the name of the texture folder may be an airline’s name (texture.virgin) or a three letter aircraft code such as texture.ual (United Airlines).  

D: The FLTSIM number also needs to be edited to reflect the correct sequence order in the configuration file. Make sure each aircraft has a sequential number. If you have three aircraft liveries, the files will be [fltsim.01], [fltsim.02], [fltsim.03].  Be especially vigilant to copy all brackets, equal signs and commas (syntax) as these are necessary to see your aircraft in P3D.

Problems and Troubleshooting

One indication that there is a problem with a livery is when the aircraft livery in question is coloured hot pink or has a checkered design. This can be caused by an incorrectly named texture file. At other times, the livery may not be visible in the P3D aircraft folder.

By far the easiest way to troubleshoot a problem, such as the aircraft not being visible in the P3D aircraft folder, is to delete the aircraft configuration file and reinstall the original backed up file.  Then redo your work ensuring there are no mistakes.  If your mistakes relate to the actual texture folders, then delete the complete folder and reinstall the original backed up folder and start again.  Most problems relate to typo errors such as forgetting to include the correct syntax (punctuation marks).

If using MSFS-2020 and the livery is not visible in the aircraft folder, the most likely reason is failure to update the layout.json file (see later)/

Screen capture showing the P3D aircraft selection folder.  Note the ‘show only favourites’ star, which when selected, will cause that livery to be displayed in the list at the expense of liveries not selected by the star.  Also, note the additional identifier in the vehicle type column (737-800 CARGO)

Setting Up the P3D Aircraft Folder for Ease of Use (favourites and type)

When you open P3D to select an aircraft, a graphical user interface (GUI) screen displays  the aircraft and liveries that are installed to the aircraft folder. 

This list can be long and unwieldy to navigate with the mouse, not to mention time consuming - you want to be able to identify your 738 liveries quickly and not wade through several versions of the aircraft you do not use.  To prune the number of aircraft you need to sort through, you can delete the unwanted aircraft from the aircraft folder, however, an easier method is to use the favourite functionality.

Select the favourite star for those aircraft/liveries you want to be see displayed in the aircraft list.   Once an aircraft /livery has been allocated as a favourite, it will always be displayed in the list, while those aircraft not ‘starred’ will not be displayed.  

If you have both cargo and passenger aircraft (or military versions of the B737), you may also want to segregate these aircraft by type.  This makes it easier to find a particular aircraft type.   This can easily be done by editing the title= ? and the ui_type= ? for that aircraft in the aircraft configuration file.  

In the example below the aircraft type has been edited to reflect a cargo aircraft (Aloha Air Cargo).  Editing the title is obvious as this changes the name in the P3D aircraft list.  However, editing the ui_type= ? enables you to change the aircraft type.  In the example below, I have included the word CARGO to differentiate cargo liveries from passenger liveries.  I have bolded the entries that need altering.

  • [fltsim.XX]

  • title=Prosim_AR_737_800_PRO_2018_Aloha_Air_Cargo

  • sim=Prosim738_Pro

  • model=

  • panel=

  • sound=

  • //sound=cockpit

  • texture=AAH

  • atc_heavy=0

  • atc_flight_number=211

  • atc_airline=Aloha

  • atc_model=737-800

  • atc_parking_types=GATE,RAMP

  • atc_parking_codes=AF

  • ui_manufacturer="Prosim_AR 2018"

  • ui_createdby="ProSim-AR"

  • ui_type="737-800 CARGO"

  • ui_variation="PROSIM_AR_Pro_2018_Aloha_Air_Cargo"

  • ui_typerole="Commercial Airliner"

  • atc_id=PS211

  • visual_damage=0

MSFS-2020

In general installing liveries in MSFS-2020 is as described above, however, there is one very important step that must be done to ensure the livery is visible - update the layout.json file after the livery has been installed, and then restart the simulator.

Layout.json File

MSFS uses layout.json files to record various changes made to the simulator.  Following any change to a file, the layout.json file must be updated.  Failure to do so will result in the changes not being implemented.   The layout.json file is located in the ProSim737 flight model folder (Aircraft\prosim-B738-v2023).

If you open the layout.json file (use any text editor such as notepad) you will observe that there are entries that refer to the default sound.  These entries must be edited to reflect the name of the audio files you have added.  As you can image, this process can be quite a chore, not too mention there is a strong possibility of making a typographical error.  Fortunately, there is a utility, called a generator file, that can be used to automate this process.

MSFS Layout Generator.exe File

The Layout Generator.exe file is a very handy utility that makes updating any layout.json file very easy.  The utility is a standalone program that can reside anywhere on your computer.  I keep a copy on my desktop.

After downloading the MSFS Layout Generator from the developer, open the file folder and you will see a file called Generator.exe.  Click and drag the layout.json file directly over the Layout Generator.exe icon.  As you drop the file onto the layout generator a  black-coloured pop-up screen will be briefly displayed.  That’s it – the layout.json file will now be updated to reflect any changes.

Important Points:

  • The layout.json file will need to be updated whenever a livery is added. 

  • The layout.json file will only update after MSFS has been restarted.

Livery List

Liveries for the Version 3 flight model can be downloaded from the ProSim-AR forum.

I also have a small collection of ProSim737 Version 3 liveries in the file download section.

Final Call

Adding various liveries can be fun and adds a element of realism, especially if you fly in different regions and enjoy looking at the aircraft, or are a videographer that creates flight simulator videos.   Paring down the aircraft list in P3D to display only the aircraft and liveries you want to see, and then segregating aircraft based on type, can save considerable time and mouse use.

The livery for JAL Transocean Air – another viewpoint.  Japan is one of my favourite regions to fly in.

  • Updated March 2020

  • Updated August 2024 (added MSFS-2020 section)

Toshi Aoki - JP Spotters, Boeing 737-4Q3, Japan TransOcean Air - JTA AN2228487, CC BY-SA 3.0

Aircraft Liveries & Textures - Adding a Livery Texture To Your B738

/

For many flight simulator enthusiasts, there’s enjoyment knowing your flying the correct aircraft livery in the correct airspace.   For others, opening the exterior views to play back your landing sequence from the flight video just looks better with a nicely painted texture or livery.  FSX comes bundled with several B738 aircraft liveries, but most of us dislike them; it’s common for individuals to search forum sites such as AVSIM in an attempt to find a livery that suits their virtual airline.

Recently, I found a FS add on that includes 164 liveries of the B738 aircraft suitable for FSX.  The file, which includes an automatic executable, can be downloaded from the French flight sim website http://www.rikoooo.com/en/downloads/viewcategory/55.   The program will download to your simobjects/aircraft folder a folder named 164 aircraft.  Within this folder can be found all the textures and a correctly constructed aircraft .cfg file.  The program also includes a correctly configured airlines file which will over right your existing airline file with all the correct ATC calls for the various liveries.  This is a wonderful time saver for those who use ATC.  Access to the aircraft is as you would usually load an aircraft, airport and weather situation..  Note that you will be required to register to the forum site before you can download the program.

Below is a list of livery textures included in the package

Adam Air, Aeromexico, Aerosvit, Air Asia Indonesia, Air Astana, Air Berlin, Air Canada, Air China, Air China Olympic, Air Europa, Air France, Air Jamaica, Air New Zealand, Air One, Air Slovakia, AirTran Airways, Air Vanuatu, Alaska , Alaska.com, Alaska Spirit of Seattle, Alaska Starliner 75, Alitalia, All Nippon Airways (ANA), ALOHA, American Airlines, America West, Ansett Australia, Austrian Airlines, Batavia Air (x3), Bmibaby, British Airways, Brussels Airlines, Bulgaria Air, Caribbean Airlines, Cebu Pacific Air, Continental Airlines, Copa Airlines, Corendon Airlines, Cubana De Aviación, Cyprus Airways, Czech Airlines, Delta Airlines, DHL Cargo, EasyJet, Eastern AIrlines, El Al (Israel), EgyptAir, Europe Airpost, FedEx Cargo, Ferrari, Ferrari Cargo, Finnair, First Choice, Flash Airlines, Fly Dubai, Flyglobespan, Frontier Airlines, Garuda Indonesia, Garuda SkyTeam, GOL, Gulf Air, Hainan Airlines (x2), IRONMAIDEN, Japan Airlines (JAL), JAT Airways (old and new), Jet2 (grey and white), JetAmerica, JetTime,Kenya Airways, Landmark (Coliseum tail), Lion Air (Indonesia), LOT (Polish Airlines), Lufthansa, Luxair, Malaysia Airlines, MALEV, Mexicana (x4), Military Woodland Camo, Mongolian Airlines (MIAT), Montenegro Airlines, Myanmar Airlines (MAI) , NASA, NAVY, Norwegian Air, Northwest (NWA), OceanAir (Avianca), Olympic Airlines,  Pan-Am, Philippine Airlines, PIA (Pakistan Intenrational Airlines), Prague (Czech Republic), Primera Air JetX (Iceland), PrivatAir, Qantas, Ryanair, Ryanair Guinness, Ryanair Kilkenny, Ryanair Vodafone, Scandinavian Airlines (SAS), Singapore Airlines, South African Airways, Southwest Airlines (Blue, Gold, New Mexico), Sterling (Australia), SunExpress, Swiss Air, TAM (Brasil), TAROM (Romania), Thomson Airways, Transavia, TUIfly (x7), Turkish Airlines, Ukraine International Airlines (UIA), UNITED (old and new), UPS Cargo, US Airways, Varig (old and new), VASP (Brazil) , V Australia, Vietnam Airlines, Virgin (blue and red), WestJet, XL Airways, XL Airways Excel.com, XL Airways Öger Tours and XL Airways Viking.

I think you will agree, that anyone should be able to find something they like from this list.

Installing to the ProSim 737 JetStream

To use the textures in the ProSim737 Jetstream B738 aircraft, it will be necessary to edit the aircraft.cfg file.  I’ve outlined the process below.  Before proceeding, make a backup of the JetStream folder BEFORE making changes.  It’s always good policy to do this just in case a problem is experienced.

A:  Copy all the aircraft texture folders (located in the 164 folder), or the ones you want as 164 edits can take a long time...., to your Jetstream folder located in simobjects/aircraft.

B:  Open two windows, one with the aircraft .cfg file opened from the 164 aircraft folder and one with aircraft .cfg file opened from the Jetstream folder. 

C:  Open/click the Jetstream aircraft .cfg file for editing. There are four main edits that need to be made.

  1. The FLTSIM number needs to be edited to reflect the correct order within the file.  Check and make sure the first airline entry is 1 followed by 2, 3, 4, 5, 6, 7 and so forth.

  2. The TITLE must be title=Jetstream738 B737-800 Air New Zealand (or whatever livery)

  3. The Sim must be sim=Jetstream738

  4. The UI manufacturer must be ui_manufacturer=”A Jetstream-Boeing”

Duplicate the text from the above mention 4 lines from the 164 aircraft.cfg, for the aircraft liveries you want, to the Jetstream aircraft.cfg file.  it's important to do these edits as you want to link the livery texture to the Jetstream flight model.  The image shows a screenshot of one of the aircraft textures from my JetStream aircraft.cfg file.

I’ve bolded and coloured red the entries that need to be edited to reflect the new aircraft textures.  You may also wish to change the ATC flight number, but this isn’t necessary for correct operation.

You have probably observed that my naming structure is a little different to the norm.  The reason I begin the name with the letter A, is so that when I open the select aircraft tab in FSX, I don’t have to scroll down to J for JetStream.  Instead, the correct folder is located at the top of the list (The letter A is at the beginning of the English alphabet).

There you have it.  The methodology explained here can be used to add textures for any aircraft livery.