legoboyvdlp wrote in Sat Nov 17, 2018 10:34 am:It essentially was putting houses where in real life there were only mountains. The houses also had incorrect elevation - some of the were floating in midair halfway down the mountain as it obviously queried the elevation further up. This also occurs without owbb - I think I posted a screenshot . (is it possible to query terrain slope to resolve this?)
Thorsten wrote in Fri Nov 16, 2018 8:09 am:Why is my scenery generating so slowly? I'm playing Los Angeles on the California package and the buildings aside from a couple of miles out have not yet generated, and I have let the simulator run for 20 minutes?
Because there's a LOD range definition - beyond a certain (configurable) distance no buildings won't be loaded no matter how long you wait.
vanosten wrote in Sun Nov 18, 2018 2:43 pm:What do you mean by "generating"? I guess you mean rendering in FlightGear and not what I would call generating in osm2city. My observation is that if you just stand still on the spot, then scenery is not necessarily loaded. A bit of movement or looking around might help.
If you mean scenery generation, then you can blame me, as osm2city is still using Python (instead of e.g. C++) and I spend time on features instead of performance.
Users browsing this forum: No registered users and 10 guests