AlwaysZzzz

Quick update on my CTD situation: After posting my original cry for help, I kept tinkering with fixes - and guess what? Something finally seems to be working! Important background: Ever since buying the A350, I'd only been flying routes involving RCTP using ACO's RCTP scenery. During one flight, right after parking at RCTP, shutting down engines, and switching to external view - BAM! CTD with WTF.dll error. That got me thinking back on previous crashes. Turns out most WTF.dll crashes happened near RCTP! So I uninstalled the RCTP scenery completely. Next flight? Successfully prepared at RCTP and took off without issues. BUT! During cruise, I switched to a fixed cabin view for a long stretch. When I returned to the cockpit and adjusted instrument brightness... BAM! Another CTD - this time blaming RenoirCore.WindowsDesktop.dll. Googled that error and found this thread: https://steamcommunity.com/app/1250410/discussions/0/2845669419714540064/ Someone described exactly what I'd just experienced! Tried his fix: Set instrument refresh rate to HIGH Cranked up OIS refresh rate to 60Hz And... IT WORKED! Completed a full 6-hour roundtrip RCTP⇄VTBS without a single crash. Huge relief! Looking back, these CTDs clearly had multiple causes. My earlier attempts likely chipped away at other crashes. Posting this hoping it helps fellow A350 pilots battling CTDs. Good luck out there!

Hi all, I'm experiencing frequent and random CTDs exclusively with the iniBuilds A350 (v1.1.2) in MSFS 2020, making it impossible to complete flights. Despite extensive troubleshooting, the issue persists. Crash Pattern: Occurs at any phase: cockpit preparation, approach, or even taxi after landing. Error modules vary: VCRUNTIME140.dll | nvwgf2umx.dll | WTF.dll | FlightSimulator.exe | ucrtbase.dll | RenoirCore.WindowsDesktop.dll | D3D12Core.dll Attempted Fixes (All Failed): Used sim default navigation data, reinstalled Navigraph apps + navdata, clean reinstall of A350 (removed WASM files & community folder remnants), rolled back NVIDIA driver to 566.36, deleted sceneryindex + other cache folders, ran sfc /scannow, tested with default white livery, ensured VC++ runtimes are updated. CTDs only happen with the A350. Other aircraft (including iniBuilds A300) operate flawlessly. System Specs: Laptop: RTX 4080 + i9-13980HX + 32GB RAM, Windows 11 24H2 (fully updated) Given the exhaustive steps I've taken, I'm seeking advanced diagnostic suggestions. Thank you for any novel ideas!

Yes, PROFILE mode is armed.

After updating to version 1.1.2, I notice that even though I insert the THR RED/ACCEL data in the FMS (with the ACCEL at 1500ft higher than RED), the thrust set to accelerate to 250kt upon it reaches the thrust reduction altitude after takeoff. This didn't happen in the previous version, the aircraft always kept the initial climb speed until it reached the acceleration altitude.