ConstVoid

The FSHud developer is trying to reach out to Fenix so that a mutually acceptable workaround can be found. The issue seem to be around some dummy aircraft objects that Fenix V3 creates. FSHud sees these as AI aircraft and tries to perform its usual actions (Import, Remove, or Ignore). The first two of these seem to cause the pushback problem and the third one causes issues for some traffic sources. Although a workaround should be possible, the FSHud developer wants to ensure Fenix are aware of the problem so that future updates wont prevent the workaround from working.

I have just posted the following on the Fenix server in relation to repeated creation/deletion of aircraft with type "Fenix Dummy Object": Yes - I'm seeing this too. I've counted 3 so far. left-FNX, nose-FNX and right-FNX - something to do with gear perhaps? These are regularly being created, and I suspect they are in some way responsible for the odd behaviour noted with FSHud ATC. It seems these are detected as AI simobjects, and if FSHud is set to Import or Remove AI simobjects then this causes the weird pushback issues, and can only be corrected currently by setting FSHud ATC to Ignore such objects. This can have consequences for some users as they rely on FSHud ATC being able to convert MSFS controlled aircraft to FSHud ATC controlled aircraft using the Import option.

I've not seen anyone say that the code in the FSLTL injector to inhibit injection if FSHud is active has ever been removed, so I assume it is still the case.

I don't think any other products intercept AI traffic injection like FSHud ATC can do to turn an MSFS controlled AI aircraft into one controlled by FSHud ATC. It's strange, because it means that something V3 does is making it look like an AI injected aircraft as far as FSHud ATC is concerned - this never happened with earlier versions.

Doesn't that mean that FSLTL stops injecting any new traffic after FSHud ATC is started? This has been a problem ever since the FSLTL team introduced a block on their product being used if FSHud is running.

Setting it to ignore will only be a problem if you have some traffic source directly injecting traffic to MSFS. This could be MSFS native live traffic, AIG TC without the FSHud option, etc. If you don't use any of these, and instead use other methods like the in-built AIG option, or AIG TC with the FSHud option then Ignore is safe, but you must ensure that MSFS Live traffic etc. is disabled, otherwise you get traffic which FSHud ATC knows nothing about - these will taxi through your aircraft, land on different runways to you etc. etc.

I'm sure we'll see improvements with the next update as better communication is the feature supposed to be next on the roadmap. Unfortunately there's no information on when we'll get that update - it's already been quite a few months in development.

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.