willwest43

On top of this, engine 2 appears to fail upon takeoff. Once restarted, engine performs as designed. Happened after flap retraction. But I do not think that is related. It happened during a previous departure as well prior to flaps being retracted. https://medal.tv/games/microsoft-flight-simulator-2024/clips/mqmKPqrcm9j28gtUy?invite=cr-MSwxU1ksMTkzNzg2ODc5

Upon further testing, it's the throttle 3 axis that is causing the eng 1 to shut down. No idea why. I went through all my axis and buttons on my Bravo to confirm nothing was tied to fuel and that the correct profile was selected (same profile I use for the TFDi MD-11) and nothing was conflicting. https://medal.tv/games/microsoft-flight-simulator-2024/clips/mqkodk9LZqQ6JILY5?invite=cr-MSxpalgsMTkzNzg2ODc5

As the title suggests, engine 1 rolls back upon engine spool up. I was able to taxi under idle power, but as soon as I spooled up to get onto the runway, engine 1 shut down. I was able to restart it, but even with the slightest amount of throttle, the engine still shutdown. This could be user error, but I was following along with a tutorial video as well as using the Autocomplete feature. https://medal.tv/games/microsoft-flight-simulator-2024/clips/mqjWJ4wW3zWpgDfoY?invite=cr-MSxYTlAsMTkzNzg2ODc5

As the title suggests, I am getting several TCAS warnings for aircraft that are no where near my position. During my climb out of Zurich, I was getting constant TCAS alerts to the point where I just turned my transponder off. https://medal.tv/games/microsoft-flight-simulator-2024/clips/lRzlxMsb0gy72sYP6?invite=cr-MSx2SEUsMTkzNzg2ODc5&v=135

Forgive my possible ignorance, as I am not a type rated A350 pilot lol, but I am a real pilot. So why would the Vspeeds increase with flap speed increase at TOGA thrust? In the screenshots, you can see the takeoff speeds increasing with a higher flap setting. All the configs are the same, PACKS off, Anti-Ice off, TOGA thrust (That was automatically generated as I was about 10 tons below MTOW). Same runway at Toronto CYYZ, Runway 23. https://imgur.com/a/mIQepJh

Everything froze up when I entered a hold at DARKE going into Katmandu. The aircraft didn't enter it in so I did it manually as per the chart and it quickly froze everything. I was able to control the aircraft, but didn't have any control on speed or anything. Flight control animations, landing gear, flaps and spoilers didn't work.

As the title suggests, the right toe brake does not work at all. The animation works, but the brake itself does not. I tried changing bindings and axis but still didn't work. Tried the default A321NEO and both brakes work, so I can conclude that this is a bug in the actual aircraft itself.

First off, I am loving the default 330 and 21LR. Theyre the only reason I am using 2024 right now lol. I noticed that when I set FLEX, the ECAM gives me a warning saying that FLX is not set. But on the FMA, it does say MAN FLX and does not give me a warning that there is a problem. And on the engine display, it does not indicate a problem, as well as the actual takeoff setting is more or less the same. I have calibrated my throttles and have a custom Airbus throttle kit for my Honeycomb Bravo. The 330 I've noticed this too. I'll jiggle my throttles in the detent, but the warning doesn't go away. https://gyazo.com/6969c905bc59bded73339ba3a68947e4

Since this aircraft has the option to have APU failure due to lack of oil or something, I feel it should be appropriate to incorporate an ASU so you can still start the engines while on stand and continue your flight with an INOP APU. Unless nothing happens when you run out of oil with the APU lol. I haven't gotten that far yet.

Sorry for the late reply. Yes, switching off the DH on the captain's side solved the speed problem. Looking forward to the upcoming fix 🙂

You are probably right. I saw a Facebook post this morning about the same thing and someone mentioned that the Captain's DH will cause an issue with selecting speed.

I was just flying into Memphis when everything went all wrong. The autopilot refused to reduce speed and I couldn't change it manually resulting in a go-around (too close to the runway to salvage the approach). Second attempt, the LAND mode did not engage even though G/S and LOC were blue and the aircraft lazily drifted off the NAV track even when in NAV mode, a second go-around. During the second go-around, the thrust did not reduce and remained at TOGA power even when I leveled off at the miss approach altitude sending my speed nearly through Vne. At this point I just took manual control of the thrust. Third time the charm! This time, I was able to land after doing an extended 22-mile final. during the downwind, I played around with the autopilot, but it flat-out refused to cooperate and did not give me any sort of manual control over the speed so I just disconnected it altogether. This was all done in IMC at night. Flying V 1.0.3

Interesting. My thrust rolled back at LEZL Seville Airport which, coincidentally, is also made by MK-Studios. However, I don't recall having any bumps that put me airborne. The thrust rolled back as I was already in the air, just before gear retraction.

15/15. I did have a gear up warning though on my most previous flight out of Lutton when I was at 15/20. Maybe the gear up warning is a big with that because the plane thinks it's landing. I'm going to try 15/20 again but set the landing config switch to 15/20 and see what happens.

Departing Seville, as I was about 100 feet off the ground when the autothrottle disconnected and the thrust began to rapidly roll back to idle without command. My physical thrust levers were at full thrust and the TOGA button had been pushed to initiate the takeoff, but the in-game thrust kept rolling back. It stopped at 60% N1 before I giggled my throttles and it went back up to TOGA thrust. My A/T disconnect hotkey is on my joystick, but I'd have to take my hand completely off my joystick to push the button. There are no hotkeys on my throttle for A/T disconnect either (honeycomb bravo). Just TOGA, but I did not press.