Export Blender models to X-Plane as OBJ8 files with correct scale, textures, animations and datarefs, plus fixes for common export errors.
To export Blender models to X-Plane, install a Blender-compatible release of XPlane2Blender, prepare an exportable collection, UV-map the mesh, apply its scale and rotation, then export it as an X-Plane OBJ8 file. Attach aircraft objects through Plane Maker or place scenery objects with WorldEditor; Blender alone does not create an aircraft or scenery package.
What file format does X-Plane use from Blender?
X-Plane uses its own OBJ8 format for rendered aircraft and scenery models. The file still has an .obj extension, but it is not a generic Wavefront OBJ file.
XPlane2Blender writes the X-Plane-specific geometry, texture references, animation commands, datarefs, manipulators and level-of-detail settings. Blender's normal Wavefront export command cannot produce these features and is the wrong exporter for this job.
| Model being created | Blender output | What completes it |
|---|---|---|
| Aircraft exterior or cockpit | OBJ8 files and textures | An .acf aircraft made in Plane Maker |
| Airport or scenery object | OBJ8 files and textures | A scenery package with placement performed in WorldEditor |
| Animated component | OBJ8 containing animation and dataref commands | A working X-Plane dataref, command or aircraft system |
You can inspect a complete Blender-built aircraft package containing OBJ assets and an ACF file to see how the visual model and aircraft definition remain separate.
How to export a Blender model to X-Plane
The reliable workflow is to configure the target first, clean the mesh, prepare X-Plane-compatible textures and only then add animation or export settings.
- Choose the model's purpose. Decide whether it is an aircraft exterior, cockpit, scenery object or animated part. This determines its origin, required datarefs, texture treatment and how it will be installed in X-Plane.
- Install a compatible XPlane2Blender release. Use Blender's add-on or extension preferences to install and enable the exporter package. Match the exporter release to your Blender generation; an old add-on may fail to load or may expose settings intended for an earlier Blender interface.
- Set the scale and orientation. Work in metres, with one Blender unit representing one metre. For an aircraft, the nose normally faces Blender's negative Y direction and Z points upwards; the exporter converts this to X-Plane's coordinates. Put the origin somewhere meaningful, such as the aircraft reference point or the base of a scenery object.
- Apply transforms before rigging. Apply rotation and scale once the object has the correct dimensions. Unapplied or negative scales commonly produce reversed normals, displaced animation pivots or models that appear at the wrong size.
- Clean the geometry. Remove duplicate and internal faces, correct outward-facing normals and check non-manifold areas. X-Plane ultimately renders triangles, so triangulate deliberately where automatic triangulation could change a curved surface or moving component.
- UV-map and save the textures. Assign image textures through UV coordinates and save the actual image files inside the aircraft or scenery package. Packing images into the
.blendfile is not enough. Procedural nodes and complex Blender shaders must be baked to image maps because X-Plane does not reproduce the Blender material graph. - Create an export root. Mark the intended collection or hierarchy as an X-Plane exportable root and set its output path. The exact panel terminology differs between exporter generations, but only objects included under an enabled export root are written to the OBJ8 file.
- Configure X-Plane properties. Select the appropriate object type, texture references, level-of-detail ranges and simulator target where the exporter exposes them. Keep filenames and path capitalisation consistent because case mismatches can break textures on case-sensitive installations.
- Export and test in X-Plane. Run the X-Plane exporter, place the OBJ and textures within the aircraft or scenery package, then load it in the simulator. Check X-Plane's root-level
Log.txtfor the object filename, missing resources, unsupported attributes and parsing errors.
An X-Plane OBJ normally uses one main texture set, with associated lit and normal or metalness maps where supported. Split a large model only when it needs separate texture sets, animation groups or practical LOD control; excessive splitting creates extra drawing work.
How do I add Blender animations and datarefs?
XPlane2Blender exports animation only when the moving hierarchy is associated with an X-Plane dataref and its keyframes are mapped to dataref values.
- Place an object's origin or bone pivot precisely on the hinge before animating a door, control surface or undercarriage leg.
- Build the parent-child hierarchy in the order the parts must move. A wheel attached to a bogie, for example, must inherit the bogie's movement without losing its own rotation.
- Assign the correct X-Plane dataref and define the dataref value represented by each keyframe. Blender frame numbers alone do not tell X-Plane when an animation should move.
- Use show or hide animation where a component should appear only under specific conditions, rather than moving it far outside the model.
- Add cockpit manipulators only to surfaces intended to receive mouse interaction, and associate them with the appropriate X-Plane command or writable dataref.
Check the full dataref range in Blender and in the simulator. Reversed movement usually means the dataref values or rotation endpoints are swapped; rotation around the wrong point indicates an incorrect origin, bone or parenting hierarchy. This adapted and animated Piaggio aircraft package provides a practical example of Blender-created geometry prepared for X-Plane use.
Why is my Blender model invisible or untextured in X-Plane?
Most failed Blender exports come from an excluded collection, an incorrect resource path, unsupported materials or transforms that were never applied.
| Symptom | Likely cause | Fix |
|---|---|---|
| No OBJ file is created | No valid export root, incompatible exporter or an export validation error | Confirm that the collection is enabled for X-Plane export and read the exporter report |
| OBJ loads but is invisible | Wrong placement, extreme scale, hidden geometry or unsuitable LOD limits | Check dimensions, origin, placement and LOD ranges; search Log.txt for the filename |
| Model is white | Missing texture, unsaved image or unsupported procedural material | Save a UV-mapped image texture inside the package and correct the OBJ texture reference |
| Parts look transparent or inside-out | Reversed normals or a negative scale | Apply scale, recalculate normals and remove duplicate faces |
| Animation remains static | No dataref mapping or an unusable dataref range | Assign the intended dataref and map keyframes to explicit values |
| Surfaces flicker | Overlapping coplanar faces | Remove the duplicate surface or separate it enough to prevent z-fighting |
Texture paths should remain inside the aircraft or scenery package. Avoid absolute paths pointing to a personal project directory: they may work on the development computer but fail immediately after the package is moved or shared.
Do I need Plane Maker or WorldEditor after export?
Yes—an exported OBJ8 file is a visual asset, not a complete X-Plane aircraft or scenery installation.
For an aircraft, Plane Maker creates and edits the .acf file that defines the flight model, dimensions, engines, systems, mass properties and attached OBJ files. Our practical guide to working with Plane Maker covers that side of the process without duplicating it here.
For scenery, place the OBJ within a correctly structured custom scenery package and use WorldEditor to position it in the scenery tile. Keep the source .blend outside the distributable package unless you specifically intend to include it.
Can any Blender model be converted to X-Plane?
No. The geometry must be sensibly scaled, UV-mapped and efficient enough for real-time rendering, while its licence must permit conversion and redistribution.
Dense models made for offline rendering often need reduced polygon counts, baked materials and planned LOD ranges. You must also own the model or have explicit permission to convert it; importing an asset into Blender does not grant the right to distribute it as an X-Plane add-on.