Install Bluebell CSL models in X-Plane for xPilot and compatible traffic plug-ins, with the right folder structure and missing-aircraft fixes.
Install Bluebell CSL models inside the CSL folder used by your X-Plane multiplayer or traffic plug-in, not in X-Plane’s main Aircraft folder. Extract the package so folders such as BB_Airbus and BB_Boeing sit directly under that CSL location, then select or rescan the path in the plug-in and restart X-Plane.
CSL stands for Common Shape Library. These models represent other pilots and generated traffic; they have no flyable cockpit or flight model and will not appear in X-Plane’s aircraft selection screen. To add an aeroplane you can fly, follow our instructions for installing selectable add-on aircraft instead.
Where do Bluebell CSL models go?
The correct destination is the CSL package directory scanned by your traffic client.
- xPilot: the standard location is
X-Plane/Resources/plugins/xPilot/Resources/CSL/. - LiveTraffic: a conventional local location is
X-Plane/Resources/plugins/LiveTraffic/Resources/CSL/. - Other clients: use the CSL directory shown in that client’s settings. Some clients use an external model directory rather than one inside X-Plane.
A configured custom path takes priority over these conventional locations. If the client provides an integrated CSL installer, use it because it creates and registers the expected directory automatically.
How do I install the Bluebell packages correctly?
- Close X-Plane and the traffic client. This prevents the plug-in from retaining its old model list while files are being changed.
- Extract every downloaded archive to a temporary folder. Bluebell models are commonly divided into aircraft families, so installing only one archive gives limited coverage. Keep the supplied folder names, object files, textures and matching definitions together.
- Find the package manifest. Each model package should contain an
xsb_aircraft.txtfile. Its parent folder should be a package such asBB_Airbus, rather than another unnecessary archive wrapper. - Copy the complete package folders into the CSL directory. A typical result is
X-Plane/Resources/plugins/xPilot/Resources/CSL/BB_Airbus/xsb_aircraft.txt. Place other Bluebell families besideBB_Airbus; do not merge all their contents into one folder. - Configure the client’s CSL path. Point it at the parent
CSLdirectory containing the Bluebell package folders. Use its rescan or reload function if one is provided. - Restart X-Plane and connect to traffic. Check the client’s model or log display for recognised packages and parsing errors.
A mistake we see constantly is an extra directory created during extraction, such as CSL/Bluebell/Bluebell/BB_Airbus. If the client cannot scan through that wrapper, move the BB_* folders up one level or change the configured CSL path. Our X-Plane folder and archive troubleshooting steps cover the same nested-folder problem in more detail.
How can I tell whether Bluebell CSL is working?
The most reliable confirmation is that the traffic plug-in lists or logs the Bluebell packages without missing-file or parsing errors.
- If remote aircraft appear with appropriate aircraft types and liveries, model loading and matching are working.
- If an aircraft appears but uses a generic model or incorrect livery, the CSL installation may be sound; the transmitted ICAO type, airline code or available matching rule may simply lack an exact match.
- If no traffic appears at all, check the connection, traffic plug-in and X-Plane traffic or TCAS integration before blaming the Bluebell package.
Why are the Bluebell aircraft missing or invisible?
| Symptom | Likely cause | Fix |
|---|---|---|
| No Bluebell packages are detected | The client is scanning the wrong directory, or the archive has an extra folder level | Select the directory containing the BB_* folders and rescan |
| Traffic uses only generic aircraft | Only some model families are installed, or no exact matching entry exists | Install the remaining Bluebell families and check that their manifests load |
| Labels appear but models do not | Object or texture files are missing, or extraction was incomplete | Re-extract the affected family as a complete folder |
| File-not-found errors appear on Linux | A filename’s capitalisation no longer matches its reference | Restore the original names and preserve their exact letter case |
| Duplicate package warnings appear | Old and new copies are both inside scanned directories | Remove the older copy or move its backup outside every CSL path |
Do Bluebell CSL models work in X-Plane 12?
Bluebell OBJ8/XSB-style CSL models can work in X-Plane 12 when the multiplayer or traffic client supports both X-Plane 12 and that CSL format. Compatibility depends mainly on the client: an obsolete plug-in will not become X-Plane 12-compatible merely by moving its model folders.
Do not place Bluebell packages in Aircraft or Custom Scenery, and do not convert or rename their files unless the selected client specifically requires it.
Can I install several Bluebell packages together?
Yes. Keep each aircraft family in its own sibling folder under the same CSL directory. When updating a family, remove the previous copy first or store the backup outside the scanned CSL tree; duplicate package definitions can produce ambiguous matches and warnings.