Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

KSEA plateau + Realair Duke graphical glitches

Featured Replies

Do I win the award for most messed up screenshot with this one? Any help appreciated, have just installed the Duke Turbine and this is what I get sitting on the active runway @ KSEA. Obviously 2 different problems here. I have UTX, GEX, FTX PNW, and FS Genesis installed as the relevant add-ons in this screenshot. Also running DX10 with no problems elsewhere.

 

kseadukeproblems.jpg

Highmemfix? Does this happen in DX9?

 

For KSEA I hadn't touched my install in a long time and I had a major elevation issue at SEA with PNW scenery. I asked in their forums about it can't remember what I did to fix it.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

  • Author

Highmemfix should be there, I'll double check thanks. I don't know about dx9 but I'm fairly certain dx10 isn't causing the elevation problem, though it could be causing the other. The weird gauges outside the cockpit thing only shows up if I move the camera outside the cockpit from the VC, not something I plan on doing ever so it's an avoidable issue.

Your screen grab doesn't show elevation, but it would be one of two things at KSEA. First, some one changed the elevation, which for such an airport can create additional problems if done hap-hazardously or two, something has taken out the airport flatten allowing the mesh to swallow you whole.

 

From what I recall, nothing in UTX alters KSEA and mesh, in and of itself will not affect an airport flatten. Think that narrows it down for you?

  • Author

I'll try disabling PNW.

 

edit: it's not PNW. if it's not PNW or UTX then that pretty much leaves FS Genesis/lack of a flatten switch. So, any thoughts how to flatten? I'd hate to have to uninstall FS Genesis to fix this problem.

  • Author

so I found Airport Design Editor and after some fooling around have managed to bring the airport's concrete surfaces to the correct elevation, but now the grassy areas in between are sitting in valleys.

so I found Airport Design Editor and after some fooling around have managed to bring the airport's concrete surfaces to the correct elevation, but now the grassy areas in between are sitting in valleys.

 

Default KSEA is at 433'. If you could get back to the same state as the first picture and try the Cessna 172 your elevation would read 439.4', or at least it should.

 

Mesh has no ability to change an airport area. It works the other way around generally, adjust the airport to the mesh. Speaking in general terms, if someone is changing an airport's elevation they are going to want to do that where the file is read early in the loading process. The generalized manner is to place what's called a "stub" file into the \Scenery\World\scenery folder. My educated guess is that you will find some file in that folder pertaining to KSEA. Despite "turning off" a scenery package, that possibly does not affect any of the files placed into the \Scenery\World\scenery folder? That's why I like to keep my elevation change files in a separate folder that is easy to make inactive in the Scenery Library.

  • Author

Default KSEA is at 433'. If you could get back to the same state as the first picture and try the Cessna 172 your elevation would read 439.4', or at least it should.

 

Mesh has no ability to change an airport area. It works the other way around generally, adjust the airport to the mesh. Speaking in general terms, if someone is changing an airport's elevation they are going to want to do that where the file is read early in the loading process. The generalized manner is to place what's called a "stub" file into the \Scenery\World\scenery folder. My educated guess is that you will find some file in that folder pertaining to KSEA. Despite "turning off" a scenery package, that possibly does not affect any of the files placed into the \Scenery\World\scenery folder? That's why I like to keep my elevation change files in a separate folder that is easy to make inactive in the Scenery Library.

 

There is a bgl file in the scenery/world/scenery folder pertaining to PNW KSEA with "elevation adjustment" in the name. I'll try renaming to .bak and see if that helps. Thanks for the tip.

 

edit: I've renamed the file and it looks about the same. However, I am running a modified bgl for the main PNW KSEA so I will switch back to the original and see if that fixes it.

 

edit 2: moving back to the original PNW KSEA bgl has made no change in the way the scenery looks for me now. However, what I have now is a vast improvement over what my screenshot shows since at least the concrete surfaces are all at the same level with no strange cliffs jutting up out of them, so if I can't find an answer to this then at least the airport is usable, I just have to be careful not to taxi off the concrete :lol:

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.