ConstVoid

For both @Shomron and @jcomm : Yes you can use FSLTL models with MSFS live traffic, without any other add-ons, so you would be using the FSHud ATC in-built facility to intercept the traffic being injected by MSFS and import it into FSHud. I don't use this method, so the only advice I can offer is to read FSHud - Air Traffic Control for details. A few extra comments: A lot of people, myself included, prefer to use AIG models due to the variety of airlines and liveries available, as well as the ability to use lower resolution textures for performance. There is a bit more of a learning curve to set this up initially, but once done updates can be managed very simply. The MSFS in-built live traffic doesn't give any hints to FSHud ATC about future flights, so FSHud ATC has no way to ensure that the correct aircraft are parked and ready at the airport. FSHud Traffic (subscription) and AIG traffic schedules both provide that data. MSFS live traffic is just that - it takes no account of the simulator time, so if you use the MSFS ability to adjust the time of your flight you may notice less or no traffic in your vicinity if the local time is different from the real-world time. Again, both AIG scheduled traffic and FSHud Traffic can use the local time to give you a realistic amount of traffic for the time of day.

FSHud ATC is a one-time purchase, as you say. This thread was started to talk about FSHud Traffic, which is a subscription add-on to FSHud ATC, which provides live and historical traffic for the product. You don't have to use FSHud Traffic if you don't want to - you can use other traffic sources such as AIG or MSFS live traffic for free. I think a free trial of FSHud Traffic is still available if you want to give it a try.

OK - I understood from your previous post that you were using MSFS live traffic as the source - is that the case, or are you trying to use the FSLTL injector with FSHud ATC? If that is the case you are out of luck. Some time ago FSLTL amended their injector to prevent it from working if it determined that FSHud ATC was running. The FSHud developers had nothing to do with that decision, and can do nothing to get FSLTL to work with FSHud ATC.

I think this would have been better in its own thread, as it has nothing to do with FSHud Traffic (the subscription traffic source for FSHud). However... I don't use MSFS traffic, but whenever anyone has problems with using a non-FSHud traffic source my suggestion is to make certain that it is working satisfactory without FSHud running. If the amount of traffic is ok then starting FSHud with the 'Import' should give similar amounts (assuming that the traffic settings for parked and active are not constraining the traffic). What aircraft models do you use - e.g. FSLTL or AIG? Are you sure you have sufficient models/liveries available to represent all of the required traffic. If you're using MSFS 2024 remember that the MSFS in-built models cannot be used by FSHud - you definitely need an alternative set of aircraft models.

You're right, FSHud ATC used to have that restriction. These days you can use a copy of your own Navigraph data if you've had a subscription sometime in the past. Disclaimer: I've not used that feature myself, as I do have an active subscription, but I think you need to have saved the downloadable Navigraph data, for example the one used with Little Navmap.

Yes, but that is often a sign that something big is on the way. FSHud_Admin has previously indicated that improvements to voice interaction, AKA "AI", is supposed to be the next thing on the roadmap.

I'm running with FSHud Traffic and AIG (TC + external options). This combination gives me as much traffic as I need, and AIGTC fills in a few gaps where FSHud Traffic misses the odd Airport/Airline/Flight. I use the simulator time option for FSHud Traffic - is this what you referred to as historical?

Not sure FSHud Traffic will be expanded to include non-commercial traffic - it would probably increase the cost significantly. Meanwhile running FSHud Traffic and AIGTC alongside each other works well for me.

I run AIGTC alongside FSHud Traffic (with appropriate settings in both) so that I get quite a few executive jets, turboprops such as PC-12s etc. It livens up the traffic variety, especially as smaller airports.

Are you just sitting there watching the progress bar while TC scans the flightplans? I start TC after MSFS loads, then I go do flight preparation. By the time the aircraft is ready to push and start TC has usually finished loading. Until that point I'm not looking out of the windows, so it doesn't matter if there's no traffic around. Alternatively, you could check the AIG option in FSHud ATC traffic settings - this should load traffic in more quickly. Some time later you could uncheck AIG and just run TC if you're concerned about resource usage. These days I use FSHud Traffic, which populates the airport very quickly, although I also run AIG TC to get its GA dynamic traffic and any flights that FSHud Traffic might miss.

The FSHud ATC traffic setting AIG selects whether or not you want the in-built injector to add traffic from the set of traffic installed by AIG - either the base pack, or additional airlines. Using AIGTC with FSHud ATC is independent of the above setting. To use it you run the AIG Traffic Controller with the FSHud option specified, and you ensure that the FSHud ATC traffic setting 'External' is checked. Typically you do not also have the AIG option checked, although it doesn't cause any problems if you do, other than perhaps using more CPU than required. In AIGTC I set the amount of traffic to 100%, and use the FSHud ATC traffic settings to limit the amount of traffic to numbers my system can cope with. Usually people find that this method gives more traffic than the AIG setting above.

What method do you use to inject traffic in FSHud ATC? It's generally recognised that AIGTC with the FSHud integration turned on and External selected in the FSHud ATC traffic settings will give you more traffic than the internal AIG option. Of course, you may find that you could get more traffic by installing extra airlines using AIM, as you suggest.

Does anyone know if BATC injected aircraft have these variables set? I know that FSHud ATC aircraft don't. They are actually documented in the SDK, but in the Miscellaneous Variables section, which says: The following SimVars are still supported by Microsoft Flight Simulator 2020, but are considered legacy and will not be getting any further support or updates. As such, we don't recommend their use in new aircraft. And specifically for AI TRAFFIC FROMAIRPORT: The ICAO code of the departure airport in the current schedule. This variable is only valid for aircraft generated by the traffic database that have schedules. If an aircraft does not have a schedule, the value returned will an empty string"". It's also marked as not settable, so that's probably why the ATC app developers are unable to set it.

Presumably you are using an old version of the injector which hasn't had the FR24 data fetch removed from it. As I understand it FR24 'asked' FSLTL to create a new injector which doesn't attempt to access FR24 data without payment, and not to make old versions of the injector available. This can't operate retrospectively, so if users have not updated their injector they will still work.

You might do better asking in the Little Navmap forum here on Avsim, but I seem to remember that it's something to do with the way the scenery database is built from MSFS 2024. Because it can't do this by scanning the BGL files as it used to in older versions it can't tell the difference between base airports and add-ons.

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.

Well FSLTL did also say that it was their agreement with FR24 which was forcing them to make the change to remove the FSHud API connection from their injector. If FR24 say there was no agreement it sort of casts doubt on that statement. Also, if it wasn't FR24 that was causing this change then, conspiracy theory or not, it makes the BATC vs FSHud argument more likely, especially given that the developer (whakamolenz) was/is still active in both BATC and FSLTL support roles.

How on earth would that work? PSXT traffic replicates the movement of the real world aircraft by interpreting their ADSB data. FSHud needs to be able to position the aircraft as it sees fit, so that it can control them in the same way as the user aircraft. They're just (and in my opinion always will be) incompatible products.

It will.

No - because @jwhak was asking explicitly about live traffic with FSHud, which means that PSXT is a non-starter. I don't think I need to re-iterate why.

Well, not exactly, but at the moment if you want live traffic your options are fairly limited, such as MSFS's own live traffic.

Correct -PSXT does not interact with any ATC (except notionally real world ATC) - so MSFS default ATC, BATC, FSHud or whatever, are not able to control PSXT aircraft. I'm told some of them may 'see' the PSXT aircraft, and advise the user to avoid them, but that's as far as it goes. If you insist on seeing traffic as it is in the real world then by all means use it, but if you want your chosen ATC product to interact with the traffic then use something else, like AIG.

FSHud itself doesn't provide any traffic schedules - it can use FSLTL models, but something would need to inject the traffic. The FSLTL injector used to, but doesn't any more. MSFS live traffic can use FSLTL models with (or without) FSHud. IMO the best option, however, is AIG, which provides both models and schedules. You can use that in FSHud either using FSHud's own AIG option or with AIG TC/FSHud integration.

PSXT is controlled by real world ATC. Neither default ATC, BATC nor FSHud have any influence on it, which is one of the reasons I would never touch it.

AIG really isn't that difficult - you may have tried it long ago, but the AIM is now very good and virtually does everything for you. The initial install may take a while, but once that's done keeping things up to date is simple. AVSIM is being used less and less with AIG because the library seems to cause too many problems. FSHud doesn't need to use an external injector if you use AIG or MSFS live traffic.