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.

FSLTL + Navigraph (MSFS 2024) - AI Go-Arounds & Wrong Runway

Featured Replies

Platform: MSFS 2024
Add-ons: FSLTL Traffic Injector, Navigraph Unlimited

Issue:
I’m currently using FSLTL Injection for my AI traffic within MSFS 2024. I also have an active Navigraph Unlimited subscription (which updates my simulator's navdata).

I am experiencing an issue where a significant number of AI aircraft are performing go-arounds or landing on the wrong runways (often preferring inactive or shorter runways over the active ILS runway). This seems to happen primarily when Navigraph is updating the simulator’s internal database.

What I’ve Tried:
I have attached my fsltl-traffic-injector-config.json settings for reference.

I am unsure if this is a conflict between the FSLTL injection logic and the updated Navigraph runway data, or if there is a specific setting within FSLTL that I need to adjust to tell the AI to prioritize the Navigraph data correctly.

Questions:

  1. Are there specific settings in the FSLTL config that relate to "Runway Selection" or "Approach Logic" that I should be tweaking?

  2. Does FSLTL rely on the default MSFS scenery data or the Navigraph data for runway selection? If it relies on the default, could the Navigraph update be causing a mismatch?

  3. Is there a specific load order or cache clear I should perform to ensure FSLTL reads the updated runway data properly?

Any advice would be greatly appreciated. Let me know if you need any more details from my end.

Thanks in advance.

fsltl-traffic-injector-config.json:

{

"livefeed": "navigraph",

"realtraffictoken": "",

"ifraircraftlimit": 80,

"vfraircraftlimit": 0,

"spawnradiusair": 150,

"spawnradiusground": 50,

"sids": "Yes",

"stars": "Yes",

"separation": "Yes",

"forceappalt": "",

"secstilremove": 120,

"flightplannerdbapikey": "",

"userflight": "",

"staticaircraftlimit": 0.1,

"staticaircraftlimitmax": 30,

"staticaircraftgalimit": 0.1,

"staticaircraftgalimitmax": 15,

"nofallback": "Yes",

"nogenerics": "Yes",

"fstraffic": "",

"modeloveride": "",

"consoledebug": "",

"defaultsim": "2024",

"silent": "Yes",

"allreg": ""

}

FSLTL injected aircraft uses the default msfs AI systems.

Any issues with runway assignment are with the sim, not FSLTL.

Edited by Tuskin38

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.