Getting Started with Aerofly FS Scenery Creation

Creating custom scenery and airports for Aerofly FS transforms the flight simulation experience from passive flying into an interactive creative process. Whether you want to add your hometown airport, improve an existing field, or build an entirely fictional landscape, the Aerofly FS Software Development Kit gives you the tools to bring your vision to life. This expanded guide covers the entire workflow from initial setup to final packaging, with practical advice for both beginners and experienced creators.

Understanding the Aerofly FS Ecosystem

Aerofly FS uses a dedicated file format and engine optimized for high performance and realistic rendering. The official Aerofly FS SDK is the primary tool for importing, assembling, and exporting scenery packages. Unlike some other simulators that rely on generic formats, Aerofly FS expects models in its native TGI (Texture, Geometry, Instance) format, with textures in DDS (DirectDraw Surface) or PNG. Understanding this pipeline is critical before you begin modeling.

The simulator supports both airport layouts (runways, taxiways, parking positions) and surrounding scenery (buildings, trees, terrain, objects). The SDK handles all coordinate transformations, so you only need to provide geometry and textures. The engine uses a tile-based system for large areas, meaning you can create seamless extensions to existing regions without overwriting base content.

Essential Software and Setup

1. Core Tools

  • Aerofly FS SDK – Download the latest version from the developer website. Install it to a convenient location (not inside the simulator folder). The SDK includes import/export scripts, documentation, and sample projects.
  • 3D Modeling Software – Blender (free, open-source) is the most widely used choice. It offers powerful modeling, UV unwrapping, and scripting tools. You will need the Blender add-on provided by the SDK to export models to the TGI format.
  • Image Editor – GIMP (free) or Photoshop (paid) for creating textures. DDS plugin support is recommended; GIMP with the DDS plugin works well. Photoshop with the NVIDIA DDS plugin is a common professional setup.
  • GIS Software (Optional) – For precise placement using real-world coordinates, tools like QGIS or Google Earth can help you gather geographic data.

2. Preparing Your Workspace

  • Create a dedicated project folder. Inside, subfolders for models, textures, reference, and output.
  • Install the SDK’s Blender add-on (typically a .zip file placed in Blender’s addons folder). Enable it in Blender’s preferences.
  • Set up your coordinate system in Blender to match Aerofly FS: use meters, and orient your models so that the positive Y-axis points north. The SDK documentation provides exact axis conventions.

Step-by-Step Scenery Creation Workflow

Step 1: Planning and Reference Gathering

Before opening any 3D software, decide what you want to create. For an airport, obtain the following reference materials:

  • Satellite imagery from Google Maps or Bing Maps. Use an image overlay add-on in Blender to trace runways and taxiway shapes.
  • Airport diagrams from sources like FAA or ICAO charts (for real airports).
  • Photographs of buildings, hangars, and terminal architecture. Ideally take your own photos to capture accurate textures.
  • Geographic coordinates of key points (runway thresholds, parking spots). Aerofly FS uses latitude/longitude with WGS84 datum.

For fictional or improvised scenery, gather concept art or draw a simple layout plan. Keep in mind that even fictional creations benefit from realistic proportions and lighting considerations.

Step 2: Modeling the Airport Layout

Start with the ground elements: runways, taxiways, aprons. These are typically flat planes with specific surface definitions in the SDK.

  • Runways – Model a rectangle with correct length/width. Use a separate material for the runway surface (concrete/asphalt) and markings (centerline, edge lines).
  • Taxiways – Model as paths (can be a series of rectangles or a custom polygon). Keep taxiway width consistent (usually 15-30 meters depending on airport size).
  • Aprons – Larger polygonal areas for parking. Add markings for parking spots, guidance lines, and tie-down points.
  • Signage – Optional for realism. Use small 3D signs or decal textures.

In the SDK, you will assign categories to these ground objects (e.g., runway, taxiway, apron) so the simulator understands their function and applies correct surface friction and lighting.

Step 3: Creating 3D Models for Buildings and Objects

Now model the structures. Common airport buildings include terminals, control towers, hangars, fuel depots, and maintenance facilities. For generic objects, use these guidelines:

  • Low-poly approach – Aim for as few polygons as possible while retaining recognizable shapes. Aerofly FS handles up to several million polygons, but performance drops with overly dense meshes. Use LOD (Level of Detail) for large structures.
  • Clean topology – Avoid n-gons and zero-area faces. Quads are preferred for UV unwrapping.
  • Real-world scale – Ensure all dimensions in Blender match meters. A 20-meter tall tower should be exactly 20 units high.
  • Pivot points – Set each object’s origin at its base center (on the ground plane). This simplifies placement in the SDK.

For vegetation, use simple crossed-plane trees or billboard objects. The SDK supports volume objects (like 3D tree models) as well, but crossed planes are more performant for large forests.

Step 4: Texturing Your Models

Realistic textures dramatically improve immersion. Follow these practices:

  • UV unwrap every model. Use smart UV project or manual seams for control. Keep UV islands proportional to avoid stretching.
  • Texture resolution – 1024x1024 or 2048x2048 for buildings. Runways and large ground areas can use larger tiles (4096x4096) but watch memory usage. Use DXT1 compression for opaque textures, DXT5 for alpha channels.
  • PBR (Physically Based Rendering) – Aerofly FS supports metallic/roughness maps. If your 3D software can bake normal and roughness maps, include them for better lighting response. The SDK expects specular/glossiness in older versions; check version requirements.
  • Diffuse maps should be photographic or hand-painted with realistic color values. Avoid oversaturated colors.
  • Markings – Runway numbers, threshold markings, and taxiway signs can be applied as decal textures or modeled as separate geometry with transparent cutouts.

Step 5: Using the SDK to Assemble the Scenery

Once all models and textures are ready, launch the SDK’s Scene Editor (part of the SDK tools). The workflow:

  1. Create a new project and set the geographic center (latitude/longitude). This defines the tile region.
  2. Import ground layout – The SDK can import ESRI shapefiles or simple CSV coordinate lists for runways/taxiways. Alternatively, manually place ground polygons using the editor’s tools.
  3. Place 3D objects – Import your TGI models and position them using the 3D view or by entering coordinates. The SDK provides snap-to-grid and elevation tools.
  4. Add lighting – Place runway edge lights, PAPI, and taxiway lights. The SDK includes predefined light objects with various colors and patterns.
  5. Add parking spots – Define gates with specific aircraft types, sizes, and fuel availability. This is essential for AI traffic and multiplayer functionality.
  6. Set navigation aids – For a functional airport, add ILS, VOR, NDB, and waypoint data. This requires knowledge of aviation navigation; the SDK includes a navigation editor.

Step 6: Testing and Iteration

Export your scenery to the Aerofly FS installation’s scenery folder. Test by loading a flight at the new location. Check the following:

  • Visual accuracy – Compare with reference photos. Are building heights correct? Colors matching?
  • Surface behavior – Taxi across runway/taxiway transitions. Aircraft should not jitter or sink.
  • Lighting – Test at various times of day and weather conditions. PAPI and runway lights should be visible from appropriate distances.
  • Performance – Monitor frame rates. If FPS drops, reduce polygon count, lower texture resolutions, or simplify lighting.
  • ATC and navigation – If you added navaids, verify they work by selecting an approach in the flight planner.

Iterate based on findings. The SDK’s hot-reload feature (if supported) lets you tweak object positions or textures without restarting the simulator – use this for rapid adjustments.

Step 7: Packaging and Distribution

Once satisfied, package your scenery for distribution. The standard format is a .tgi file plus a .txt metadata file. Many creators provide a ZIP archive containing the package with installation instructions. Include:

  • A readme with credits, required SDK version, and installation steps.
  • Optional screenshots or a small preview video.
  • License details (e.g., freeware, payware, open-source).

You can share on the Aerofly FS forum, flight sim community websites, or your own platform. Be prepared to support users with questions.

Advanced Techniques for Realistic Scenery

Terrain and Elevation

Aerofly FS uses its own terrain mesh. To modify terrain (e.g., flatten an airport site or add a hill), you need to create a custom elevation map. The SDK includes tools for importing GeoTIFF or DTM (Digital Terrain Model) data. Use QGIS or other GIS software to generate a relief map of your area. Apply smoothing to avoid sharp edges. For airports, you can flatten the entire apron area to a constant elevation.

Custom Vegetation and Objects

The SDK allows you to define custom object libraries. Create a .tglib file listing your models, tags (e.g., “tree”, “building”, “streetlight”), and LOD settings. Then place these objects individually or use the random scatter tool for forests. This method reduces file size and speeds up loading.

Dynamic Elements

Add animated objects like windsocks, rotating beacons, or ground vehicles. Aerofly FS supports simple animations (rotations, translations) defined in the SDK. For complex animations, you may need to write Lua scripts, but that is beyond basic scenery creation.

Common Pitfalls and How to Avoid Them

  • Incorrect coordinate systems – Double-check that your models align with real-world GPS. A 1-meter offset at the airport threshold can cause incorrect terrain collision.
  • Texture tearing or glitches – Ensure DDS files are power-of-two dimensions and compressed with the correct format for alpha transparency. Use mipmaps for distance rendering.
  • Missing collisions – Ground objects need collision meshes defined. The SDK can auto-generate collisions from geometry, but complex shapes may cause issues. Test landing on all surfaces.
  • Overcomplicated models – Keep your first few projects simple. A single hangar and a runway are a good start. Scale up only once you master the workflow.
  • Ignoring documentation – The SDK comes with manuals and example projects. Read them thoroughly. The Aerofly FS community also provides tutorials; search for “Aerofly FS scenery creation” on YouTube.

Conclusion: Elevating Your Flight Sim Experience

Creating custom scenery for Aerofly FS is a rewarding endeavor that blends artistry, technical skill, and aviation passion. Whether you are replicating your home airport, building a fantasy island, or contributing to the community, the process outlined here gives you a solid foundation. Start small, test often, and don’t hesitate to seek feedback from fellow enthusiasts. With each project, your models will become more detailed, your workflows more efficient, and your virtual world more immersive. Now open Blender, launch the SDK, and bring your airport ideas to life.