I use P3D 5.2 with Orbx scenery. I see glaringly misplaced roads in the scenery. They are clearly drawn over a background scenery. Either this background or the roads must be very incorrectly placed.
I have tried remove them in Global Vector configuration. And also uninstalling Vector. Then tried uninstalling Global and then reinstall it. Nothing helps.
I also see these roads in regions like PNW. You can see example of this incorrect scenery in the Orbx Central. Select Global Vector the third and fourth pictures show what I mean.

 

As far as I could figure out the roads are part of the default vector data, the default V5.x vector data is much more extensive than the V4.x data (and the ORBX vector data). Not sure how to get rid of it though and they will never line up land class tiles unfortunately.

10 hours ago, pinepix62 said:

As far as I could figure out the roads are part of the default vector data, the default V5.x vector data is much more extensive than the V4.x data (and the ORBX vector data). Not sure how to get rid of it though and they will never line up land class tiles unfortunately.

But is not the Orbx scenery supposed to write over the default scenery ?

Alas, you might as well give up. You can't get rid of this. Using Orbx Global and Vector reduces it, but you can never get rid of it completely. I suppose you could go MSFS....

The land class layer is at different level (separate bgl files) from the vector, dem and autogen layers. Most of the ORBX regions replaces the land class definition and the tiles with better looking tiles (and I suppose the autogen layers that goes with the land class tiles). The ORBX TrueEarth that are based on aerial  photos solves this problem and like mentioned MSFS does not use the land class method as the whole globe is based on aerial imaging.

1 hour ago, andreh said:

Alas, you might as well give up. You can't get rid of this. Using Orbx Global and Vector reduces it, but you can never get rid of it completely. I suppose you could go MSFS....

But could not a developer do something ?
And yes I have noticed that MSFS is much better in this regard. Although there is a problem with mis colored roads but that is not so glaringly incorrect as the misplaced roads in P3D.

1 minute ago, jfri said:

But could not a developer do something ?
And yes I have noticed that MSFS is much better in this regard. Although there is a problem with mis colored roads but that is not so glaringly incorrect as the misplaced roads in P3D.

The only thing I can think of is meticulously handcrafted sceneries, like Orbx TrueEarth.

Ultimate Terrain has an 'Exclusion for Default Scenery' layer that, when moved to the proper place, hides the low-res roads showing on top of lakes and such. I don't know if there is such a layer in Global Vector. I'm using UTX with Global Base and Global openLC. Took a while to get it right and it was a pain in P3D 5 with the scenery layer changes, but I'm very happy with the combination now.

I'm not on my home PC right now, but I can look it up tonight and post here if more info is desired.

6 hours ago, jfri said:

But could not a developer do something ?
And yes I have noticed that MSFS is much better in this regard. Although there is a problem with mis colored roads but that is not so glaringly incorrect as the misplaced roads in P3D.

IIRC, you can turn off most of the roads and the railways by unchecking all the boxes in the Vector config tool, accessed via the 'Configure' button on the Vector product page in Orbx Central.


I think there may be a little misunderstanding about what landclass can and cannot represent compared to photoreal.
The roads are not misplaced. They are based on OpenStreetMap data and actually follow the real-world positions quite closely (within the limitations of how the sim can represent them).

The actual problem is the way the landclass textures are drawn.

See below how the fields bisected by the river in the middle of the picture are identical on either side?
The river is not in the wrong place. The data saying 'display field here' is not wrong either, it's just that the image representing the fields is incorrect.
It's clever how realistic-looking landclass can be, but that road leading to the river would not just stop like that in reality, especially considering its size.

 

Let's look at another landclass image below. The brown field in the middle left would never exist like that in real life. While the data says 'put field here', the brown and yellow field to the left of the freeway would never occur in real life. Similarly, the light green field bisected by the freeway junction in the bottom right of the image.
That's to say, the data is correct to real life, the way it is represented as drawn is not.

Landclass:

 

Photoreal / Ortho:

While fields in the real world are oddly shaped, there is a natural border to them as defined by roads, urban areas, industrial areas, etc. compared to the way landclass displays them.
 

I agree it's actually quite remarkable how good p3d can look considering the system it's based on. I fly airliners so I rarely get a good look at the scenery anyway so its more than enough for me.

Have you ever considered making your own Ortho scenery?

I have made the whole of the UK at zl 17 and it knocks spots off of anything offered commercially.

Better still, it's free!

Best....  Phil

12 hours ago, philmurfin said:

Have you ever considered making your own Ortho scenery?

I have made the whole of the UK at zl 17 and it knocks spots off of anything offered commercially.

Better still, it's free!

Best....  Phil

I have doing that for XP11 where I found instructions on how to do it. But found no such instructions for P3D.
And also it's very much work to do it and it consumes very much storage memory. But of course the Ortho I have XP11 surely does not have the corrupted scenery I describe in this thread. Actually the airport closest to where I live (ESGP Säve) is the most accurate in my XP11 ortho among all sims I have (MSFS P3D FSXSE XP11)

Making Ortho  for P3d is as easy as making it for XP. It is virtually the same program and it just requires 2 extra clicks.

Ortho does take up a lot of space, 4 times more for each increase in zoom level, you could always try zl 14 or 15 and see how that looks for you.