A short reply on the last 10 or so messages. The LOD loading behavior can be tricky. In FG NEXT a new parameter (which osm2city uses) is introduced to make some calculations more fair. So in the next FG version with osm2city built with FLAG_AFTER_2020_3 some of this should improve - but not everything has been coded yet.
When discussing osm2city please always tell where you got the scenery from (e.g. worldbuild) and/or whether it is using building lists (aka. shader buildings - visually detectable by "rectangular houses seems to look more the same and are darker"). The loading behavior is different. Building lists are loaded per tile and in worldbuild larger and smaller houses (the ones not in building lists) are loaded in squares (ca. 3x3 km), with larger buildings having the medium LOD and therefore typically loading sooner.
If you are not within LOD distance, then FG typically does not load it. See also
https://osm2city.readthedocs.io/en/late ... ry-objects (I use larger distances with my graphics card). Therefore, you also need to mention your FG LOD settings when discussing such matter.
In upcoming osm2city with FLAG_AFTER_2020_3 some of this will change as more buildings etc. will be rendered per tile.
Lastly: as osm2city is relatively heavy on disk usage, putting scenery on an SSD does not hurt.