FSHud - Air Traffic Control - 2025 Roadmap

Thanks for the reply mate.

I firstly want to say that, I was one of the very first buyers of this product and over the last four weeks, especially realizing that I had to connect it up to Navigraph :rofl::joy:

I have absolutely ENJOYED this product and am so glad I have never gone down the STAR of other two routes. See what I did there :rofl: I’ll see myself out..

It has absolutely revolutionized my experience in msfs and thank you.

Just a couple of things.

One was the reply above but firstly…,

One thing I do miss from the early days of fshud was the randomness of runway departure intersections like for example. A departure from Auckland airport 23L with the A320 or ATR and getting directions for A2 or A3A (turboprop)

I dont seem to be getting that at all recently over the four weeks I have been using FShud. All of my departures with the smaller aircraft have seen me use the full runway at the respective international airports with long runways. Is there something I’m not doing right or some limitation in 2024?

Going back to the old aircraft and old school navigation flying.

I’ve been making an effort in regards to making sure that there are no rnav SIDs/STARS in both, navigraph and fshud with some mixed results

I get the standard VOR departure but I still get offered an rnav approach for my arrival.

Like I suggested.

It would be cool if its not a major re coding, for a tickable option in the fshud game interface to turn on “flying a old school aircraft” mode and for that mode in fshud to give you the respective old-school radio navigation/vecotring/visuals for the respective airport. You could call it “old-school mode” sounds real cool. Then for some complete randomness of fahud atc giving out those radial arc approaches (as I belive it was rare for ATC to actually give those arc approaches and majority of those VOR approaches to be vectored in)

Just one more thing.

Flightplans that have the airport/vor as the last way point.

It would be cool if vectoring for the respective ILS/VOR/NDB/Visual approach started before hitting that last way point.

Some airports like for example with Sydney, if your flying from New Zealand. Sometimes (FR24) you do fly over the DME other times they start vectoring you before the final waypoint in this case, Sydney airports DME.

But like I say man. I absolutely :100: love this product and especially over the last four weeks with the updates and figuring out navigraph :sweat_smile:… I have been absolutely loving it all the more.

Just a few things like above would take it to the next level.

Thanks for sharing your experience.

Regarding intersection takeoffs: you can adjust this in the aircraft settings (see the manuals).
Reduce the required takeoff/landing distance; if the taxi distance to the runway threshold is too long,
you’ll be assigned an intersection departure.

Regarding “flying an old-school aircraft”:
in real-world operations this is referred to as “RNAV-equipped,” and it’s typically specified in the Aircraft Equipment section of the flight plan.
I agree this option should be added.

Thank you

Really appreciate the continuous work on FSHud — great to see all the fixes and updates lately!
I’m a happy user and just wanted to say thanks.
Also, awesome move with the Halloween discount — perfect timing!
Looking forward to the next updates on the roadmap. Keep it up! :jack_o_lantern::airplane:

1 Like

I am looking into FSHud thinking of buying it. Now that it’s the end of the year, what of this roadmap has been achieved? Because it looks very promising but I can’t really find a good list of features that FSHud offers at the moment and wich ones will come in a future update.

Also does FSHud require a Navigraph subscripiton because I’ve read this somewhere, or a least read that the Software heavily relies on Navigraph.

I hope the status bar UI can be made smaller, as it occupies too much space on my screen

1 Like

I was away for a few months (work), and I was so surprised when I came back! I want to say thank you to @fshud3909 and the entire team for bringing the Airport Configuration Manager! I am now able to configure my favorite airports according to real-world operations. On top of that, I can configure each parking spot, placing airlines that actually use those spots! That’s amazing! Thank you!

3 Likes

What about information on the mobile tablet? I can’t bind with FShud on the PC.

Please check firewall settings, if it works on another device or another browser in your tablet.
Those are the main reasons why it might not work on the table.

It seems like quite often FSHUD on a final approach (in this case RNAV RWY 10 at MBPV, a very small airport), will tell me to go ahead with the approach (transition) and then while the plane is following a logical path to the Final approach fix, will tell me to turn in all sorts of directions, often 180 degrees from the heading to the runway. It will give me heading instructions every 5 or 10 seconds on a wildly zig-zag course. Eventually it will have me on a correct final. If I ignore it and just let the FMS guide me through the RNAV (or other) approach, all will be well and I get to the runway a lot quicker than following all these heading changes.

I can understand these maneuvers bering necessary in a very busy airspece for traffic avoidance but at a small airport it makes no sense. This has happened frequently and makes it difficult to use the ATC program, though I generally consider it a good ATC addon.

Is this common with other users?

Further experimenting with FSHud leads me to some more comments-

I did 2 flights with it today. both were from LSZH to LOWW, large airports with multiple procedures available, in a Cessna Citation and with a Simbrief flightplan.

For the first flight I just followed the FMS, choosing the runway and arrival in the Simbrief plan. I used VNAV for all my descent and did an ILS approach. It went perfectly.

For the 2nd flight I listened to all descent and heading instruction from FSHud. They got me down from my cruise altitude of 21000 ft to 5000 ft before vectoring me to a different heading every 10 seconds, zig-zagging way more than should ever be needed. I talking about headings changing by up to 100 degrees, every 5 to 10 seconds!Finally they got me on the ILS path (MUCH longer than when I just ignore ATC and let the FMS do it’s thing). However by that time I was way too high to catch the glideslope since they never told me to descend below 5000, so I had to abort the landing.

This has been my experience lately, especially if ATC gives me a different runway or arrival than the original one in the Simbrief plan (and I select that in the FMC mid-flight). It seems (maybe just my memory) that it did not used to have these constant inaccuracies.

Is it me or the program?