@FSHud

Looks quiet promising.

I am just wondering how Fs Hud ATC can give instructions to Live Traffic ac that can have real world changes, like diversions, delays, another SID/Star/ Approach.

 

19 minutes ago, GSalden said:

@FSHud

Looks quiet promising.

I am just wondering how Fs Hud ATC can give instructions to Live Traffic ac that can have real world changes, like diversions, delays, another SID/Star/ Approach.

 

As I mentioned previously, live traffic is managed independently by FSHud - Air Traffic Control according to the airport configuration and other factors used by FSHud, such as separation.

This means that once an aircraft is injected into the simulator, its next states are separated from what continues to happen with the real live traffic aircraft.
From that point, the aircraft has its own flight lifecycle inside the simulator, which may differ from the real one.

Great to see FSHud continue to add impressive new capabilities and looking forward to the new Major improvements to existing traffic sources as well.  

17 hours ago, FSHud said:

 

As always, development priorities have to be balanced between many requested areas — adding more traffic types, improving AI behavior, improving voices, and refining airport/runway handling.
We will continue improving these areas as priority and technical feasibility allow.

Absolutely understandable, yet I cant see any much more immersion breaking thing in the current FSHud state than this missing pushback feature. It ruins everything the moment a plane starts moving on an airport and I honestly dont understand why it is not pretty up on the priority list. Because for me, it belongs to THE main AI traffic behaviour features. But that is just me then 😉

Good to see this moving forward. For me the scheduled traffic part is especially welcome, because that usually does a lot for making the world feel less generic on IFR flights. I still care more about how it behaves in day to day use than feature lists, but this looks like a genuinely useful step in the right direction.

On 5/6/2026 at 10:24 PM, bmarcoux2 said:

Tryed Fshud again this morning at KSAN. Shut it down when it told me to taxi to runway 09. 09 is pretty much Never used at KSAN

FSHud has an airport configuration editor, which would allow things like this to be managed. One very simple option in this case would be to 'close' 09 as far as FSHud is concerned, but the editor provides many more more subtle options.

This is the kind of update I was hoping they would eventually add. For me the interesting part is not just the live side, it is having scheduled traffic in the same ecosystem so the airports do not feel empty or random once live coverage gets thin. If it works reliably in day to day use, that could be a very solid step.

Is this out yet?  I already have fshud 2.1.127.  

 

I'm waiting for this one too.

What I really want to test is seeing real aircraft around me again directly through FSHud. If this works well, it could be a much cleaner solution than the old FSLTL setup, especially now that FSLTL is not really an option for FSHud anymore.

For me the interesting part is not only the traffic itself, but how well it all works together with the ATC side once it's out.

That scheduled traffic part is actually what interests me most.

Live traffic is nice of course, but schedules by airport could make a big difference for day to day flying. If it works the way it sounds, you should not only see aircraft passing through, but also get more believable departures and arrivals around you at the airport itself, even when live coverage is thin.

That’s the part I’m really curious to test, because if they pull that off well, it could make FSHud feel much more complete on its own.

For products that inject traffic, for me the single most important factor is AI traffic being aware of my aircraft's presence and AI aircraft adjusting their behavior accordingly. AI aircraft going through my aircraft like a hot knife going through butter, especially at intersections and runway holding points, is a show stopper regardless of the level of sophistication of other features.

How will the new FSHud release manage AI aircraft behavior with respect to my aircraft ?

Just need actual pushbacks (instead of the 180 no-scope that’s currently the case) hopefully this wasn’t forgotten!

4 hours ago, zachlog said:

For products that inject traffic, for me the single most important factor is AI traffic being aware of my aircraft's presence and AI aircraft adjusting their behavior accordingly. AI aircraft going through my aircraft like a hot knife going through butter, especially at intersections and runway holding points, is a show stopper regardless of the level of sophistication of other features.

How will the new FSHud release manage AI aircraft behavior with respect to my aircraft ?

First of all, FSHud - Air Traffic Control is an ATC add-on, not a standalone traffic add-on.

However, traffic is a fundamental part of any ATC environment. For this reason, traffic management and interaction with the user aircraft have been core requirements of FSHud - Air Traffic Control from day one, and this logic has been continuously developed over the last five years.

FSHud does not simply inject aircraft and leave them unmanaged. AI aircraft behavior is controlled according to the ATC environment, airport configuration, separation logic, runway usage, taxi routing, and the presence of the user aircraft. This includes managing conflicts at runways, holding points, taxiways, and other areas where aircraft interaction is required.

How long until release?

7 hours ago, FSHud said:

First of all, FSHud - Air Traffic Control is an ATC add-on, not a standalone traffic add-on.

However, traffic is a fundamental part of any ATC environment. For this reason, traffic management and interaction with the user aircraft have been core requirements of FSHud - Air Traffic Control from day one, and this logic has been continuously developed over the last five years.

FSHud does not simply inject aircraft and leave them unmanaged. AI aircraft behavior is controlled according to the ATC environment, airport configuration, separation logic, runway usage, taxi routing, and the presence of the user aircraft. This includes managing conflicts at runways, holding points, taxiways, and other areas where aircraft interaction is required.

Thanks for clarifying.