@Fragman444 Thanks for the input.
The purpose of my initial post on the subject was, in a nutshell, to evaluate how realistic it is to fly from TOD to final approach without intervening at all, and my conclusion is that no, it probably isn’t. But perhaps it shouldn’t be expected anyway: for example, the speed limits on STARs and final approach plates are -in general- upper limit speeds, which the MCDU has you fly at most of the time, and if you do, will make you arrive way way too fast. In reality, if you look at FlightRadar24, you will realise that planes MAY arrive much slower than the speed limits. The problem is that the MCDU doesn’t seem to be able to tell how much slower it should fly at in order to make the approach actually flyable on its own.
Thus my conclusion is that what the MCDU computes has limitations, which is fine, and not necessarily a surprise.
Of course, intervening the way you do it, which is how I have to do it too if I want to perform a somewhat realistic approach and landing, this will work. Of course.
I also would like to add, several people here are confused about semantic. There are 2 speed modes:
Managed mode: this is the speed that you see displayed in the MCDU and takes into account speed restrictions. When this mode is engaged, “_ _ _” will show on the FCU because you don’t control it (unless you go into the MCDU and force input your own speed restrictions).
Selected mode: this is when you pull the rotating speed knob on the FCU, and manually select the speed you intend to fly at. In this case, your target speed is whatever it is on the FCU and won’t be restricted (@Fragman444 and @RagingWombat839 , this is the mode you actually refer to in your posts).
Haha I was going to reply saying “I know why are you correcting me?” but I reread my earlier post and saw I’d written “managed” twice where I meant selected. (But curiously also got it right twice.) Brain must have been in neutral that day. Sorry for any confusion, I edited to fix my typos.
Recently I’ve been getting the following on landing:
-Retard at about 20 feet, touchdown.
-Activate thrust reversers and advance throttles to slow down to 80 knots, then back to idle. Maybe leave them in idle reverse until vacating runway.
-Retract flaps and speed brakes.
-At that point, I get red + audible warnings, “slats not in TO Config”. I have to hit CLR button multiple times as I taxi to gate (when throttling up). I also get the Takeoff Checklist display on the screen, plus other things that I forget but mean that the plane thinks I’m taking off.
Nothing has changed with my control mappings, but perhaps a recent update might be causing this?
Maybe I’ll try to video and post this later tonight if that’s helpful.
I’ve had somewhat a close experiences with both A73x and A32x too.
The 738 are specially “slipery” and hard to slow down. Sometimes you need to descend way earlier. Choose long aproaches when avaliabe or even fly outside the path to slow down or loose altitude.
With the A320/321 I usually don’t have problems with the finals. Most of the time I’m low and slow before the final. The only detail is descending early, like 40 miles and I always get it right.
For anyone using Fenix in 2024… Do you feel the ground physics have down graded compared to the latest build from November for 2020…?
I did not see anything regarding it in the known issues but wanted to see if anyone else felt this or my mind is playing tricks on me haha
When I say downgraded I mean no matter the load in the plane it seems it gets rolling and taxies very quick and to ‘twitchy’ feeling rather then the ‘heavy’ feel I felt in 2020 where you gotta give it some thrust and a few seconds for those engines to get the plane rolling…
Appreciate anyone’s input!
Thx. I toyed around with it this morning. I remapped my reverser from toggle to activate on press-and-hold (which I use on the 737 but not the FBW). Did the trick.
Finally making some headway getting the Fenix to work for me in 2024. Still working through a few issues but the most nagging right now is the EFB map (the Fenix EFB, not the one that comes in 2024). The Navigraph charts all display fine but the map itself (the one that shows general airways, aircraft position, etc is black. If I go to zoom in or out, it displays for a second or two and then goes back to a black screen. Any idea what the issue may be?
The Navigraph map flashes/flickers quite badly for me on the Fenix unless displaying a SID/STAR/APPROACH chart. I think it’s a bug needing a fix at this stage. Maybe with your system it manifests as being completely black. I’m using a 3090 with the latest NVidia GRD (566.36). It is still “experimental” in 2024.
I’ve not tried that many other aircraft to tell admittedly. I was wondering if it was a DX12 issue, but maybe it is just a FS2024 thing. I take it the Navigraph toolbar panel is ok? I haven’t been using it much in FS2024 since Navigraph is now available in the default EFB.
On my first 2024 A320 flight, I also had an issue mid-flight where I received two duct overheat warnings. I had shut off maintenance failures for this flight, just wanted to focus on the basics. Anyone else have maint failures when they disabled them in 2024?
I’m having this issue in FS2020 with all versions of the Fenix A320. On final approach right before the flare, my plane starts doing an uncontrollable sway, like its input related, but I’m not doing anything when it happens. If I dont fight it, the plane will roll left or right into the ground.
Seems to be more prominent in VR and only on approach. No weird behaviours on takeoff or at cruise.
TLDR - plane starts behaving erratically at about 500ft on final approach.
I’m slowly getting the 320 to the same condition it was in 2020 before I “upgraded” to 2024. 2nd flight went better than the first, but I still have a couple of issues. The Sim Brief flight plan loaded fine but for some reason, the passenger, cargo and fuel numbers didn’t. Also, I’m struggling with the detents on the throttle for take-off and climb thrust. They seem to be much more sensitive than what I had in 2020. Any suggestion on how to resolve these two?
Guys, is “dimming the cabin light” done automatically ?
I’m asking because one of the cabin announcements (the CabinDimTakeoff one) triggers based on, partly, cabin light being dimmed but in my case this announcement is coming too late so I’m wondering if I have to dim the cabin lights myself to trigger the announcement earlier.
It’s automatic. I was doing some night flights earlier this week and all of the cabin dimming and announcements were done automatically right after pushback. That was on 2020 so if you’re on 2024 I can’t confirm or deny if it works.
Thanks for the response. I think my issue is that the real life long cabin announcements I’m using (CX) are too long and all get sort of clogged when I reach the runway’s threshold. They add up to 10 minutes which isn’t what it takes me from push back to the threshold in general. May be I can chill a little more lol
I bought the A320 a few days ago and since then I learned that the build-in Airbus Optimal and REC MAX flight levels aren’t very accurate. In real-life, pilots apparently use the Flysmart+ app on an iPad to get the accurate flight levels.
Is there any way I can get the accurate OPT and REC MAX numbers without having to buy an iPad?