pijnackerpilot

Description: I have encountered persistent crashes in Microsoft Flight Simulator 2024 (MSFS 2024) while flying, with the application consistently failing and crashing due to issues with the WTF.dll module. The crashes occur intermittently during the flight, specifically either during the flight loading process or during the cruise phase of the flight. This issue started about a week ago after I installed version 1.0.8 of the inibuilds A350. Additionally, I have encountered several bugs after recovering a flight via autosave, including: Inability to activate ALT CRZ mode in the FMA. During Open Descent or Climb, the aircraft busts through the set altitude and does not follow the altitude constraints, unless manual level off is used. ALT CRZ mode remains blue in the FMA and does not engage properly. Crash Details: Faulting application: FlightSimulator2024.exe Version: 1.3.23.0 Faulting module: WTF.dll Exception code: 0x80000003 (breakpoint) Fault offset: 0x00000000000023cb Faulting process ID: 0x1050 Crash occurs during: Flight loading or cruise phase. Log Entries: First crash: Occurred at 16:48 UTC, with the WTF.dll error, while trying to load or during cruise. Second crash: Another instance at approximately the same time, with the same error related to WTF.dll. Steps Taken So Far: Reinstalled GPU drivers: I updated my graphics drivers (NVIDIA drivers) to the latest version, but the issue persisted. Checked for Mods: No new mods or add-ons were added recently to the community folder, and all add-ons were disabled to test the issue. WTF.dll found at C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\WTF.dll. Problem began: The issue began after installing version 1.0.8 of the inibuilds A350 addon. Bugs after autosave recovery: ALT CRZ mode in the FMA cannot be activated. During Open Descent or Climb, the aircraft busts through the set altitude unless using manual level off. ALT CRZ mode remains blue and does not engage properly. Observations: The crashes do not occur during landing or approach, but only during the flight load process or while cruising. The issue seems to be related to the WTF.dll file, as indicated by the crash logs. The application repeatedly crashes with the same error in WTF.dll, even after troubleshooting steps. The FMA bugs (unable to activate ALT CRZ, altitude busts during open descent/climb, and ALT CRZ staying blue) only appear after recovering from an autosave. System Information: OS: Windows 11 GPU: RTX3080 MSFS Version: 2024 - 1.3.23.0 Driver version: Latest NVIDIA driver Request: I am requesting assistance with troubleshooting or a possible fix for this issue. Has anyone else experienced similar issues with the WTF.dll file in MSFS 2024, particularly after installing version 1.0.8 of the inibuilds A350? Additionally, has anyone encountered the bugs related to ALT CRZ mode and autosave recovery? Any advice or solutions would be greatly appreciated.

I can confirm this issue. I experience it too. Despite having enabled L-CRTL and the amber keyboard input appears on the screen, I cannot enter text

That might be the case. GSX was acting up the whole ground time prior to take off. What is recommended regarding proper use of the OIC 'loadsheet' page in conjunction with GSX integration? In what order do things need to be done to do it properly?

Hello all, Today I did a Qatar flight from Islamabad (OPIS) to Doha (OTHH) in the A35K. I set up simbrief to take along a block fuel of 33000 which is plenty for this flight. As per OP, I loaded the fuel and payload via the load sheet. All as indicated on the OFP, generated by simbrief using the A35K profile provided by simbrief. After loading the Fuel and Load page (screenshot taken after being airborne for one hour), I already noticed that the required fuel enroute burn was significantly lower than stated below. The route includes a step climb to FL400 at TAPDO over the Persian Gulf about 2/3 into the flight. After take of I got a master caution and an ecam memo that states Fuel Weight data disagree. I followed the steps on the ECAM but all checks out. I don't know where this message is coming from. All checks out during the flight. Fuel consumption is according to the flight plan and I didn't have any fuel leaks What is causing this error and why does it still impact landing performance even if all is good. Additonally, on the STS page it states that BTV and autoland are now inop. Why? I hope someone can help me out here on what is going on. Thanks in advance.

Hi all, I have encountered a bug in the A350-1000 with regards to the navigraph data token within the OIS/ANF function. In preparation of a flight earlier today from OTHH to VABB I was prepping the flight charts within the OIS. Without issues I was able to create clips by pinning charts and I have no problems accessing the charts. When I access the ANF function though it indicates that airport nav data is unavailable. When I look at the 3rd party option screen to remedy the situation I see a QR code prompting me to link my Navigraph account again which, after scanning the code, does not work. Despite this I can still access all charts within the OIS. Even switching nav data does nothing. I cannot reset my credentials as that option is not present. Any pointers to what I can do to resolve the issue?

I was flying my first flight with this aircraft in MSFS2020. While I was setting up for the approach, my screens completely froze and the controls did not respond to input. As briefed, I checked the debug console and I have included report below. Here some flight details A359 QTR1170 from OTHH to OERK MSFS2020 NAVIGRAPH data NO WASM error found, but some sim var error every few miliseconds I9 9900K GTX3080 32 GB RAM To reproduce I was manually altering the flight plan by removing several waypoints by hovering over with the mouse, right clicking the waypoint, then selecting delete. I encoutered a double entry of two waypoints so I opted to delete them. The first one I managed, but the second caused the crash without my being able to confirm the temporary input