#Flightgear custom scenery how to#

Supported by stable FlightGear release (requires no patching) There are several ways of creating photoscenery for FlightGear, of which some are discussed here. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable. Shadows included in the images will conflict with shadows added by FlightGear.Since FlightGear adds haze to the scene, the textures should be 'unhazed' to avoid double hazing.

#Flightgear custom scenery how to#

The prefered way of downloading these images depends on the used method Please read how to create photoscenery, before starting. USGS, provides 3 m/pixel imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox. Orthoimagery is often hard to obtain, especially under an open license.For low level (VFR) flying, 1 m/pixel is the absolute minimum. One needs large (or many) textures for high resolution scenery.Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.Photoscenery shows the real world, it does not try to resemble it.5 Extending the photoscenery support in FlightGear.Items missing from the TerraSync and custom scenery:įor all official airport documents, including SID, STARS, IAC, etc. There is a new custom scenery made and maintained by user 'D-SVEN' available on his github. Some yet unpublished updates are to be found in this repo: a=summary Generally, changes go mostly directly into the scenery DB and are distributed via TerraSync. Prior to that you may use the AddOn-Scenery-Package from (See the README inside the package).Starting with FlightGear version 3.0 (and Scenery 2.12) the new runways and new ILS-frequencies are included and/or downloaded by TerraSync.In addition to that there is a new custom scenery with many details for the area around the airport. The version available through TerraSync is reasonably up-to date, while the version in the Git repo contains some future changes (new runway, buildings under construction). Runway 18 does not have ILS as it is used only for departures in real life.Ĭaution There is no runway 36 as that direction leads towards the Taunus mountains that would be in the way at takeoff. ILS is available for runway 25L, tune your NAV radio to 111.15 with a heading of 249.571 (prior to FlightGear version 3.0 the frequency was 110.70).ILS is available for runway 07R, tune your NAV radio to 110.95 with a heading of 069.619.ILS is available for runway 25C, tune your NAV radio to 111.55 with a heading of 249.568 (prior to FlightGear version 3.0 the frequency was 109.50).ILS is available for runway 07C, tune your NAV radio to 110.55 with a heading of 069.614.ILS is available for runway 25R, tune your NAV radio to 111.35 with a heading of 249.568.ILS is available for runway 07L, tune your NAV radio to 111.75 with a heading of 069.614.These runways are used only for landings of medium size aircraft - no starts are allowed. Three runways are positioned approximately parallel east-west, and the forth is north-south.