Install CSL aircraft packages in X-Plane 12, set the model path, verify xsb_aircraft.txt and fix missing, duplicate or incorrect traffic.
To install CSL aircraft packages in X-Plane 12, extract each package into the CSL directory used by your traffic plugin or pilot client, preserve its internal folders, then select that directory in the plugin’s model settings. Restart X-Plane and confirm the client reports loaded models; never place CSLs in Aircraft.
Where do CSL packages go in X-Plane 12?
The correct location depends on the plugin displaying the traffic. CSL, or Common Shape Library, packages contain visual models for multiplayer or live traffic; they are not flyable aircraft and X-Plane does not load them by itself.
| Use | Package location | Configuration |
|---|---|---|
| VATSIM pilot client | The client’s CSL directory, often under its own Resources/CSL folder | Select or confirm the CSL/model-matching path in the client |
| Live-traffic plugin | A dedicated CSL folder recognised by that plugin | Add the parent folder to the plugin’s model paths |
| Flyable aircraft | X-Plane 12/Aircraft | Not applicable: this is not a CSL package |
Some clients automatically scan a fixed folder, while others accept an external directory. If an external path is supported, it can be preferable because plugin updates are less likely to replace the models.
How do I install a CSL package step by step?
- Identify the plugin that will use the models. For network flying, install and configure the pilot client first. Our X-Plane 12 VATSIM client configuration explains where CSL model matching fits into the setup.
- Close X-Plane and extract the complete archive. Do not leave the package compressed, and do not move individual object or texture files out of their supplied folders.
- Check the package structure. A traditional CSL package commonly contains an
xsb_aircraft.txtdefinition file alongside model folders and assets. For a practical example, see our Bluebell folder structure and metadata checks. - Copy the package into the CSL parent folder. A typical client-managed layout is
X-Plane 12/Resources/plugins/<client>/Resources/CSL/<package>/, but use the directory required by your particular client rather than assuming every plugin is identical. - Set the model path. Open the traffic plugin or pilot client settings and find the option labelled CSL path, model path, model matching or similar. Select the parent folder containing the package directories, not an individual aircraft model unless the plugin specifically asks for that.
- Restart and verify the installation. A full X-Plane restart is the safest way to force every client to rescan its models. Connect to the network or enable live traffic, then check the plugin’s status or model count.
A mistake we see constantly is an extra archive folder, producing a path such as CSL/Package/Package/xsb_aircraft.txt. Move the inner package folder up one level so the plugin reaches its definition file where expected.
How can I tell whether the CSL models loaded?
A successful installation is shown by a non-zero model count, no CSL loading errors and visible traffic once the plugin receives aircraft data. CSL aircraft will not appear in X-Plane’s aircraft selection screen.
If the plugin provides no clear count, inspect Log.txt in the main X-Plane 12 folder after closing the simulator. Search for the client name, CSL, the package name, or messages about objects and textures that could not be loaded.
Why are my CSL aircraft not showing?
Missing CSL traffic is usually caused by an incorrect model path, an extra folder level or an incomplete extraction.
- Zero models detected: confirm that the configured parent folder contains actual package folders and their definition files. Make sure the path was saved before restarting.
- Invisible or untextured aircraft: extract the archive again and preserve every relative path. Renaming object, texture or livery files can break references stored inside the package.
- Package works in one client but not another: CSL formats and metadata support vary. Use a package explicitly supported by the traffic client rather than assuming all X-Plane model libraries are interchangeable.
- Failures on Linux: file names and paths are case-sensitive. A texture reference whose capitalisation differs from the real file can work on another operating system but fail on Linux.
- Models disappear after an update: check whether the client’s internal CSL folder was replaced or its custom model path was reset.
- Duplicate traffic: disable X-Plane AI aircraft or a second traffic-injection plugin. Two active sources can draw separate models for the same aircraft.
For LiveTraffic and similar uses, our live-traffic installation and model-path guidance covers the additional data-source and duplicate-aircraft checks.
Why do the aircraft types or liveries look wrong?
An incorrect type or paint scheme usually means model matching fell back to the closest available CSL, not that installation failed. The client compares transmitted aircraft, airline and livery codes against the package definitions; if no exact match exists, it substitutes another model.
Check that the relevant aircraft family and airline package is installed, then review any model-matching messages. Installing several overlapping libraries can also create duplicate definitions, so remove or disable the older copy rather than combining files manually.
Can one CSL folder be shared by different plugins?
One folder can be referenced by multiple plugins if each plugin supports that package format, but every plugin must be configured separately. Do not run two traffic injectors at the same time simply because they share the same models; that can produce duplicate aircraft and competing TCAS control.
CSL models cannot be selected and flown because they lack the cockpit, systems and flight-model files of a complete aircraft. To fly a downloaded model, install it as an X-Plane 12 add-on aircraft instead.