I refer my honourable friend to my previous answer. Edit the aircraft.cfg files yourself, because no-one else is capable of doing it.
1 Like
Thank you for this v1.3 base update, much appreciated.
Note: The manifest.json file still says v1.2.2 (just an FYI) which can be confusing when you check the version number you have in add on linker say. 
“Capable” “…serious about MSFS Air Traffic”
Just humorous the complaints some devs receive for actually doing something to improve the state of MSFS instead of complain in forums and not actually produce anything.
5 Likes
The FSLTL Discord mentions this was missed before release and will be fixed on next update.
1 Like
ok thanks, as long as they know about it. I’m not nearly nerdy enough to spend Saturday evening trawling discord though 
haha No worries. The Discord server is the best way for us to keep track of reported issues, requests, etc. A single forum like this, reports of issues get lost easily. Most features, changes and fixes have come from the community and we appreciate the friendly feedback.
1 Like
Any reviews of V3.0 out there? I don’t do Discord.
1 Like
V3.0? 10 characters
Think he might men 1.6.3
First fire up with the latest versions, the very first “other” aircraft was a King Air, a type I’ve not seen before, so at least the new GA element works!
1 Like
Tried it out today at LSZH and was amazed by how lively the airport now feels. It’s also cool to listen to real world ATC and then see a plane with matching livery landing.
What I noticed was that planes were not landing on the runway that is used in RL. But I guess this is information is just not available and needs to be approximated by some sort of educated guess.
Anyhow, great work! Will use it much more frequently now.
P.S. appreciate the new aircraft models and liberty for vatsim model matching
1 Like
The landing runway is currently selected by MSFS over which FSLTL has no control and the parameters it uses don’t always agree with RL. The sim just takes the aircraft info from FSLTL and adapts it to whatever is happening at the time. This has been a bone of contention for a long time and was supposed to have “improved” in SU14 but not by much it seems.
Hopefully this is being worked on by BeyondATC, one of whose developers also works for FSLTL, not quite ready for release yet as the main dev wants it right. Looking for Q!/2024 although he makes no promises.
2 Likes
Base model update was released yesterday. I just noticed.
FSLTL Base Models 1.3.1 available in FBW installer (Final version for 2023)
VMR file fully updated this time Version number in manifest updated to 1.3.1 (AddonLinker, etc) Corrected Porter Airlines DH8D to use correct PTR ICAO code instead of POE
Interesting, thanks for the explanation.
Airports are nicely filled for me but I hate the sims fixation to use Runway 19 at Brussels (my home airport) regularly, which is not the case in real life.
Has anyone run the texture optimizer against the new v1.3.1 base files? It so, any issues? Apologies if this has been discuss elsewhere!
1 Like
I ran them, down sampled to 1k textures, and I think it ended up around 4GB.
2 Likes
I haven’t yet, but planning to if I can remember the next time I have a moment to spare. I haven’t even tried SU14 yet aside from just a few minutes with the drone cam checking frame rates.
I know this is more of a sim issue rather than FSLTL but I was curious if anyone else has experienced this lately.
When I start the injector and the static planes are injected the sim all of a sudden removes a handful of not almost all the statics. As soon as the injector shows a static was injected it then says “removed by MSFS engine”.
My injector settings haven’t been changed in a while and everything is up to date. This is happening on payware airports which I have never seen happens at them before. For example at KSEA (BMWorld).
Anyone else notice this?
Hi , I found a fix for this . I am using the current version of FSLTL Base model as of today . But the pink models are still existed .
So this is the fix .
There are three FSLTL_ A320 liveries that have pink textures I have found so far :
1/ FSLTL_A320_AAY
2/ FSLTL_A320_DAL
3/ FSLTL_A320_VIV
It is because of textures config fallback are incorrect that cause textures conflict .
OK , so go to community folder and find :
fsltl-traffic-base/SimObjects/Airplanes/FSLTL_A320_AAY/TEXTURE.AAY/texture.CFG
The correct fallback in the texture. CFG should be edit so it looks like this : ( Note : The fallback text line below somehow does not show correct as I type . It should be : dot dot backslash dot dot backslash THEN FSLTL_A320\TEXTURE ) Or you can copy from other correct texture.CFG liveries .
[fltsim]
fallback.1=…..\FSLTL_A320\TEXTURE
That’s it , done .
Do the same with the other 2 liveries .
1 Like
I have the same issue with the beechcraft kingair. It’s definitely an FSLTL model issue as it only appears while using FSLTL.
1 Like