I could finally figure it out. The thing causing the road-offset was the orthophoto scenery I created long ago with g2xpl. I tried to remove a bunch of stuff but never expected orthos to contain road data (or data interfering with roads). After Disabling them in scenery.ini everything looked good again. Thanks anyway for sharing your thoughts!

I made a mod on the .org that is a temp fix for the apts… basically made the obj sunk into the ground..

It would epic to get the Caribbean in HD mesh. Many of the islands do not have the proper definition in the mesh to represent the terrain. Notably TFFJ in St. Barths and also Saba. These are the two most challening airports in the Caribbean and the mesh looks nothing like the real thing, so there really is no “simulation” there.

Thank you kindly.

We have more than considered it … we once _tried_ it. Albeit this was a long time ago, but the results were _not_ a good. Basically a huge chunk of our user base wasn’t torrent-savvy and was really annoyed that downloading wasn’t click-and-go. This is why we built our installer with multiple servers backing it.

Hmmm … this screen shot seems to be more than just a simplification issue. Usually, those roads shouldn’t be that much off … expect, if they are already at a quite bad “quality level” in OSM (that can happen – OSM make no promises about quality, and can have very big differences therein).

But the OSM data around EDDF is really really good …
http://www.openstreetmap.org/#map=16/50.0512/8.6030

This screen shot looks like, as if your scenery would use something entirely different!
If I look at the same location in HD Mesh, then I get a more or less exact representation of the OSM data abov (and definitely miles better than what your picture suggests):
https://lh4.googleusercontent.com/-d5tu11eJJr0/UpkRbqhAxOI/AAAAAAAADyc/PnXFkVVtsuo/s800/Eclipse_1.jpg

I definitely recommend, that in situations like this, you double check what exactly you have installed and have running (very often people ask, why this or that is not so great in HD Mesh etc. … just to find out,that they are not even looking at it).

For the default global scenery, some simplification of road data DOES happen; I don’t know if what you see is an error in OSM, our simplification’s limits, or a bug in the orthophotos; I also don’t know how Andras’ HD mesh changes the simplification (if at all).

Hi Nino,

Alex and I looked at a lot of options when working on the autogen roads and concluded that based on current mesh tech, what we do is the least bad option. Basically the sim right now can’t dynamically flatten the terrain in small areas at the resolution needed for the roads; we looked at including ‘retaining walls’ in the roads but the result was much more distracting than what we have now. This is also compounded by the base mesh not always being accurate enough in the source data.

So someday we would like to be able to ‘bulldoze’ the ground a bit under the roads – but that would require a substantial change to how the engine works; furthermore, even if we had this, the question of how to know how to bulldoze is extremely complicated. We don’t get good elevation data off of the road data, so how do we know how far to ‘bury’ the road (and cut the ground) to get correct behavior for example, when the road is in a trench (which happens quite often for US highways in cities)?