I was planning a flight from Central Colorado Regional Airport this afternoon and when I looked it up on P3D it had two identifiers, KEAJ and 7V1.  When I Google each one they both come up with the same thing.  I'm puzzled.  I've never run into this before.

Noel

2 hours ago, birdguy said:

I was planning a flight from Central Colorado Regional Airport this afternoon and when I looked it up on P3D it had two identifiers, KEAJ and 7V1.  When I Google each one they both come up with the same thing.  I'm puzzled.  I've never run into this before.

Noel

I should be able to help you and answer your question. First of all I think you mean KAEJ, not KEAJ. Need two questions answered first. First question, Which version of P3D are you using?  second question, do you have the Free ORBX global airport package installed?

Edited March 15, 20224 yr by johncott

I'm using P3Dv5.3 and yes, I am using the free Orbx global airport package.

Noel

 KEAJ is an ICAO designator and the other is an FAA one. There are thousands of them in the US that have different identifers like this 

2 minutes ago, birdguy said:

I'm using P3Dv5.3 and yes, I am using the free Orbx global airport package.

Noel

Here is the issue, in P3DV5, Central Colorado Regl. airport has the ICAO code KAEJ.  The free ORBX global airport package has both KAEJ and 7V1 airports both at the same location with the same name Central Colorado Regl.  You simply have to rename "ADE_FTX_FTXG_7V1.BGL" in the FTX_FTXG_AIRPORTS/scenery" folder.  I would recommend that you change the extension to something else like "inactive" for example.  If you reinstall or verify the free ORBX global airport package, you may have to rename the "ADE_FTX_FTXG_7V1.BGL" again.  Why are there two airports with different ICAO code? in FSX for example, the Central Colorado Regl. Airport has ICAO code of 7V1 and not KAEJ.  I went from FSX to P3dV5 so I'm not sure what code this airport had in previous versions of P3D, but it was changed somewhere along the way.  With the ORBX Airport Package installed, either way you going to end up with two ICAO codes no matter which sim you're using and will have to rename some files. With FSX you will have to change the files with KAEJ in them.

John C.

 

Thanks John that explains it.  I'll just leave them both there.  I don't think it hurts anything.

Noel

12 hours ago, birdguy said:

Thanks John that explains it.  I'll just leave them both there.  I don't think it hurts anything.

Noel

Noel,

I do not think it will hurt anything. LM upgraded a lot of airports in P3DV5 and the ORBX airport package was designed for FSX and previous versions of P3D where the airports didn't change much if any.  For this reason you will probably find some airports with two ICAO id's, sunken or elevated runways, two set of taxi signs and maybe some other objects that appear out of place.

John C.

If I run into any elevated or sunken runways I'll check for two identifiers and delete one.

Noel

Unfortunately, just renaming the Orbx bgl file will not change the name of the airfield in the P3D database or in the bgl.  To delete a stock airport and its identifier, you have to build an exclusion under the replacement airport.

The changes in elevation on some (but not all) airfields in P3Dv5 are due to rebuilding the worldwide default terrain mesh using a newer, more accurate DEM elevation map than the ~2005 SRTM data used for the FSX builds and then subsequently in P3Dv1-4.  An airport file that places a flatten at a different elevation than the underlying base mesh will result in a plateau or sunken airport.  To fix it, the flatten has to be redone to reflect the elevation in the updated terrain mesh.

The doubled taxi signs and disappearance of some buildings in v5 is due to rebuilding the airport bgls in v5, which changed the object IDs and/or positions of objects from where they were in the scenery bgls in FSX and P3D v1-4.  The micro-exclusions that were coded into add-on airport files to remove stock objects are based on position, and don't work when the objects have been moved as part of the airport scenery rebuild.  Additionally, some of them also place objects using P3D stock GUIDs that don't work any more because the they've changed or the object was deleted/replaced in the new object libraries.

Yet another quirk is the more widespread use of autogen buildings in the stock scenery, which can't be excluded in an airport file, but have to be excluded in a layer below the airport scenery.  That often explains the reappearance of stock buildings that were successfully excluded by the same ADE file in P3Dv4.