Systems

Aircraft: A350-900 Version: 1.2.3 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: Attached WASM Error: Not related Specs: 9800X3D, RX 9070 XT 16G, 64G RAM Autosave File: Not related As titled, I encountered 2 consistent premature rotation during takeoff roll. I did not record both flights but I have the aircraft loading available here. Takeoff performance calculated by the built-in tool. I can confirm that the load is correct and that no weight disagree message was shown. TOW: 194710kg ZFW: 173696kg 2026031501_VHHHRJFF_PDF_1773578058.6d60e72d.pdf

Hi, I initially was able to download the terrain database, the file was present in the WASM file, but nothing showed on the ND when Terrain was selected. So I deleted the file and tried to redownload it, initially a warning came up saying "download failed" and now for the last hour is simply said "downloading" Can anyone help solve this? Kind regards

I keep getting D-ATIS updates for my departure airport. I turned it on, but the option to turn it off is greyed out after clicking on it to cancel. Steps to recreate is to ask D-ATIS to keep updating for dep airport, in my case MMMX. Then turn it off after a while.

The plane now feels heavier in terms of FPS, with almost 15 more FPS consumption and stuttering since the last update.

Had today directly after update the A350 for MSFS 2024 two D3D12Core.dll CTDs. Never had this before......

I presume the RA callout logic on touchdown could be related to retard logic, if it isn't then my bad, however if it is the logic is still the same as it originally has been for quite a while and is not added. Retard does not abruptly cut off as soon as the thrust is set to idle in cockpit videos this doesn't seem to happen, Airbus A350 - Full Approach and Landing in Boston (ENG subtitles) in this video PF idles it and the computer calls it out twice however it does not cut off. The Flight Computer will call retard (only once) even if the thrust is set to idle before the callout as well.

Hi, My plane rolls to the right throughout the entire flight. It's really disconcerting.

HI there, I deleted the WASM and reinstall the whole A350, now it can fly stably, but then the HUD, "Normal" and "X-wind" switch did absolutely nothing to it... any idea?

Since update 1.2.3 and 1.2.4 the "Company MSG" displays on the ECAM. Is this a bug or can I get rid of it somehow?

I have updated to the latest 1.24 version, but the VNAV issue still persists. When I lowered the altitude to below 21,000 feet, the T/D indicator disappeared and the aircraft prematurely entered the DES mode.I conducted tests using the autosave file created in version 1.23. Subsequently, I will test with the file created under version 1.24. It can be said that this issue might still not have been resolved at present.

Long haul from Kuala Lumpur - 2 hours in and this is the UTC data. What’s going on? If I re-insert the landing airport (EGCC) and STAR then, for a short while, the UTC info corrects, but it goes rogue again quickly after. Why? On Xbox.

Hello, I just started a Flight based on my simbrief planning I used for all flights before last update. I‘m underway with 190to ZFW and remaining fuel of 55to. I‘m flying on FL350 and the fuel consumtion is between 7.5 and 8 to/h. It should be 5.8 - 6.2to/h. I have a tailwind of abouut 50kn. Something changed after last Update. 7to Plus is never correct for -900. any thoughts/ideas? BR Andreas

Hi team @iniBuilds I did a couple of test flights on the V1. 2.3. In the new update VNAV has some serious issue. About 25-50 miles or so before TOD on dialing the cdu alt to about 3000 feet, the TOD disappears from the ND as well as from the OFP on the FMS without pressing the ALT knob button(activating the Des). This is a serious VNAV issue requiring an immediate hotfix to make the plans fly able. Regards

Hey, both of my engines failed at the same time because of the hydraulics failure, not sure it was a bug or something, but it is kinda suspicious. Check please the time 18:44 when it began (this is a raw video, sorry about that)

When in ARC mode on the nav display selecting any other mode (PLAN, NAV, VOR or LS) the range selector increases one level by itself. For example, starting with with 40 NM set on the range selector knob and the ND set to ARK. Set the ND to NAV and the range knob will move to 80 NM. This happens in both the left and right seat. The opposite is also true. When in any mode that is not ARC, the range will be decreased by one level when selecting ARC on the ND.

How to input a holding at present position? Thank you.

Currently 10 hours in to EGLL-WSSS and have noticed a couple of things since the latest update. Upon departure, the PERF page would instantly switch to DES phase with no way of forcing the FL to reinstate the CLB phase. I was not able to fly the managed ascent of the SID. Once cleared for cruise altitude, the CLB phase would initiate after selecting 20000 or above. Whilst in CRZ, selecting an altitude below 20000 would initiate the DES page, without actually selecting to descend. Secondly, "Cabin ready" appears permanently. No way of clearing. As said, minor issues and not something i've encountered in previous versions.

I was vectoring to the final approach course for the ILS on 26R at EDDM. I selected direct and CRS IN to the fix outside the final approach fix. The FMA showed HDG in green and NAV in blue. The ND showed a solid green line on the inbound course between the fix and the intercept point and a solid green line from my plane symbol to the intercept point with a green circle at the intercept point. I was approaching the final approach course 30 degrees off of the inbound course. When the plane reached the intercept point circle the inbound course line turned to a dashed line and the plane continued on the original heading. I selected a heading back to intercept the inbound cour…

Hi guys, @iniBuilds since last few updates the jepp charts(Navigraph) don't get unpin when press the unpin button next the chart tile. Instead you have press unipin next to the tile and then press the pin/unpin button at the bottom (next to chart types) to make the chart tile disappear. It used to work great in the initial builds. Please fix this.

Whenever I apply roll input in flight (for example during a normal bank), the roll spoilers deploy as expected, but the animation is not smooth. Instead of moving cleanly and holding position, they rapidly jitter / chatter back and forth while extended. Aircraft rolls normally flight model seems fine It’s the spoiler animation itself that looks unstable. I’ve checked all my control bindings no duplicate roll or spoiler axes. Using Thrustmaster Airbus sidestick and Honeycomb Bravo Happens and it happens regardless of DLSS, Frame Gen, or graphics settings. IMG_3893.MOV

The external lights have not been working for me for about a month now v1.2.3. In the video I the batteries on along with the gpu connected and all the lights set to the on position and they just dont work 😞 Microsoft Flight Simulator 2024 2026-03-13 14-12-01.mp4

Hello, developers, I hope it will be helpful for you from me just to sent logs from a clean install of A350 (as for 13. 3. 2026, the new version). There are some issues, a bit flicker of displays and a lot of errors and warnings from the dev console. I hope it is helpful. So far I loaded and compiled WASM. One thing is solved for me -- the plane automaticaly no longe crashes to a building during waiting for yellow "FLY" button 🙂 It's moving a bit, but it stops immediately. Files: Video [mkv]: Flickering displays Log01: What errors it wrote when selected from menu (nothing else, just selected) Log02: Separated Errors/Warnings/Messages. My HW: AMD 795…

Yea, after a while I tried A350 again, my flight from KOCD to WSSS was great, so I tried WSSS to LKPR and it crashed over himalayas, aircraft flew normally straight in line, but nothing repond, no butons, nothing. Waste of time.

Small bug: When crossing the International Date Line, the route depiction on the Enroute page in the EFB disappears. It also affects the Day/Night map selection. No effect on the flight.

Hi Team, Regarding the current behaviour of elevator trim after landing/rollout is that it will automatically set to a value that will enable based on THS. Based on observation IRL, the elevator trim should be set to neutral (I believe 4 degrees up). Can this be looked into and whether this logic needs to be corrected. Thanks, Wisam