39 minutes ago, Sethos1988 said:

....it sound like the upcoming OrbX Central might actually solve the problem. We'll see.

That's a good point. Hopefully it will...😁

2 hours ago, guibru said:

You do not need to manually disable files in the Vector Scenery Folders. If you have compatibility issues with ORBX or other products, you should use the Flightbeam manager Troubleshooting tab. Disabled with the sliders. 

 

I just restored the files and ran it, not a single one of them shows up in there.

 

Here's a post from Nick over on the OrbX forums;

Quote

The reason that Vector AEC has no effect here is twofold.

 

1. there are no Vector AEC files, therefore Vector AEC is not the cause.

2. the anomaly is not at the airport and indeed is not directly to do with the airport elevation.

 

It looks like the Flightbeam utility searches the Vector folders for the ICAO code for the airport in question
but in this case, that is not the solution, due to the relevant files in this case having no ICAO code in
their file names.

The anomaly is caused by Vector amending the water levels and contours around the airport and that
is neither the fault of the addon, nor of Vector.
Clearly the Flightbeam airport has been modeled to fit the default water level, this is perfectly acceptable.

The files that I told you to disable remove the influence of Vector on the water in the immediate vicinity
of the airport and of course, this makes the Flightbeam product fit again.
I simply found out from Tmf Viewer where the Vector files were and relayed the information to you.

 

Edited May 24, 20197 yr by Sethos1988

Hi Sethos1988,

Sorry for the late response.
The problem does not come from the Flightbeam scene since it fits perfectly on ORBX Global.
This is a problem with ORBX Vector. Disabling the Vector_EXX scene library entry removes the terrain problem.
The file that caused the field problem is 2316_EXX_Excludes.bgl under Vector FTX, FTX_VECTOR_EXX. The conversion of this file to . off corrects the altitude inconsistency. Unfortunately, this also creates other anomalies in the surrounding area, such as shoreline problems.

KMSP is one of the many ORBX Vector problems in the world.
For example in Asia a lot of problem of elevation with third-party publishers.

KMSP has another problem that hasn’t been solved yet, a bridge duplication with ORBX Vector.
I hope ORBX will update Vector.

 

25 minutes ago, guibru said:

I hope ORBX will update Vector.

I assume you have advised Orbx of this in their forum.  I have found it helpful to report all things abnormal to them and they get them fixed.

3 hours ago, guibru said:

The problem does not come from the Flightbeam scene since it fits perfectly on ORBX Global.
This is a problem with ORBX Vector. Disabling the Vector_EXX scene library entry removes the terrain problem.
The file that caused the field problem is 2316_EXX_Excludes.bgl under Vector FTX, FTX_VECTOR_EXX. The conversion of this file to . off corrects the altitude inconsistency. Unfortunately, this also creates other anomalies in the surrounding area, such as shoreline problems.

 

Orbx do not profess to be expert in Flightbeam products, it seems that the opposite is not the case.

Quote

 

The anomaly is caused by Vector amending the water levels and contours around the airport and that
is neither the fault of the addon, nor of Vector.
Clearly the Flightbeam airport has been modeled to fit the default water level, this is perfectly acceptable.

The files that I told you to disable remove the influence of Vector on the water in the immediate vicinity
of the airport and of course, this makes the Flightbeam product fit again.

These are the files.

2315_WTR_Waterbodies.bgl

2315_EXX_Excludes.bgl

2316_WTR_Waterbodies.bgl

2316_EXX_Excludes.bgl