What fixes Elevation in P3dv5?

[spilok 1,132]

When I used Central version 3 in ORBX with P3dv4+, there used to be a tab that could correct elevation problems of all kinds.  You just had to put in the airport code and disable it if there were a problem. 

Is there anyway to address specific airport elevation of weird problems at airports in P3dv5?

Stan

[jabloomf1230 2,445]

That was part of FTX Vector.

[Ed_S_Pilot 227]

They do need a FTX Vector for V5. I fly RW out of KCRQ and the ground elevations are way off compared to what i see on final.

Edited May 16, 2020 by Ed_S_Pilot

[BMW969 126]

I always searched for the airport manually in the folder ORBX and turned it off

[Dave_YVR 968]

AEC only corrected elevations that vector introduced. Most issues come from bad default data or high res mesh. 

[gaab 111]

Since Prepar3D V4.5 HF2 the elevation of an airport is defined by the LAST redefinition (upper in library). There is no more such a thing as Alt stub.

One of the reasons of vector not being ported to V5.

So the elevation must be fixed by your airport supplier.

Gérard

 

[jabloomf1230 2,445]

1 hour ago, gaab said:

There is no more such a thing as Alt stub.

Actually not quite true. An ALT stub BGL is no longer needed to change an airport's elevation. Unless LM fixed this in P3d5, an ALT sub BGL is still needed to change an airport's name. 

[gaab 111]

6 hours ago, jabloomf1230 said:

Actually not quite true. An ALT stub BGL is no longer needed to change an airport's elevation. Unless LM fixed this in P3d5, an ALT sub BGL is still needed to change an airport's name. 

You are right, but that was not the topic.

There is a need to let people know this change (probably needed for the sloped runways).

It is not as frequent to need to change the ICAO name 😉

LM has not listed it in any change log as long as I know. And the impact is not unsignificant...

That is the reason why I try to insist on this point frequently.

Regards

Gérard

Edited May 17, 2020 by gaab

[Balint Szarka 123]

14 hours ago, gaab said:

You are right, but that was not the topic.

There is a need to let people know this change (probably needed for the sloped runways).

It is not as frequent to need to change the ICAO name 😉

LM has not listed it in any change log as long as I know. And the impact is not unsignificant...

That is the reason why I try to insist on this point frequently.

Regards

Gérard

This is actually something very interesting to know to be honest. Could you please fill me in on the details on this? Does that mean that I wouldn’t need to include the xyz_ALT.bgl’s in an add-on.xml that come with some sceneries?

The main reason of my interest in this topic is because all these altitude stubs create a whole mess in an add-on.xml file which is a lot of work when I am trying to keep all the scenery files out of my P3D folder by manually adding the ALT files to the scenery’s already existing add-on.xml and moving them the scenery’s location. Especially with Drzewiecki Designs airports which still love to install all the files within the P3D main folder - which I don’t like, creating a mess (a bit of OCD).

Kind regards,

Balint

Edited May 17, 2020 by Balint Szarka

[jabloomf1230 2,445]

58 minutes ago, Balint Szarka said:

This is actually something very interesting to know to be honest. Could you please fill me in on the details on this? Does that mean that I wouldn’t need to include the xyz_ALT.bgl’s in an add-on.xml that come with some sceneries?

LM changed the way a revised airport's altitude was prioritized beginning with P3d 4.5 HF2. Prior to that revision, a stub BGL file usually identified with ALT in its filename was placed in .../scenery/world/scenery in order to change an airport's altitude, since that folder loads first in P3d. See this explanation by Jon Masterson (AKA ScruffyDuck), the author of Airport Design Editor:

https://scruffyduck.screenstepslive.com/s/help_docs/m/20268/l/199754-how-do-i-change-the-altitude-of-an-airport

This approach was cumbersome, so LM changed it such that the version of the airport that is the highest priority in the scenery library determines the airport altitude. This renders those ALT BGL files useless, except possibly for changing the name of the airport.

 

[gaab 111]

Deleted

Edited May 18, 2020 by gaab
deleted

[OzWhitey 3,353]

7 hours ago, jabloomf1230 said:

LM changed the way a revised airport's altitude was prioritized beginning with P3d 4.5 HF2. Prior to that revision, a stub BGL file usually identified with ALT in its filename was placed in .../scenery/world/scenery in order to change an airport's altitude, since that folder loads first in P3d. See this explanation by Jon Masterson (AKA ScruffyDuck), the author of Airport Design Editor:

https://scruffyduck.screenstepslive.com/s/help_docs/m/20268/l/199754-how-do-i-change-the-altitude-of-an-airport

This approach was cumbersome, so LM changed it such that the version of the airport that is the highest priority in the scenery library determines the airport altitude. This renders those ALT BGL files useless, except possibly for changing the name of the airport.

 

Interesting. My Orbx Trueearth UK South still has a stub folder, but the other parts of the UK do not. Anyone know whether these are still required? 
Sounds like it would only make sense if the airport scenery had the wrong altitude encoded.

[gaab 111]

16 hours ago, Balint Szarka said:

Does that mean that I wouldn’t need to include the xyz_ALT.bgl’s in an add-on.xml that come with some sceneries?

Exactly. I have started to update all my add-on.xml except Orbx,  because
- they frequently mix alt.bgl with traffic.bgl
- they update very frequently their sceneries to (try to) address V5 evolution...

But will happen one day 🙂

Gérard

I am convinced that sloped runway is the real driver for this long waited evolution.

[Balint Szarka 123]

@jabloomf1230 and @gaab thank you both very much for clarification!

It’s time then for all the ALT files to go from my add-on.xml’s. They only add complexity to the already complex scenery priorities... Again OCD 😆