One of the most frustrating parts of distributing custom flight simulation scenery is guiding end users through manual folder extraction, library dependencies, and editing scenery_packs.ini. World Builder Pro solves this with an integrated Standalone Installer Compiler.

1. The DAG-Based Incremental Build Pipeline

When you click Build All, World Builder executes a Directed Acyclic Graph (DAG) pipeline across four staged layers:

• Overlays: Assembles placed 3D objects, facades, forests, lines, strings, and town autogen polygons into compiled DSF overlay tiles.
• Landmarks: Compiles procedural OBJ8 models, verifies UV atlases, and ensures accompanying _LIT.png textures exist.
• Mesh & Orthos: Slices elevation triangles and compresses photographic textures with proper mipmap generation.
• Assembly & Validation: Verifies every texture reference and checks that no external library paths are missing.

2. Scenery Pack Consistency Checks

The builder performs automated sanity tests before packaging:

• Detects missing or broken texture references that would cause simulator load errors.
• Verifies that exclusion zones do not inadvertently suppress your own custom airport buildings.
• Confirms that all custom .obj and .fac definitions match official X-Plane 12 format standards.

3. Generating the Standalone Installer

In World Builder Pro, navigate to Publish > Create Standalone Installer. Configure your product title, version number, custom branding banner, and optional license agreement.

World Builder compiles a single, self-extracting executable installer for macOS and Windows. When your end users run the installer:

• It automatically locates their X-Plane 12 installation directory.
• It extracts the scenery files directly to Custom Scenery/.
• It correctly places your pack at the top of scenery_packs.ini, preventing priority ordering conflicts.