Sethos

Vector related elevation issue at Flightbeam's KMSP

Recommended Posts

Hey,

Noticed this odd elevation issue behind runway 30L on KMSP, which can be solved by disabling Vector. However, KMSP does not show up in the AEC tool (which I've run, of course). Here you'd normally manually disable some specific files but the only file I've found, ABP_KMSP.bgl, does nothing.

Would anybody happened to have run into the same issue and found a fix for it?

mvj03lx.jpg

 

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Posted (edited)

Too me it simply looks like the terrain mesh resolution is not fine enough to render what a river, levee, flood plain combination would look like.  I don't think this is a problem but that is just my opinion.

Edited by downscc

Share this post


Link to post
3 minutes ago, downscc said:

Too me it simply looks like the terrain mesh resolution is not fine enough to render what a river, levee, flood plain combination would look like.  I don't think this is a problem but that is just my opinion.

It works / looks correct when Vector is disabled. So I was hoping I could manually disable the specific elevation / terrain files of Vector that affect this specific airport, like you sometimes have to with various airports when clashing with OrbX regions / Vector.

Share this post


Link to post
3 hours ago, Sethos1988 said:

It works / looks correct when Vector is disabled. So I was hoping I could manually disable the specific elevation / terrain files of Vector that affect this specific airport, like you sometimes have to with various airports when clashing with OrbX regions / Vector.

Run the VECTOR tool.....I think I have about six APT that elevation needed to be "corrected", some better some not, but it works, with exception of KSEA in my case and I gave up landing there since FSX time. Thought P3D would be better but it is not in my case.

Share this post


Link to post

Do you have any mesh addon in your sim?

Share this post


Link to post

Have you tried reaching out on the Flightbeam forum?

Share this post


Link to post

Under trouble shooting in the FB manager, you might find some files that need to be disabled in order to display correctly.

  • Upvote 1

Share this post


Link to post

try disabling the file ABP_KMSP.bgl in the Vector Scenery folder

Share this post


Link to post
1 hour ago, cyyzrwy24 said:

Run the VECTOR tool.....I think I have about six APT that elevation needed to be "corrected", some better some not, but it works, with exception of KSEA in my case and I gave up landing there since FSX time. Thought P3D would be better but it is not in my case.

As mentioned, I already did. KMSP isn't under my AEC, most likely due to being installed via the add-on method instead of the old scenery.cfg method.

 

1 hour ago, Dave_YVR said:

Do you have any mesh addon in your sim?

No but I can comfortably confirm it's due to Vector, just need to find the Vector files to disable it.

1 hour ago, ryanbatcund said:

Have you tried reaching out on the Flightbeam forum?

No, figured this was a Vector issue, so OrbX's forum would be more relevant. Just asked here as well, in case someone had a quick-fix solution, which files to disable.

1 hour ago, newtie said:

Under trouble shooting in the FB manager, you might find some files that need to be disabled in order to display correctly.

Good suggestion. Couldn't see anything related to elevation / mesh / compatibility though.

14 minutes ago, pads103 said:

try disabling the file ABP_KMSP.bgl in the Vector Scenery folder

Yeah, first thing I tried, only relevant file that came up in the search. Didn't seem to do the trick, unfortunately. Some other Vector files are at work here.

Share this post


Link to post

Thanks to Mr. Nick Cooper over on the OrbX forums, I found what I was looking for.

The files in question are;

2315_WTR_Waterbodies.bgl

2315_EXX_Excludes.bgl

2316_WTR_Waterbodies.bgl

2316_EXX_Excludes.bgl

In case someone should ever have the same issue and stumble on this.

Thanks for all your replies.

  • Like 1
  • Upvote 3

Share this post


Link to post

Glad you got this sorted Sethos.

Nick and company at the ORBX board are usually very good at getting issues like resolved quickly, so that that would be the first stop for anyone encountering problems similar to this that can't be resolved with the Vector AEC tool.

  • Upvote 2

Share this post


Link to post

Isn't the Vector config tool supposed to solve these kind of conflicts? What was different in this case?

Share this post


Link to post
31 minutes ago, Shomron said:

Isn't the Vector config tool supposed to solve these kind of conflicts? What was different in this case?

Not every airport will show up in the Vector AEC, if the 4 letter ICAO code for the airport isn't listed in the Vector AEC enable/disable drop down boxes you can't add it manually. I Checked, and sure enough KMSP is not listed.

Share this post


Link to post
Posted (edited)
2 hours ago, SunDevil56 said:

Glad you got this sorted Sethos.

Nick and company at the ORBX board are usually very good at getting issues like resolved quickly, so that that would be the first stop for anyone encountering problems similar to this that can't be resolved with the Vector AEC tool.

Absolutely. Sometimes you just hope, with the place being this active, that someone has the magical solution up their sleeve and can provide it quickly 😛

1 hour ago, Shomron said:

Isn't the Vector config tool supposed to solve these kind of conflicts? What was different in this case?

As SunDevil said, some airports don't show up there and KMSP is one of them. However, that might be attributed to the fact that it's installed via the new add-on method, which I believe AEC can't read. There's some not-so-elegant solutions to get around that but it sound like the upcoming OrbX Central might actually solve the problem. We'll see.

Edited by Sethos1988
  • Upvote 1

Share this post


Link to post

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. 

 

Share this post


Link to post
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...😁

Share this post


Link to post
Posted (edited)
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.

vEDVEqo.jpg

 

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 by Sethos1988
  • Like 1

Share this post


Link to post

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.

 

Share this post


Link to post
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.

Share this post


Link to post
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

 

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now