malichek

That predictability point is one I keep coming back to too. At busier European hubs the traffic flow during approach is complex enough that having consistent behavior instead of random movements actually helps with descent planning. With FSHud historical traffic loaded for my evening sessions, the arrival sequencing stays coherent all the way through, which matters when you are trying to manage a proper approach into a field like EDDM or LFPG during a simulated busy period. It is probably even more important at the smaller regional airports you mentioned, where you do not have full radar service sorting things out.

For me FSHud is mainly an IFR tool. I fly the 737 almost exclusively, so I mostly notice what it does during approach and departure phases at busier European airports with historical traffic loaded for my evening sessions. The vectors and sequencing work well for that kind of offline IFR workflow. For VFR I can see it being useful if you want traffic around you, but at smaller GA fields the density might not be there to make the subscription worthwhile. Historical Flights is really what keeps me subscribed - loading earlier daytime traffic at a European hub makes the whole environment feel alive during a late night session. For pure GA or VFR flying though, other injectors might fit better.

That ground traffic question from jcomm is interesting. From what I have seen, FSHud does influence ground movement when the traffic add-on is active. When I set specific runways as active, the taxi routes and holding positions change accordingly. It is not perfect - I still see the occasional odd behavior near the gate - but the overall ground flow feels more connected to the airport configuration than what I get from standalone traffic injectors. The sequencing on approach is where I notice the biggest improvement though. For my late evening sessions with historical traffic loaded, the arrival patterns look pretty close to what you would expect during the busier period.

The 180 turn issue is a fair point. For my IFR flying it matters less because I'm usually already climbing out by the time surrounding traffic starts doing anything interesting, and the ground phase isn't where my session lives or dies. The reason I keep the subscription is the historical data - loading a busier time of day makes the whole airport environment feel alive during my late evening sessions, and that trade-off is worth more to me than polished pushback behavior. Would be nice to see that side improved eventually though.

Thanks for the replies! Interesting to see most of you are running FSHud without the subscription. For me the historical flights feature is what keeps me subscribed. Since most of my flying happens late evening, loading earlier traffic makes a real difference in how alive the airport feels. I still use AIG for model quality, but the traffic patterns from FSHud Traffic feel more realistic for offline sessions. Curious if anyone here has actually tried the historical option?

Hey simmers, who is using Fshud Traffic? Screenshot I think I will keep subsription! EU Airport approved😎 What about you?

Nice one, thanks for doing a separate 2024 build. Smaller regional fields like this are exactly where the sim benefits from handcrafted scenery, especially if the runway slope and local character come through. Added to my list for a California hop.

I don't really see flight model updates as a bad sign by themselves. For me it is more about whether the developer keeps listening and whether the aircraft moves in a sensible direction after release. A business jet with a realistic and a slightly more forgiving option also doesn't sound unreasonable, as long as it is clear which one you are flying.

If searching HEADING still does not show it, try BUG or INC/DEC as the search term, with the filter set to all commands. The useful binding is usually the bug increment/decrement pair, not a plain HDG control. I would assign those two generic commands first and test them in one simple default aircraft before spending time on anything Wingflex-specific.

Try searching for the autopilot heading bug commands rather than just HDG. In the MSFS control list they are usually something like Heading Bug Increase and Heading Bug Decrease, or sometimes only show up if you search for increase/decrease rather than heading. Also make sure you are not filtering by an aircraft-specific section only. I would bind the left/right knob turns to the generic autopilot heading bug increase/decrease commands first, then test it in a simple default aircraft before chasing per-aircraft bindings.

That sounds more like a power or driver reset than a normal MSFS problem to me. If the whole PC is rebooting, I would check Windows Event Viewer after it happens and see whether it is only Kernel-Power 41, or if there is a WHEA, USB, or controller error just before it. The USB power-saving angle is worth trying, but I would also disable sleep and USB selective suspend temporarily and test with the headset idle on the desk, without MSFS running. If it still reboots there, you have narrowed it to Pimax, USB, or power management instead of the sim.

I'd separate the two problems a bit. FSRealistic is more about camera and cabin effects around the aircraft, while RealTurb is aimed more at air movement and weather effects. If the thing bothering you is the sim feeling too smooth or too jerky between Medium and Realistic, I would start with the turbulence/weather side first and keep FSRealistic as a separate decision. For light GA like the Comanche or Bonanza, I also find the built-in turbulence setting can be a bit of a blunt instrument. One extra add-on doing the specific job you want is usually better than stacking two effects and then trying to work out which one caused what.

That more or less answers what I was wondering about earlier. If people are getting stable approaches in calm weather, then I would be careful about judging the whole flight model from one gusty or review flight. The go-around report sounds like a separate thing though. If it rolls hard with the autopilot still connected, that feels like something worth reporting with a simple repeatable setup, because that is different from a small pitch change when disconnecting on final.

That approach behaviour is the bit I'd want to pin down before judging it too harshly. For those seeing the nose-down change or the +/-10 kt swings on final, was that with live weather/gusts active, or also in a calm preset? MSFS can make swept-wing aircraft feel very twitchy in gusts, so it would be useful to separate a sim/weather issue from an aircraft trim or autopilot disconnect issue.

I would first check whether GSX itself is closing, or whether it is still running but not detecting the arrival airport properly. After takeoff, try opening the GSX menu once and see if it is still responsive. Then on arrival, before parking, try restarting Couatl from the GSX/FSDT menu and see if the marshallers come back. If that brings it back, at least you know it is more of a Couatl/session issue than a PMDG profile issue. I use GSX with the PMDG too and it normally stays available after landing, so if it happens every flight after a reinstall I would grab the Couatl log and post it on the FSDT support forum or Discord. That sounds more specific than a normal setting toggle.