TBM shows TCAS traffic no problems with FSLTL.
Are you in contact with Asobo?
Hi there, a question to other FSTL users…
Can FSTL (or FSTL-injected traffic) cause a huge memory over-run in MSFS?
I has happened to me twice, and always in two-leg flights (turnaround returning to first airport, without going via main menu / world map).
First time was LEBL-LEIB-LEBL
Second time today LTFJ - LTAF - LTFJ
When landing, MSFS becomes a slide-show, and task manager shows that MSFS is eating 22 Gb of RAM:
Since memory is full, I assume Windows starts pagination, hence the slide - show.
Also, both times, I saw FSTL planes “frozen” in the middle of the runway (in one case, several of them stacked together)
Closing FSTL improves a bit the situation (RAM usage decreases, FPS goes from 2 to 6) but MSFS does not recover fully.
I have done now twenty flights with FSTL, the longest one being more than three hours, and the only times I have seen the issue is when the flights were multi-leg (two out of two times). The other 18 flights (single-leg) were perfect.
System and Soft:
i7 11700, RTX 3060Ti, 32 Gb RAM
VR, HP G2
DLSS quality, TLOD 100, no OXR toolkit
Fenix A320
FSTL with FS Traffic models
Other add-ons: GSX, Flight Control Replay, Navigraph in game panel…
Not a deal breaker (I love FSTL) but certainly annoying since (in my case) it seems unable to work with multi-leg flights.
Any insight will be appreciated.
This issue is documented in the FSLTL FAQ and covered on this forum as a known MSFS bug with returning to the same airport you started from.
Starting with reading the FAQ is the best way to get answers: Support FAQ – FSLTL – FS Live Traffic Liveries
Thxs, hope it gets fixed in SU12…
Is it possible to leave FSLTL running after closing the sim, and perhaps add an auto-reset so it doesn’t lock up if the sim crashes?
It seems like MSFS is as much a benchmarking tool as it is a simulator with all the tweaking I do. Any time I close it to restart after some changes, I have to manually re-launch FSLTL because it closed itself. If the sim crashes, FSLTL pops a notice of the crash, but I have to manually close it and again manually re-launch it when I re-launch the sim.
Anything on livery-matching and model-matching for Live Traffic?
(In SU11 it’s all messed up)
There are two possible APIs for accessing the TCAS data for AI Traffic (simconnect):
~ Coherent (Javascript) or
~ WASM (compiled languages, mainly C++ or Rust).
In SU11, the aircraft that can see TCAS for AI offline Traffic are using WASM.
The aircraft that currently cannot see the TCAS for AI offline Traffic are using Coherent.
For example, the FlyByWire A32NX suffers in this regard because it has implemented TCAS using the Coherent JavaScript API, so it currently does not “see” the en-route FSLTL & AIG (or any “AI”) traffic at cruising altitude.
I hope SU12 fixes this problem with the Coherent-based API.
It is logged with Asobo – Here’s the developer bug track report:
https://devsupport.flightsimulator.com/questions/12949/ai-aircraft-generated-airborne-do-not-get-returned.html
Please make sure you vote for that topic and also add your comment/issue. We need as much noise as possible so Asobo fixes this issue. It’s been there since SU10.
Today I watched a plane approaching at the airport and before landing it disappeared. I can read at the injector page " Removed by MSFS traffic engine". Why does this happen and can I avoid this? All MSFS traffic is turned off.
This usually happens when there is no suitable gate available at the airport.
Seems to be some type of corrupted livery/model for an airline somewhere in China coming in from the north. My past two flights entering China has resulted in CTD’s. Doing the third flight now without FSLTL’s base and have passed the previous points of CTD’s.
Come to the discord and raise a support ticket with your log file and then you can get support. We have batch testing processes to inject all liveries / models before we do a release, so its probably some other aspect of the data being used.
Thanks mate, I’ve optimized my sim with your settings
It does work, and I think SU12 helps out too. Still see slight issues at non/less optimised airports, and not all airports offer performance tweaks. Some should still carry warnings!
When using the API key, does this affect FPS more then leaving it off? I don’t care so much about realistic flight plan.
There’s no FPS impact from using the API key.
Thanks. I assume using it will require it to be connected to a server hosting it and constantly feeding data. I have enough stuff going on the background already LOL.
The link is through the FSLTL injector itself, there’s no additional software running - it’s a set-and-forget feature.
Its funny you say that as I have observed a small FPS impact when a particular API key in input.
Could very well be psychological but could also be the software trying to get constant information from the internet through that link.
Cheers,
Nish
