TuomasV

My advice is not to mechanically just execute a standard maneuveur to idle and flare at certain altitudes - though as a rule of thumb they're good advice. But both decisions depend on your vertical speed, airspeed, weight of the plane and wind conditions. Something that an IRL A350 pilot taught me: Start the flare a tad earlier but start it with an almost imperceptible pull at first - then increase gradually if needed. Many slams and floaters happen because the pilot has a standard "always jerk back at altitude x" which will end up being too little or too much. Also, trying to follow the FD / glidepath too far down when already visual tends to mess the hand flying. When you see the PAPI lights, go visual and stay there. I spent some time doing visual pattern touch and go's with the Fenix back in the day with just the birdy on PFD, and that greatly helped my landings!

LSGG - Geneva is my hub though I live nowhere near IRL. Great payware scenery, 4km runway, scenic and intuititive Alpine approaches and 7000nm puts pretty much everything in reach except Australia and New Zealand. 778 gets you further than that, but the real beauty is there's something different in every direction you go.

Lot of good points already given! I go to idle at 30 feet, but from that point onwards instead of trying to just execute a standard manouvre, it is important to fly the plane based on how heavy the plane is, what kind of descent rate one has at that point and how gusty or windy the weather is. These all affect what kind of pull is needed. Also, for safe operation it is more critical to get the plane consistently and firmly down between the 1000-1500ft markings than try to buttersmooth it beyond that. In wet weather even more so as too light a touchdown risks aquaplaning.

Could you also post a photo in the Airbus where your FCU is visible?

Have had this happen three times in the past 6 months. Last time, it wasn't even solved by reloading the sim, but loading the sim with another plane and then again with Fenix solved the issue.

That is annoying! Works fine here and I actually get better performance there in 2024. Is it the same every flight there? I wonder if GSX, Photogrammetry or traffic on the ground could have something do with it.

I fly Fenix almost predominantly. Thought it'll take longer to make the transition, but I have much smoother performance and especially atmospheric colours are significantly improved, so now haven't opened 2020 in 3 months and couldn't go back. I've never used PG. SPAD.nxt, SimHaptic, FsRealistic, BATC with AIG - these didn't even notice the sim had changed after updating them. Most sceneries have worked just by dropping the folder from 2020 folder to 2024 one, which at first was a surprise as the scenery providers don't yet say there is compatibility or sell the sceneries for 2024.

Was about to say the same! Some of the trees in the real life clip are way too tall, and the haze is overdone as well.

This here is the reason. That's 22,000 terabytes. I always wonder what people mean when they say "SSDs" and hardrives are cheap. They seem to underestimate how much textures and mesh data and whatnot is needed to deliver scenery for the entire world. Even if you only wanted one region, it would still be a massive amount of data. For just the aircraft and airports, there is probably a case for more offline elements. but that won't really change the big picture of streaming. Delivering a potato for offline flying would be easy to do, but I don't think that's what people are after when they demand an offline version.

Here MSFS 2020 keeps loading as it always has....I can only wish it loaded as rapidly as 2024 does. I was one of the seemingly lucky ones to have 2024 up and running immediately on Day 2 with no loading or server issues witnessed.

Sayintentions for immersion. Not the cheapest but difficult to go back. Trying the 24h demo is worth a shot.

This happened to me once when my FMC PROG page had a higher planned flflight level than the one I ended up using. The plane was thus still in climb mode and didn't start a descent until I changed the PROG FL.