active KGPI runways and taxiways floating

[ironcondor]

Installed KGPI today and noticed the runways and taxiways floating. I did the normal Vector scan and made sure the eleviation's were correct. Also, purchased Northern Rockies. Double checked all FTX Central settings.

 

Thoughts?

 

 

 

 

[ironcondor]

Follow up:

 

1.) Removed FTX Global Base, Open LC NA, RMN, KGPI.

2.) Reinstalled

3.) FTX Vector Elevation scan

4.) Dried both AFCAD per the KGPI control panel.

 

Here is another image.

 

 

[BoyScout]

Same issues as well.  I just installed today and I am not even able to get it to work in slew mode.  Thanks

 

Rob

[Doug Sawatzky]

Hi

 

Please first apply and confirm the below process.

 

Ensure all of your 3rd party non Orbx addons are at the top of your scenery library and above your FTX entries.

Then in FTX Central 3 Insertion points, move "FTX entries should be inserted below"  just below your last 3rd party addon.

Then move the "openLC entries should be inserted below"  just below your FTX entries. and click "Save".

 

 

 

[BoyScout]

ALCON,

 

  Please see the attached on Turbulent Designs website/forum:

 

https://www.turbulentdesigns.co.uk/forum/topic/733-kgpi-terrain-issues/

 

  Has this update been applied to the installers as this is my issue?  Thanks

 

Rob

[Sabretooth78]

I was experiencing possibly the same problem, which as in the TD thread linked above turned out to be a mismatched elevation conflict with fsAeroData.  My solution was to load up the fsAeroData ../Navigation Data/P3D/PROC/scenery/KGPI.bgl into ADE, revise the elevation and compile.  I put the resulting file in a scenery level just below ORBX (it also creates a _ALT.bgl file in ../scenery/world/scenery) and that seems to solve that problem.

 

Another potential solution is here:

https://www.fsaerodata.com/forum/viewtopic.php?f=4&t=305

 

That said, I seem to have a Z-fighting issue that occurs regardless whether fsAeroData is installed/activated or not.  This may not be relevant to the original topic of the thread but the TD thread linked above mentions a z-fighting fix in the patch; thus my curiosity as well as to if it is included in the FTX Central download.  I didn't test this extensively but I was able to get the z-fight to occur reliably at the RWY 2 start position (and for some distance down the runway), especially from low altitude - both outside and inside the aircraft.

 

 

[boogie]

I am having the same issue although I use the free version of Navaids for P3D. From what I read at Turbulent's forum there was a patch for it.
Is this patch applied to the ORBX version too or what do I have to do to get rid of it?

 

Regards, Klaus

[Doug Sawatzky]

Hi

 

I don't have any nav or traffic addons and my airport displays correctly, does maybe the below setting in the KGPI control panel have any bearing?

 

 

[boogie]

14 hours ago, Doug Sawatzky said:

Hi

 

I don't have any nav or traffic addons and my airport displays correctly, does maybe the below setting in the KGPI control panel have any bearing?

 

 

 

I tried it with this setting and it looked like this:

 

 

 

 

I changed back to KGPI with my GA Settings:

 

 

 

 

When I used my lower settings for Jets it seemed OK for me

 

 

 

The difference came up after using my low Jets settings when I increased the texture and mesh resolution.

 

[Nick Cooper]

Hello,

which version(s) of P3D do you have and are all the three parts the same version?

[boogie]

Hi Nick,

 

I use P3D 4.4 (only client updated).

Please have a look at my previous post again, I edited it to explain the differences.

[boogie]

I made 2 new screens, the first with the recommended settings (5m Mesh resolution), the second with 2m Mesh resolution.

This seems to be the reason!?

 

 

 

 

What I just noticed apart from other things, the jetways look quite strange!?

 

Edit: After a fresh P3D start the jetways went back to normal, only the effect of mesh set to 2 or 1m stays.