ConstVoid

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.

Of course

We'll just have to await whatever the FSHud developer is referring to in the above paragraph. Meanwhile I'm happy with the AIG support in FSHud, although it has one or two issues.

I didn't have to set up custom views. I just tried the default Fenix views one by one (shift 1, etc.) until I found one with the panel I required, and configured POM to place it where I wanted it. When I run POM it deals with all the panels I've configured, one after the other, regardless which view it needs to select to find the panel.

It can only pop-out "panels" that you can pop-out manually using something like alt-gr mouse click - that's a restriction of MSFS I believe. Nevertheless it works well and I always run with it.

Another vote here for 320simpilot who was an A320 captain. If you go to his channel on youtube you'll see a few playlists, one of them specifically for the Fenix. These include some videos designed as generic A320 tutorials. They're a bit old (320simpilot has since gone to the 'dark side' and is now a real world Boeing 787 captain 😀), so a few details specific to the Fenix might be a little out of date, but the general principles of flying the airbus won't have changed and I found his style very informative.

Just for clarity, the 2024 upgrade charge was only for those of us who purchased (and presumably enjoyed using) FSHud well before 2024 was released. Nowadays purchasers of FSHud pay one price and are able to use it on 2020, 2024, and P3D.

Absolutely incorrect as far as FSHud is concerned. Sure it has to know where you are, but that's part of the sim. There's no interaction with FSHud required - if it's running it will generate traffic around you, and control and communicate with them. Many people, myself included on occasion, simply do that for traffic spotting.

Did you have AI traffic in the area. FSHud will try to separate you from traffic, firstly by requesting you and the traffic to fly at specific speeds. If that doesn't achieve the required separation it will vector you as required. If you believe the vectoring was erroneous you should capture a screen shot of your FSHud window (both comms and map) and submit a ticket. That will allow the developer to examine the logs to identify the problem.

As you may know I was a long-time user of RC, but my attempts to use it in MSFS were fruitless, and I think that even people more adept with FSUIPC etc. would find it impossible without the source code. Sadly, even if it were possible somehow, I think the devotees of BATC, SI and FSHud would find it rather dated, with its lack or real support for SIDs, STARs and approaches, no real idea of MVAs etc. Too much is left to "pilot's discression" which wouldn't satisfy today's user expectations. The vectoring, emergency procedure support, etc was good for the time, but I'm sure the current crop of alternatives are improving all the time.

That goes without saying, as FSHud already gets the current airport layout from MSFS (default or add-on) to determine the taxiways etc. Editing will surely just be added as an option on top of that.

We'll have to wait and see what's actually delivered in terms of airport editing, of course, but I have the impression from previous comments from FSHud that we won't actually be able to 'fix' taxiways that are broken or disconnected, but we will be able to change their identification among other things to avoid taxiway instructions that might say 'via C C1 C C2 C', and replace them with just 'C'. I just hope no-one is being too optimistic about the upcoming feature.

Discord has provided a forum-like option for a while now, and many developers use that for the problem reporting sections of their discord. Each problem gets its own thread, so its responses are grouped together.

FSHud will tell you to expect a particular arrival and approach shortly before the calculated TOD, which I guess it does via a 3 to 1 rule or similar calculation. It then asks you to descend when ready to a cleared flight level, usually corresponding to the first altitude restriction in the STAR, so it's up to you if you delay the descent for a while or start down straight away. It's at this point you can select another arrival etc. once you are close to the beginning of the STAR it will clear you for the selected STAR and approach. Transition altitudes vary throughout the world - I think it gets them from the navdata (Navigraph).

FSHud works with MSFS 20/24 and with P3D (although I've never used P3D so I don't know how different is is on that sim) - there's no free trial, but it's on sale this month. The FSHud application must run on the same machine as the sim, but the UI can be accessed via a browser, so could be any machine on your network. It will typically give you a STAR and approach for you to follow shortly before TOD. You have the option of selecting different arrivals, approaches and runways as you prefer, including vectors if you wish. There's no FAA vs ICAO terminology, which is a pity. It's more similar to ICAO, but could do with a bit of improvement for regional use. As a long-time user of RC 2, 3 & 4 myself, there are one or two features currently missing (such as emergencies), but generally I think FSHud shapes up extremely well against RC.

At the moment the developer is keeping the production branch more or less in-step with the beta branch. Patches get released into beta, then a couple of weeks or so later they get rolled into production. I would expect that close relationship to be changed when the 2025 Roadmap updates are with us, as I would expect there to be a more extended amount of time between beta and production updates to allow new features to be fully tested by the community. In the end it mainly depends if you want to be on the 'bleeding edge' of new developments or prefer a more stable life as to whether you choose beta or production. (As an aside, I see a number of references to FSHUB rather than FSHUD in posts - is that just a spell-checker thing or is there/was there something called FSHUB too?)

Replying to PM received from oleg28: I'M PLAYING MSFS 2024 FSHud B NHFABR FSLTL WHEN THE PLANE LANDS AND STEERS INTO PARKING, THEN IT DISAPPEARS AND IT'S ALL PLANES Please don't PM me responses to posts in the forums. I think the best option would be for you to open a ticket with the developer - there's a button for that in the FSHud application. This will allow the developer to see the logs.

Sorry, even with your translation I don't understand the question.

OK - I've posted about this before, but the cut-down version is that there are three ways to get AIG traffic in FSHud. Run AIG TC without the FSHud option, set Simulator traffic to Enable in FSHud. Disadvantage: Will use more resources than other methods - TC spends time injecting aircraft which FSHud may discard for various reasons. Use Simulator traffic set to remove and check AIG box in FSHud traffic settings. Don't run TC. Advantage: Probably most efficient. Disadvantage: Less enroute traffic. Use Simulator traffic set to remove, uncheck AIG box, run AIG TC with the FSHud option. Advantages: more enroute traffic than 2. more efficient than 1. Disadvantage: still have to run AIG TC, so less efficient than 2.

I know some people don't like discord, but the FSHud discord does have a support channel, which has threads, like a forum. It doesn't replace the built-in ticketing system, as that ensures that the application logs are included, but it does allow a thread to be created (maybe with a similar title to the ticket) which allows screen captures and other information to be added to provide supporting information for the ticket.

You obviously missed my post above, which summarised the requirements for using FSLTL in FSHud: