Hello friends:

 

I have encountered a strange scenery display problem today and I would like to ask for your advice on now to fix this...

As you can see there seems to be a mistake in the elevation of the green parts so that the reunways and taxiways only appear intermettantly...

 

Any ideas what could be the cause for this phenomenon and how to get the airport back to "normal"?

 

Thank you very much!

Scorpio47

 

 

BTW I checked the altitudes of the tarmac and runways and it is at 404 ft, however the elevated green areas are at 437 ft.

Perhaps this will helpt to better identify the culprit.....

Looks like conflicting AFCAD files to me.

Do you use any kind of addons for this area, e.g. ORBX PNW and/or a freeware AFCAD for SEA, and if so, do you use both? In that case, I guess that all PNW entries in the scenery library should have higher priority than the file that contains the AFCAD.

If you also use an AI traffic addon, it should have a very low priority in the scenery library to avoid conflicts.

FTX Global Vector caused that kind of weirdness for me. I had to use it's configure tool to disable it around KSEA.

 

Gre

I had the same problem with  Ray Smths afcad update for 3rd runway at KSEA , i changed it for this" Seattle-Tacoma KSEA Upgrade" file from Simivation which is only 1 BGL file  and the deep trenches problem vanished.

 

I too have ftx global vector and did not  use the configuration tool to solve it , but useful to know that works !

 

 

I too have ftx global vector and did not use the configuration tool to solve it , but useful to know that works !

 

Had to use it around KBUR as well (hot mess).  There will probably be others.

Thank you for your ideas, but I think this is not the problem here, as I do not have any AFCAD files installed (at least not that I know of) and no AI traffic.

Also, I do not have FTX vector installed here.

 

Here is another pic form closer up to illustrate the phenomenon:

Had to use it around KBUR as well (hot mess).  There will probably be others.

 And there is. I have the exact same problem with Boise airport (KBOI) and I don't remember changing or adding and new AFCAD file. Scorpio47 let us know if you find a resolution?...I will too. Thanks

 

Troy

I have to apologize but my memory failed me....

 

I do not have FTX Global Vector installed here, BUT:

 

after a HD failire and complete loss of data I reinstalled FSX a few weeks ago and to save time I then copied over the files from my backup. That backup contained a series of older files from an  earlier installation of FTX and so I found this file ADE_FTX_PNW_KSEA_elevation_adjustment.BGL in my scenery directory.

 

After I renamed it, the problem is GONE!!

 

So, you were right nevertheless, this was the consequence of conflicting scenery files for Seattle and there might be other areas which I have not yet discovered.

 

Thank you for your help and ideas, you made my day!

 

Cheers

Scorpio47

I to have FTX PNW and I did renamed the ADE_FTX_PNW_KBOI_elevation_adjustment.BGL files but that did not resolved. However, there are multiple files with this same name in which case I made an attempt to rename all of them to no avail. What resolved it for me was reinstalling FTX PNW. Everything is a OK now. Thanks

 

Troy

That is for STOL practice. 

 

Bob

Those ORBX elevation files get out of sync occasionally.  

That is for STOL practice. 

:rolleyes: :rolleyes: :rolleyes:

Those ORBX elevation files get out of sync occasionally.  

 

Why they are messing around with big airports is beyond me! Tinker with the little, out of the way airports all they want, but when they are messing with Seattle or Boise or other large fields it makes me wonder WHY? Those elevations are correct (*) and they need to adjust their terrain to match.

 

 

*the elevation shown would be the highest point of the traveled airport