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.

Gate to Nowhere a KSEA

Featured Replies

Does anyone know what causes this problem? As you can see, a gate showed up at the holdpoint on KSEA runway 34R. I'm using the default airport. The only thing I recall doing is installing FSDT scenery updates and installing a SP1 to F1 S80.I remember reading, some time back, how scenery at one location can cause this problem at KSEA. I thought it had something to do with KORD? I've searched this forum, the FSDT forum, and the Flytampa forum and can't find the topic on this. Does anyone remember where it is or better yet, what file I need to remove to fix it?http://imageshack.us...etonowhere.jpg/Thanks,Mike

Mike Franks

The KORD problem was due to a KMDW exclude. Are you running AES?And for the record I was tempted, but did not, "scratch the girl".....

Al Stiff

  • Author

No, I'm not using AES. Maybe it wasn't the scenery from KORD interfering with KSEA. However, I do remember reading about another scenery interfering with KSEA. Unfortunately, I don't recall what the scenery was or the fix.Thanks for the reply,Mike

Mike Franks

  • Author

***FIXED*** My problem had to do with the updated FSDT Zurich 2.5 scenery. If I activate it, then the gate shows up. When I don't activate the scenery, the gate goes away. I guess I won't be doing any flights from KSEA to LSZH :)I'll bring this up at the FSDT Forum.Thanks,Mike

Mike Franks

That is a strange one for sure....

Al Stiff

  • Author

Thank you Umberto! That fixed the problem. I appreciate the quick response on Christmas day.Mike

Mike Franks

I remember reading, some time back, how scenery at one location can cause this problem at KSEA. I thought it had something to do with KORD? I've searched this forum, the FSDT forum, and the Flytampa forum and can't find the topic on this. Does anyone remember where it is or better yet, what file I need to remove to fix it?
Just for the record, the earlier issues you quote relates to several add-on sceneries sloppily-built with EZ Scenery software. It is unfortunate that EZ Scenery defaults to the reference point at KSEA and a click of a button before selecting co-ordinates in that software is enough to install a scenery object there and not at the location of the scenery concerned. It is possible to have quite a pile of odd buildings and objects right in the middle of the runway and those can all be eliminated by creating an exclude file around them.As I say, that is purely for the record but it seems unlikely this was the issue here as the object was not at that location . . . and that it has been easily resolved by the designers of that scenery themselves.John

My co-pilot's name is Sid and he's a star!

http://www.adventure-unlimited.org

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.