![]() ![]() ![]() (There is no requirement for such a folder structure - vanosten might provide some of the sceneries like this for convenience.) ![]() By renaming folder "Buildings" to "Buildings_mesh" and then renaming "Buildings_list" to "Buildings" you can transform from 2017.2 to 2020.1 and get the rendering advantages. If a table entry specifies both 2017.1, then it means there is a sub-folder "Buildings_list" within the scenery. Your FG will most probably crash immediately if you use such a scenery with an older FG version. The big change is the possibility to render the majority of buildings with the FG random buildings shader, which results in faster rendering and depending on the region a factor 4-10 reduction in disk size. The FlightGear versions mentioned in the tables below indicate compatibility as follows: Note: You only need to download from this page if: a) your internet connection is limited or, b) you are looking for OSM2City scenery built with different options or a new OSM2City version than the rollout on TerraSync or, c) you are using an old version of FlightGear and can't update to 2020.3.8 LTS or later. The OSM2City manual describes how to use the sceneries in FlightGear. This article contains a list of areas having osm2city generated scenery available for manual download. 2020.3.6 LTS and earlier will not automatically download OSM2City. OSM2City scenery for the whole world has been generated from the objects in the OSM database - see 1st world-build of OSM2City. ![]() See here for more screenshots.Īs of FlightGear 2020.3.8 and later, the normal way to get OSM2City is automatic downloads as you fly through TerraSync with the latest version of FlightGear. OSM2City output for Madrid, Spain - 2017.2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |