So FSHud should be working properly now with the static models?

This works very well !
Been using this with the FSLTL as static etc.

https://flightnews24.de/2026/04/30/live-traffic-mit-fsltl-1-9-0-so-gehts/

On 4/23/2026 at 9:18 AM, Noel said:

This belonged in the recent thread that was locked:  try default RealTime traffic.  I'm first trying this now at SKRG and I couldn't tell the difference between it and FSLTL.  I do use BATC but sometimes avoid using its injector and this seems to work fine as a sub for FSLTL.

I gave the default Real-Time traffic a try and it seems to work fine just like FSLTL with one major exception.

With either FSLTL or default Real-Time traffic, the biggest problem for me with these uncontrolled A/C roaming around in  airports is that they are.... uncontrolled- they cut you off at taxiways, go through you, etc. so what we gain in realism visually, we lose functionally.   FSLTL had mitigated this problem via the in-flight menu by giving us the option to remove nearby A/C or reset air traffic.  For me being able to avoid such occurrences at critical times, e.g., while taking off or landing was key.  There is no such option with the default Real-Time traffic and for me this is a show stopper.  Taxiing becomes a video game especially in busy airports.  In the near-term I will continue to use FSLTL since the eye candy aspect of flight simulation is low on my priority list and make a longer-term decision later (I have seen the various posts with other options).

That’s pretty much where I landed too. The default real-time traffic can look convincing enough in the air, but once the airport gets busy the lack of any quick traffic reset or nearby-aircraft cleanup becomes the real drawback for me, not the visuals.

That’s why I still separate the two jobs in my own setup. For airline presence and model coverage I can live with AIG or better models on top of the sim traffic, but for the actual IFR flow I still prefer a dedicated ATC layer because the ground behavior and spacing are what break immersion first.

If Asobo eventually gives the stock traffic better control on the ground, I think a lot more people would be happy to stay native. Right now it still feels like the eye candy has moved ahead of the logic.

Edited May 2May 2 by Cloud Surfing

Like several of you I've decided to try MSFS live traffic since FSLT isn't working for injection anymore. I use FSLT for parked traffic and AIG for the models. I find it convincing enough given the state of AI traffic in MSFS but I can't get any default traffic to push back. They will take off and land  but they will only spawn on taxi ways. Some will spawn on gates but then disappear.  Any of you guys using live traffic get push back traffic from gates? Just curious to see if it's a problem from my end.

You're not the only one. In my experience with stock live traffic in 2024, pushback from gates has been pretty inconsistent. I still see a lot of taxiway spawns and gate pops or disappearances, especially once the airport gets busier. That's basically why I can live with the default live traffic for some airborne ambience, but I still don't really trust it for believable airport surface behaviour. If you already have AIG models and FSLTL statics in place, what you're seeing sounds more like current sim behaviour than something broken on your end.

Thanks for the answer. I never thought after all these years with MSFS I would miss P3D traffic logic.

 

just got BATC with AIG models and looking good at YBBN.

Did a quick flight from EGLL to CYEG this morning. Good traffic representation (I was #6 in line for departure) but BATC got stuck with traffic piling up in line for the active where the two taxiways merge at 27R.  Had to remove two different aircraft to get things to flow again.  Good, but not great.  

 

I gave the default Real-Time traffic a try and it seems to work fine just like FSLTL with one major exception.

With either FSLTL or default Real-Time traffic, the biggest problem for me with these uncontrolled A/C roaming around in  airports is that they are.... uncontrolled- they cut you off at taxiways, go through you, etc. so what we gain in realism visually, we lose functionally.   FSLTL had mitigated this problem via the in-flight menu by giving us the option to remove nearby A/C or reset air traffic.  For me being able to avoid such occurrences at critical times, e.g., while taking off or landing was key.  There is no such option with the default Real-Time traffic and for me this is a show stopper.  Taxiing becomes a video game especially in busy airports.  In the near-term I will continue to use FSLTL since the eye candy aspect of flight simulation is low on my priority list and make a longer-term decision later (I have seen the various posts with other options).

I've found this, conflicting ground traffic, is more of an issue with BATC than w/ RT traffic, and find FSLTL's version of it was about the same. One factor will be density. For me, it's relatively uncommon to have conflicts overall and when it happens just cope with it because ultimately there are too many positives to go back to BATC's traffic manager.

I don't know why but for some reason now when I use MSFS24's RealTime Traffic, have BATC's traffic OFF, I'm now getting mostly generic plane models on the ground and presumably in the air, whereas when I started this thread I got mostly all FSLTL liveries. I've been away about a month and wonder if others using this model are experiencing this change.