Pianoman

I had a CTD with the v 1..0.3 the update on my first attempt to fly. I did the full uninstall etc and just before the flight spawned using a BA livery ay Heathrow the Sim crashed with a message saying I had exceeded the memory usage as per the inibuilds new update fix. I normally use Navigraph, GSX and FSTL and had not selected them yet. However, I changed my aircraft to a Virgin livery and selected Gatwick instead and am pleased to say that I just did a 7hrs 5mins EGKK TO KJFK flight without any problems whatsoever. The aircraft even descended when I pressed the altitude button at the TOD. It is the first time the aircraft has worked perfectly for me.

The short term answer for those of you with a back up of the MSFS community folder is to replace the version 1.0.2 with version 1.0.1 from your backup. Copy and paste the inibuilds-aircraft-a350 file and overwrite when asked. This worked for me. I just did a 3 hrs 20 mins flight. Prior to that. reinstalling and deleting the WASM folder contents made no difference at all.

Same here, my aircraft screens, autopilot buttons and throttles freeze after about 30 minutes whilst the aircraft is still moving over the ground and the moving map screens still work. Version 1.0.2 has broken the A350

Sorry Guys. For me the A350 is broken with the v1.0.2 update. Previously, the aircraft worked fine for me. I have done numerous 4 hours flights with only one fault and that is the aircraft would not descend when you you push the descent button at the TOD. I have to disengage the AP then re engage after descending approx. 2000 feet. This has been reported elsewhere. I have tried to do two flights since the new version v1.0.2 update and the most of the aircraft display screens freeze after about 30 minutes even whilst the aircraft is still moving. The moving map screens work as do the map switching buttons but all the buttons on the top of the consul freeze as well. The throttles freeze as well. The aircraft is now U/S and unusable. I have a capable system and I use MSFS 2020 at max settings and still get more than 60fps with the A350. My system is a new Windows 11 pro purposely professionally built CHILLBLAST flightsim PC, with A Ryzen 7 7800X3D processor, 32 GB ram, Nvidia GTX 4070Ti and the sim is installed on its own 2tb SSD. It is more than capable of running the A350. I have done a complete reinstall of the aircraft plus I cleaned out the wasm folder etc. Doesn`t make any difference. Its the 'fix' that broke the aircraft for me I am going to try to reinstall version 1.0.1 from a backup UTFN. Update to the above. By replacing my v1.0.2 file with the v 1.0.1 file from my Back of the MSFS community folder, With the exception to the TOD button problem, I just did a 3 hrs 20 mins flight. This is the temporary solution until v 1.0.3. comes out.