On 9/24/2025 at 9:29 PM, Dave_YVR said:

It isn't an FSLTL problem. ALL AI traffic that have multi LODs are effected by the aggressive LODs that Asobo has changed in an effort to improve performance at the cost of image quality.

The discussion had nothing to do with LOD issues or image quality.  I was referring to FSLTL aircraft never landing at airports, and instead just doing low level go-arounds. 

Woops, my bad. I must have been also reading/replying to one of the threads about AI traffic missing landing gear at various distances..

 In this case as well though, it is an Asobo issue as the traffic on and around airports is controlled by the ai engine of the sim and not by FSLTL. 

1 hour ago, PlumCrazy said:

The discussion had nothing to do with LOD issues or image quality.  I was referring to FSLTL aircraft never landing at airports, and instead just doing low level go-arounds. 

I've never experienced that issue, presumably because I use FSHUD with FSLTL

4 hours ago, HiFlyer said:

I've never experienced that issue, presumably because I use FSHUD with FSLTL

The LOD issue isn't as prevalent with the FSLTL models as they are generally only 2 LODs and don't comply with the MSFS SDK.  The lack of lod's is also a small reason why they are generally slightly harder on performance than the AIG or JF alternatives.

17 hours ago, Dave_YVR said:

Woops, my bad. I must have been also reading/replying to one of the threads about AI traffic missing landing gear at various distances..

 In this case as well though, it is an Asobo issue as the traffic on and around airports is controlled by the ai engine of the sim and not by FSLTL. 

I understand AI traffic is controlled by the sim after injection.  But the issue of AI aircraft not landing does not effect traffic injected by the sim (stock MSFS2024 AI aircraft) - it only effects the FSLTL injected traffic.  So it would seem to me it is up to FSLTL to make their injected traffic work within the parameters of the sim engine.

Today I reinstalled FSLTL base models, and the FSLTL Traffic Injector, but when I start the injector it shows, in the CMD window, an error message with:

14:03:37   FSLTL Traffic Injector v1.7.0
14:03:37   Before contacting support --->
14:03:37   Read the user guide: https://www.fslivetrafficliveries.com/user-guide/
14:03:37   Read the FAQ: https://www.fslivetrafficliveries.com/support-faq/
14:03:37   Review the log file: C:\Users\simmer\AppData\Roaming\fsltl-trafic-injector\logs\fsltl-traffic.log
14:03:37   Running MSFS 2024
14:03:37   MSFS is Store version
14:03:37   Community location:  F\MSFS\Packages\community\
14:03:37   Broken folder link: F\MSFS\Packages\community\
14:03:37
14:03:37   No model/liveries found - Verify FSLTL Base Models is installed in your Community folder!
14:03:37
Press Enter to close this injector console:

Tried all, including the supposedly not necessary "massage" of the "layout.json" over MSFS Layout Generator, but the error persists and the FSLTL Traffic Injector isn't working 😞

I find it weird that both Paths show no ":" after the "F", otherwise when I start FBW it shows the liveries and injector correctly installed.

Any suggestions?

I'm on FS 2024 SU4 beta 1.6.16.0

Edited October 18, 2025Oct 18 by jcomm

1 hour ago, jcomm said:

Tried all, including the supposedly not necessary "massage" of the "layout.json" over MSFS Layout Generator, but the error persists and the FSLTL Traffic Injector isn't working 😞

I find it weird that both Paths show no ":" after the "F", otherwise when I start FBW it shows the liveries and injector correctly installed.

Any suggestions?

I'm on FS 2024 SU4 beta 1.6.16.0

In my case, the location of the community folder on the main drive is more like:

C:\Users\username\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community

Did you move your community folder?

3 hours ago, HiFlyer said:

In my case, the location of the community folder on the main drive is more like:

C:\Users\username\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community

Did you move your community folder?

yep, and it's correctly set in the FBW installer settings.

[SOLVED]: It was incorrectly set within "UserOpt.cfg" when a couple of days ago I made that last line pointing to the Community folder read "F\" instead of "F:\"....

I didn't yet install any external addons, and FS 2024 had been working flawlessly even with that typo, so today FSLTL models and traffic injector were the first, and while the FBW installer didn't complain because it doesn't depend on UserOpt.cfg, the traffic injector, or maybe it's calls through Simconnect, do check that path (?).

Well, anyway, all solved and traffic + 3d models working fine, this turn around with default FS 2024 ATC because I want to test it thoroughly before tryin 1.6.16.0 with FSHUD and BATC.

Edited October 18, 2025Oct 18 by jcomm