This sounds lile you habe 2 copies of FSLTL installed.
Check the download location in the FlyByWire installer.
Thats where you updated to the current version that spawns traffic correctly.
And then go to your community folder
There you will find an outsated version that only spawns ground traffic.
I would suggest to delete that outdated copy and then update the path in your exe.xml to point to the current version.
That way FSLT will start with MSFS and use the current version that you can always update woth the FlyByWire App.
Edit: just saw you use addon linker. Well, simply apply my suggestion above to the way addon linker works.
Currently you are linking the outdated version.
You will have to get the path where the FbW App is installing to into addon linker
Thanks Wined2310!
You were right. I seemed to have an older copy running which caused the problem.
I did like you suggested, deleted the older copy and adjusted the correct path.
Everything works fine now
Thanks
Amazing how often that double Community Folder situation causes problems of all sorts. Perhaps it should be a first check for anyone with any problems!
Curious if what I saw the other day was a real flight track from FSLTL, or some sort of bug/quirk. I was on a flight from KGRB to KASE and somewhere over the central states I saw an aircraft running a back and forth pattern. I happened to have the VFR map up and noticed it doing this the entire time it was within my “bubble.” It was too far below me to notice what kind of aircraft it was or the livery, but it was moving fast enough that I’m pretty sure it was a jet. The flight path was similar to this, but this image was just a random from the net and not this particular flight in question.
Mooncatt I live in Charlotte, NC near a muni airport and noticed a single engine doing pattern work above so pulled it up on Flightradar24 and its pattern resembled this. No idea what it was doing but curios as heck.
My question wasn’t so much about what the plane was doing, but whether or not what FSLTL was doing was mimicking a real flight. It operates on IFR flight plans, but I thought those flights are VFR.
I was reading an article a few years ago from a kiwi pilot in NZ that did those flights, aerial mapping for local councils (which then get sent to Google maps) and also for post natural disaster mapping… Great we read…
Those flights are all GPSed out as you need to be accurate with your laps so you don’t over fly the same laps etc.
So basically those mapping flights are, effectively ifr
Not the article I was reading but that’s the aircraft used mainly in NZ
Looks like an update (v1.3) to the Base Models dropped this evening with new liveries and other changes / improvements. FYI, for those of you who don’t get Discord notifications.
FSLTL Base Models 1.3 available in FBW installer
Added B788 (38 liveries)
Added AT45 (16 liveries)
Added AT46 (8 liveries)
Almost 100 additional liveries across our existing models (over 1900 now!)
Refreshed .vmr file for VATSIM
Model changes & fixes:
Fixed multiple broken animations on flaps/reversers
Added ‘drooping elevator’ animation when parked
Sounds:
Improvements across the board for all models
Complete revamp of startup and shutdown sounds
Improvements for VR and headphone users
Effects:
Fixed effects to work better on all model LODs
Optimized various heat blur effects with less impact on FPS
Lighting:
Now offer the option between the faux flare and “no flare” lighting, with no flare as the default (easy manual steps to switch as needed)
Flash rate for nav and beacon lights are different to better match real life
Taxi/landing lights are now fixed to front gear as appropriate and disappear when gear is retracted
Some models now have logo lights on while parked to add variety at night
Interior lighting now have different colors
Exterior lighting now appear smaller at distance
Fixed lighting issues/conflicts on some user-controlled aircraft models
Wingspan:
Wingspan values for all models have been set to approx 10% below real life values. This helps towards working around the sim’s extra 6m diameter added to parking spots in scenery.
Note 1: You may notice aircraft parking in spots they did not park before, depending on scenery design. To fully take advantage of this wingspan reduction, matching changes to scenery parking may be needed. (Scenery Devs: feel free to contact the FSLTL team for details if needed)
Note 2: Because the wingspan values for a particular aircraft type may not match the wingspan of that same aircraft type from other sources, you may notice parking differences between FSLTL models and others
We’ve noted a number of times on our discord we are lacking modellers. Hence these don’t exist.
You have modelling experience and want to come make them - drop us a line on the discord.
I do struggle with what is such a common thing in the flight sim community - people focussing immediately on what’s missing rather than what has been done. This all takes a huge amount of time and effort from the team for free.
There is still room for improvement in the aircraft.cfg file details so that ATC calls the aircraft model correctly and that model matching works properly when required:
atc_model = “A320” - will be ignored by ATC.
atc_model = “$$:A320” - will be announced as A320 by ATC.
icao_manufacturer = “A320N” - will be ignored for model matching.
icao_manufacturer = “Airbus” - will be recognised for model matching.
Anyone who is serious about MSFS Air Traffic should be on top of this stuff by now.
