![]() Currently there is limited change in appearance from one region to another.Contributions are welcome - see the scenery forum or the " fg-devel" mailing-list to help. The appearance of OSM2City buildings and objects is placeholder.Random building density can be turned up in the property browser : Try setting /sim/rendering/building-density to 1-10. It randomly creates buildings in the new OSM2City format. Flightgear has an alternative random buildings feature.This can be done by using smaller values for LoD:Rough in View menu > Adjust LOD ranges If FPS is low try reducing the distance objects are loaded.Flying away from city centers of large cities means most buildings in view are smaller buildings in the new format, and will be fast. If FPS is low try switching off pylons, random scenery objects, and roads until FPS is acceptable.Objects in new format: Smaller buildings, and randomly generated buildings. Objects in old format: Roads, Pylons, random scenery objects, and large buildings. OSM2City has objects in new and old formats.There is no need to lower graphics settings, or buy faster GPUs, if FPS is low in areas with a lot of OSM2City buildings and objects. The limiting factor is the CPU, not the GPU in most systems.It's best to wait as new hardware is also steadily getting faster, and hardware prices will also be expected to drop after the situation with the global pandemic eases.). This is because FlightGear's rendering and bottlenecks, will be changing so much in future - with WS 3.0, upcoming rendering features the compositor enables, future OSM2City, move to a higher version of OpenGL, and so on. Please don't buy new hardware yet based on early rollouts (Before buying new hardware, it's a good idea to wait until /after/ the future LTS that contains WS3.0. Performance will improve drastically in future rollouts.To force a 2nd scenery load go to in-sim GUI menu > Debug menu > Reload Scenery. You will see terrain and scenery as normal without OSM2City buildings. ![]() A limitation of the experimental rollout in 2020.3.7 is that FlightGear will not load OSM2City objects as part of the first scenery load on the first visit to an airport.If you have a custom scenery with subfolders for Terrain as well as object folders like buildings, roads or pylons, you can delete these object folders and FlightGear will then load the updated TerraSync object folders. If FlightGear sees a folder of a certain type in custom scenery at a specific location it will use that, and it will not load TerraSync objects of that type from the folder for that location. the Addons > Scenery folders section in the qt-launcher, or a command-line folders list. Remember to remove any custom scenery folders you have that contains object folders for buildings, roads, pylons to see the updated OSM2City objects on TerraSync! Old folders can be removed from where you added them - e.g. ![]() FlightGear 2020.3.6 and earlier will not download OSM2City data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |