Getting Started with World Editor

Before you begin designing scenery, download the latest stable version of World Editor from the official X Plane developer site. WED is available for Windows, macOS, and Linux. Once installed, launch the application and take time to explore the interface: the main 3D viewport, the hierarchy panel (listing airports, objects, and terrain polygons), and the properties palette. Familiarize yourself with keyboard shortcuts—especially G to grab and move objects, R to rotate, and F to toggle full screen—to speed up your workflow.

Start with a small, manageable project, such as adding a few hangars to a default airport. This builds confidence before tackling a full custom scenery pack. WED uses a tile-based system: each tile represents a 1×1 degree area of the real world. When you create a new project, you choose a tile by entering latitude/longitude coordinates or selecting from a map. The tool auto-loads default X Plane data (airports, roads, forests) for that tile, which you can modify or replace.

Planning Your Scenery Pack

Every great scenery pack begins with a clear vision. Decide on the primary focus: a detailed airport, an urban environment, a natural park, or a combination. Gather reference materials: satellite imagery from Google Earth, airport diagrams from AirNav or official charts, and photographs of buildings, signage, and vegetation. Organize your references in a separate folder so you can consult them while working.

Create a checklist of features you want to include: runways, taxiways, apron markings, lighting, buildings, vehicles, static aircraft, trees, water bodies, and terrain mesh corrections. Prioritize elements that most affect immersion. For example, accurate runway markings and approach lighting matter more than decorative benches. Also consider the performance target: a highly detailed pack for a major airport may need LOD (level of detail) versions of objects to maintain frame rates.

Designing the Terrain

X Plane’s global scenery provides a base mesh, but WED lets you refine it with custom elevation, water, and landclass. Use the Terrain tools (click the terrain icon in the top toolbar) to add, remove, and reshape terrain polygons. For realistic undulations, work with elevation points: click a vertex and adjust its Z value in the properties panel, or use the Elevation brush to paint hills and depressions.

Water is handled separately: place a Water polygon from the toolbar and adjust its boundaries to match shorelines. For rivers and small lakes, use multiple polygons. Remember that water polygons must be flat and at sea level (elevation 0) to avoid artifacts. If your scenery is coastal, blend the water edge with the existing ocean using a soft transition.

For landclass (the texture painted on the terrain), click the Landcover button and choose categories such as urban, forest, grass, or beach. Apply these polygons over your terrain to force X Plane to display the correct autogen textures. This is especially useful for correcting mismatches between the default scenery and your custom objects.

Working with Mesh and Overlays

X Plane uses two layers: the physical mesh (elevation, water, landclass) and the overlay (objects, facades, strings). The mesh defines the shape of the Earth; the overlay places things on it. When you export your scenery, WED generates a .mesh file for terrain changes and a .overlay file for objects. Keep these separate to allow other scenery packs to coexist without conflicts. If you only modify objects without touching elevation, you can skip the mesh export entirely—this keeps your pack lightweight and compatible with orthophoto scenery.

Placement of Objects and Features

Populating your scenery with objects is where it comes to life. WED includes a vast library of default X Plane objects: trees, buildings, vehicles, windsocks, runway signs, taxiway edge lights, and more. To place an object, open the Library panel (Window > Library), browse or search for an item, then click to place it in the viewport. Hold Shift to lock placement to the ground elevation. Use Ctrl+D to duplicate objects quickly.

For realistic airports, pay attention to the order of runway markings. X Plane uses a system of Lights and Signs objects that automatically adapt to the runway orientation. Place Runway lighting objects (edge lights, threshold lights, PAPI) from the library and align them with the runway’s edge. For taxiways, use Taxiway polygons (not just objects) to paint surface markings—they respond to the surface type (asphalt, concrete) and display proper shoulder textures.

To import custom 3D models, export them as .obj files using a 3D modeling tool like Blender or SketchUp, then place them in a folder inside your scenery package. In WED, click File > Import obj to bring them into the library. For complex buildings, consider creating LOD models (e.g., a detailed version for close-up, a simplified version for distance) to maintain performance. Name them with suffixes like _LOD0, _LOD1; WED will automatically handle transitions.

Facades and Strings

For long, linear structures like fences or walls, use Facades (pre‑made repeating panels) or Strings (lines of objects). Facades are especially efficient: they stretch to any length without increasing polygon count. Select a façade from the library (e.g., a hangar wall), click to define its start and end points, and adjust height in the properties panel. Strings work similarly but use an array of individual objects along a path—ideal for rows of trees, lampposts, or parked cars.

Finalizing and Exporting Your Scenery

Before exporting, run WED’s validation tools. Click Validate Scenery from the File menu (or press Ctrl+Shift+V). WED will check for common errors: overlapping runways, missing airport boundaries, misplaced objects, invalid elevation, and missing textures. Fix all errors and warnings—a scenery pack that fails validation may crash X Plane or display incorrectly.

Next, test your scenery in X Plane. Save your WED project, then click File > Export Scenery Pack. Choose a destination folder inside X Plane’s Custom Scenery directory. Give the folder a descriptive name (e.g., KLAX Custom v1.0). Launch X Plane, navigate to your airport, and inspect each area: runway alignment, taxiway markings, building positions, lighting, and terrain transitions. Use the Local map (M key) to verify object placement from above. If something is off, return to WED, adjust, re-export, and test again.

For large packs, export incrementally. Export only the mesh first, test terrain, then add objects. This isolates problems. Also check performance with the X Plane frame rate counter (Ctrl+Shift+F). If frame rates drop below 20 FPS, simplify objects, reduce object density, or create LOD models.

Advanced Techniques for Stunning Visuals

Once you master the basics, elevate your scenery with these techniques:

  • Orthophoto overlays: Use tools like Ortho4XP to generate high-resolution satellite imagery as a base texture. WED’s terrain polygons sit on top, so you can blend custom landclass with real‑world imagery. Ensure the overlay elevation matches the orthophoto’s ZL (zoom level) to avoid floating objects.
  • Dynamic lighting: In WED, set the Light Level property on objects to make them cast light at night. Use the _LIT texture variant for custom objects to give them night windows, signs, or runway edge lights.
  • Animated objects: Place animated objects from the library (e.g., windsocks, rotating radar) or create your own using the Animation tab in the object’s .obj file. For simple animations (rotation, translation), .obj files support keyframes—consult X Plane’s OBJ8 specification.
  • Seasonal variations: If your scenery is in a region with distinct seasons, create separate .obj files for winter (snow texture) and summer, then reference them in WED with the Season property. X Plane will switch automatically based in‑sim date.
  • Ground traffic routes: For airports, define vehicle paths using Ground Traffic strings. Connect baggage carts, fuel trucks, and follow‑me cars to make the apron feel alive. Use the Traffic tool in WED’s toolbar to draw the route and set speed/type.

Optimizing Performance

Even the best scenery is useless if it chokes your simulator. Keep these optimization principles in mind:

  • Object density: Don’t place trees or small objects within 50 meters of runways—X Plane already has built‑in exclusion zones for safety, but you can add explicit exclusion rectangles in WED (right‑click the airport > Add Exclusion Zone). Exclude objects, forests, facades, and autogen.
  • LODs: For custom objects, create at least two LOD levels. The detailed LOD0 appears within 500‑1000 meters; LOD1 (simplified) beyond that. Use WED’s LOD property on each object to set the distance at which it disappears entirely—culling distant objects saves GPU work.
  • Texture resolution: Keep textures at 1024×1024 or 2048×2048 for most buildings. Only use 4096 for critical surfaces like runway markings. Compress textures as DDS with mipmaps (using tools like GIMP with DDS plugin or NVIDIA Texture Tools).
  • Batch objects: Instead of placing many identical objects individually, use String objects for lines of trees or lights. Strings internally batch geometry, reducing draw calls.
  • Terrain mesh complexity: Avoid adding too many elevation vertices. The human eye notices broad shape, not every bump. Use a LIDAR‑derived DEM if high accuracy is needed, but simplify before importing—WED can handle tens of thousands of vertices, but X Plane’s loading time grows with complexity.

Testing and Troubleshooting Common Issues

When you export and load your scenery in X Plane, watch for these frequent problems and their fixes:

  • Objects floating in the air: Your terrain mesh may not match the object’s ground elevation. Ensure the object is placed on a flat area or adjust its Y offset in WED. If using orthophoto, verify that the .mesh file uses the same elevation source as the ortho tile.
  • Runways invisible or misplaced: Double‑check the airport header in WED: the runway’s latitude/longitude, elevation, and heading must be precise. Use the Align Runway tool (right‑click runway > Align to Magnetic North) for correct orientation.
  • Texture flickering (z‑fighting): This happens when two polygons occupy the same plane. Avoid overlapping airport markings on the runway—delete the default runway markings and replace them with WED’s Runway polygon itself.
  • Scenery load failure: Open X Plane’s log.txt in the main folder. Search for your scenery pack name to see error messages. Common causes: missing .obj files, incorrect library paths, or broken texture references.
  • Low frame rate: Use X Plane’s FPS in cockpit display and look for regions where object density is high. Add exclusion zones or reduce object count in that area. Check if any object uses an unnecessarily high‑resolution texture.

Sharing and Contributing to the Community

Once your scenery pack is polished, share it on platforms like X‑Plane.org’s Scenery Downloads or the X‑Plane Gateway for default airport submissions. Write a clear description, include screenshots showing key features, and mention system requirements (e.g., “requires Ortho4XP tiles in ZL17”). Credit any custom objects or textures you didn’t create yourself. For Gateway submissions, follow Laminar Research’s guidelines: only use default objects, keep file size under 5 MB, and ensure the scenery matches real‑world data as of the current AIRAC cycle.

Consider joining the X‑Plane developer community on the X‑Plane.org Forums or Discord channels. Share your work in progress for early feedback. Other users may spot terrain misalignments or missing objects you missed. A second pair of eyes can turn a good scenery pack into a stunning one.

Conclusion

Creating breathtaking scenery packs for X Plane with World Editor is a rewarding process that combines technical precision with artistic creativity. By mastering terrain editing, object placement, validation, and performance optimization, you can craft immersive environments that transform every flight. Start small, iterate often, and always test in‑sim. With patience and attention to detail, your custom airports and landscapes will become destinations that fellow pilots seek out. Happy designing, and we look forward to seeing your creations take to the virtual skies.