FSX-MS FSX Orbx OLC USA Indiana pyramids

[kttd 12]

It used to be fairly easy to log on to Orbx and post a problem but it seems sort of difficult now, at least for me.  Have not been there in years.  Maybe someone has had this same issue. 

FSX - Orbx - OLC USA - Indiana

pyramids

 

[Patco Lch 1,485]

Could it be an elevation issue caused by ORBX Vector? Or a layering issue in the scenery library? Just a thought.

[Luis Hernandez 594]

Landclass shouldn't affect mesh. Are you using any mesh in that area?

[kttd 12]

Howdy airplane friends.  No extra LC or Mesh.  

Downloaded OLC twice from Orbx app, synched twice from same app.

Scenery config editor shows no error.

Redid the flight, same issue.

[Reader 2,035]

Sometimes, the assumption that the default simulator is perfect is flawed.

Here is the precise location in an entirely default FSX:

 

There is no need to waste any more time in trying to determine the cause and a couple of excludes would remove those default mesh spikes.

[Luis Hernandez 594]

Nothing a freeware mesh can't solve

[kttd 12]

Thank you airplane addicts, thanks for chiming in.  Must not be an OLC issue.  I'll search for some freeware mesh.  Happy flying.  

[kttd 12]

Hello friends, thanks for the replies and illustrations.

I installed some freeware mesh, directly below all of my Orbx software, which is first in line at the top.  It did not solve the pyramid issue.  Perhaps that's the incorrect location in the scheme of things.

I have most of the Orbx software, but not all.

[Reader 2,035]

As explained, this has absolutely nothing to do with Orbx software.

[kttd 12]

My comment has nothing to do with Orbx with the exception of where I placed the mesh with regards to before or after Orbx software. 

I posted the comment in case my placement of the mesh in the scheme of things was incorrect.

[Reader 2,035]

On 5/2/2024 at 6:52 PM, kttd said:

I installed some freeware mesh, directly below all of my Orbx software, which is first in line at the top.  It did not solve the pyramid issue.  Perhaps that's the incorrect location in the scheme of things.

More likely is that the freeware mesh has the same anomaly.
The solution remains: excludes for the two mesh spikes.

Edited May 13 by Reader

[kttd 12]

I'm sure you're correct.  Thanks to everyone for commenting.