Install XPlane2Blender correctly, export OBJ8 models, set textures and datarefs, and fix missing menus, version errors and failed X-Plane exports.
Install XPlane2Blender by downloading a packaged release that matches your Blender version, installing the ZIP through Blender’s Add-ons or Extensions preferences, and enabling it. To use it, mark an object or collection as exportable, assign its X-Plane file path and properties, then run the X-Plane OBJ export and inspect the log for errors.
What does XPlane2Blender actually export?
XPlane2Blender exports Blender models as X-Plane’s OBJ8 format, which is different from an ordinary Wavefront OBJ despite using the same .obj extension. It handles geometry, materials, texture references, animations, datarefs and cockpit manipulators supported by the selected exporter version.
It does not create a complete aircraft, an .acf file or a scenery package by itself. Aircraft still require Plane Maker configuration, while scenery objects must be placed in a package with an editor such as WED. Treat XPlane2Blender primarily as an exporter rather than a round-trip OBJ importer.
How do I install XPlane2Blender in Blender?
- Check Blender compatibility. XPlane2Blender depends on Blender’s Python API, so an exporter built for one Blender generation may fail in another. Use the compatibility information supplied with the packaged release; installing the newest Blender build is not automatically the right choice.
- Download the packaged release ZIP. Use the add-on archive published by the XPlane2Blender project, not an automatically generated repository source archive. The latter often has an extra directory level and will not register correctly.
- Open Blender’s preferences. Find the section labelled Add-ons or Extensions. Depending on Blender’s interface, the local installation command may be called Install or Install from Disk.
- Select the ZIP without unpacking it. Only extract it first if the release documentation explicitly says that the actual add-on ZIP is nested inside the downloaded package.
- Enable XPlane2Blender. Search the installed add-ons for its name and tick or enable the entry. Save preferences if that Blender version does not save them automatically, then restart Blender.
- Verify the installation. Look for X-Plane properties on objects or collections and an X-Plane OBJ command in Blender’s export interface. If neither appears, the add-on did not load successfully.
When Blender reports a registration, syntax or missing-module error during activation, the usual cause is an incompatible Blender/exporter combination. Reinstalling the same archive rarely fixes that; use a supported Blender release or the corresponding XPlane2Blender package instead.
How do I export my first X-Plane OBJ?
- Work at real dimensions. Keep the scene’s unit scale consistent with metres and verify the model against a known measurement. Set origins where hinges and pivots belong, and apply scale or rotation before rigging when doing so will not damage an existing animation.
- Create one export root per OBJ. Select the object or collection that should become the file and enable its X-Plane exportable/root option. Releases supporting both forms commonly label these Exportable Object and Exportable Collection.
- Set the destination and OBJ type. Enter the export filename or path in the X-Plane properties. Choose the aircraft, cockpit or scenery-related options appropriate to the model rather than reusing settings from an unrelated project.
- Prepare the materials. Assign image textures through Blender materials and keep their filenames and capitalisation consistent. A single OBJ8 normally references one base texture sheet, with optional lit and normal-map companions; split the model into separate exported OBJs when it genuinely needs different texture sheets.
- Run the X-Plane export. Use the X-Plane OBJ export command, whose exact wording and location can vary between Blender releases. Exporting normally processes every enabled export root, so disable test roots that should not be written.
- Read the exporter report. Warnings about missing textures, unsupported nodes, invalid animation data or absent export roots should be fixed before testing in X-Plane. A file being created does not mean every feature was exported.
Do not export over X-Plane’s default aircraft or stock resources. Put scenery work under a dedicated Custom Scenery package and aircraft objects inside the relevant custom aircraft package. If X-Plane cannot find the completed package, check the placement and nesting rules in our guide to X-Plane add-on folder structure and testing.
How do aircraft and scenery workflows differ?
| Project | Where the exported OBJ belongs | What happens next |
|---|---|---|
| Aircraft exterior | The custom aircraft’s objects directory | Attach the OBJ to the aircraft in Plane Maker and verify its position, lighting and animation in X-Plane. |
| 3D cockpit | The aircraft package, using the appropriate cockpit-object setup | Configure datarefs and manipulators, then test every control from the pilot’s viewpoint. |
| Scenery object | An objects directory inside a custom scenery package | Import or reference it in WED, place it, validate the package and test it in the simulator. Our WED scenery creation and validation walkthrough covers that stage. |
XPlane2Blender supplies the visual OBJ, not the surrounding package logic. A finished Blender-originated X-Plane aircraft package is useful for seeing how exported objects, textures and aircraft-level files are arranged, although its contents should not be treated as a template for every exporter version.
How do I animate parts and cockpit controls?
XPlane2Blender converts supported Blender keyframes into X-Plane animation commands when the animated object or bone has a valid dataref mapping. Create the motion around the correct origin, define the relevant dataref path and map the keyframes to meaningful dataref values in the add-on’s animation properties.
An animation only changes the model’s appearance. A cockpit switch also needs an appropriate manipulator, and the aircraft or plugin must provide a working command or writable dataref. Inventing a dataref name does not create functioning aircraft logic.
Test simple motion before building a long hierarchy: two positions for a door, one rotation axis and one known dataref. If that works, add parented parts and manipulators. This isolates reversed axes, incorrect pivots and parent transforms before they become difficult to trace.
Why does XPlane2Blender fail to export?
| Symptom | Likely cause and fix |
|---|---|
| The add-on is not listed | The wrong ZIP was installed, the archive has an extra folder level, or the release is incompatible with Blender. Install the packaged add-on release matched to that Blender version. |
| Activation produces a Python or registration error | Remove stale duplicate copies from Blender’s user add-ons directory, restart Blender and install one compatible release. |
| The export command runs but creates nothing | No object or collection is marked as an export root, its output path is empty, or validation stopped the export. Check the exporter log rather than repeatedly changing the destination. |
| The model is pink in Blender or untextured in X-Plane | An image is missing, the OBJ references the wrong path, or filename capitalisation differs. Case mismatches are especially visible when a package is moved between operating systems. |
| The exporter reports conflicting textures | Materials in one OBJ are using different base texture sheets. Consolidate them into one atlas or split the geometry into separate export roots. |
| The model has the wrong size or orientation | Check scene units, unapplied transforms and object origins. Do not add arbitrary 90-degree corrections without first testing a simple known-orientation object. |
| An animation is static or rotates incorrectly | Confirm that the animated object or bone has a dataref mapping, usable keyframe values and the correct pivot. Also check for parent transforms affecting the result. |
How should I update XPlane2Blender?
Back up the .blend file before changing either Blender or XPlane2Blender. Disable and remove the old add-on, restart Blender, install the matching replacement and export a small test object before opening and resaving a production project.
Keep an older working Blender installation when maintaining an established aircraft or scenery project. Blender upgrades can alter materials, animation behaviour and add-on data; converting the only copy of a project can leave no practical route back.