Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

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.

cscurlock

Member
  • Joined

  • Last visited

Everything posted by cscurlock

  1. Ignore this it looks like its fixed now. Must have been something MS corrected.
  2. After last MSFS update when planes land they do not stop and call the atc after exiting the runway and also do not stop and call the atc to cross the runways. Its like the triggers that tell the aircraft that its exiting the runway or about to cross the next runway are removed. I am using FSHud where this was working for a long time correctly until today when I ran a MSFS update.
  3. I am using FSHUD and FLSTL and for the most part the scenery behaves correctly when using AI traffic. But there are a few issues I am seeing. 1) When AI traffic enter the 22R runway they enter at taxiway G and backtrack to the runway lettering and uturn to take off. I am not sure why they would be entering here unless it was small GA plane. Regular commercial aircraft take off by C or YA maybe. 2) it seems that when crossing runway 22R and taking off 31R the trigger to let the MSFS know the planes is off 22R is not working. The strobe lights are still on and it locks the runway so other aircraft cant cross until it takes off on 31R. 3) When taking off from 4L its not recognizing when the plane crosses and leaves 31L. It thinks the plane is still on 31L until it takes off from 4L. Many planes are waiting at K to cross 31L until the previous plane takes off. This causes issues with the flow of traffic. This is the same trigger issue and #2. Love the scenery and I know this is specific to this scenery as KLAX doesn't have this issue.

Account

Navigation

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.