648
edits
Line 2: | Line 2: | ||
== FlightGear Versions == | == FlightGear Versions == | ||
The FlightGear versions mentioned in the tables below | The FlightGear versions mentioned in the tables below indicate compatibility as follows: | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 9: | Line 9: | ||
| 2019.3 || 2019.2 x-mas and all newer versions || traffic, regionalization || yes || 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. Your FG will most probably crash immediately if you use such a scenery with an older FG version. | | 2019.3 || 2019.2 x-mas and all newer versions || traffic, regionalization || yes || 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. Your FG will most probably crash immediately if you use such a scenery with an older FG version. | ||
|- | |- | ||
| 2017.2 || 2017.2 and all newer versions || traffic, regionalization || yes || | | 2017.2 || 2017.2.2 and all newer versions || traffic, regionalization || yes || | ||
|} | |} | ||
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. | |||
== Available areas == | == Available areas == |
edits