648
edits
Areas populated with osm2city scenery: Difference between revisions
Areas populated with osm2city scenery (view source)
Revision as of 09:26, 18 January 2020
, 18 January 2020→FlightGear Versions
Merspieler (talk | contribs) |
|||
| Line 12: | Line 12: | ||
|} | |} | ||
If a table entry specifies both 2017.2 and 2019.3, then it means there is a sub-folder "Buildings_list" within the scenery. By renaming folder "Buildings" to "Buildings_mesh" and then renaming "Buildings_list" to "Buildings" you can transform from | If a table entry specifies both 2017.2 and 2019.3, then it means there is a sub-folder "Buildings_list" within the scenery. By renaming folder "Buildings" to "Buildings_mesh" and then renaming "Buildings_list" to "Buildings" you can transform from 2017.2 to 2019.3 and get the rendering advantages. (There is no requirement for such a folder structure - vanosten might provide some of the sceneries like this for convenience.) | ||
There are older osm2city sceneries around, but there is no reason to use an old FG version: if your computer does not run a newer version, then chances are high that the rendering of osm2city will be poor, too. | There are older osm2city sceneries around, but there is no reason to use an old FG version: if your computer does not run a newer version, then chances are high that the rendering of osm2city will be poor, too. | ||