![]() Using the FlightGear FlightGear_Qt_launcher both the terrain and the airport are "installed" by going to tab "Add-ons" and then add the respective folders to "Additional scenery folders". The scenery files above are compressed and include the "vpb" folder. To be recognized by FlightGear, the selected scenery (from the table above) must be located in a folder with a "vpb" subfolder, such as (EX: C:\mysceneryfolder\hawaii\vpb). Uncompress the downloaded scenery files into a folder of your choice, such as E:\MySceneryFolder. You can find them here Scenery Files Placement In addition to the selected areas above, global up-to-date WS3.0 airports have been built. If you are using merspieler's updated airports, then it will most often work fine, but there might be residuals (e.g. PNG Includes high resolution water raster from OpenStreetMap. Osm2city buildings, trees, maritime, pylons etc. 230 MB) - San Francisco Bay and San Pablo Bay PNG for most pilots this is the only scenery that works without troubles. If you set these in your scenery path ahead of any other scenery, it will pick up osm2city, scenery objects etc. If you don't wanna deal with changing your terrasync settings, you can always download sections of scenery via the links individually and added to your scenery path. As of writing () it contains all of the sceneries below (duplicates removed) and will get updated when a new Airports package is made and when Wayne provides her with new US scenery. Scenery is currently not distributed using the official Terrasync, Nia provides a terrasync compatible download, point your terrasync client to to make use of it. 2.1 WS 2.0 scenery might still be needed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |