A350 update v1.0.2

[PJackes]

Hello, I just downloaded the new update for the a350 hoping this would fixes all the crashes I've been encountering since the launch. I sadly haven't been able to complete a single of my last 6 flight due to freezes. So hoping this update would fix my problems I eagerly jumped into the sim to do a quick test flight only to find myself disappointed again. This time I encountered a new bug I had not have before. During preflight preparation my camera got stuck. I couldn't move anywhere, the panels were all still working and clickable but my camera wouldn't move, I noticed as well that my inputs on my thrustmaster TCA had no reaction from the Sim as well. I could still switch to the exterior camera with the built in (msfs2020) camera panel but couldn't move that one as well. It's really a shame to have put on the market such a miserable product and especially for this prize.

[SkyKing33]

I got thee jitters which I NEVER had with the previous versions in 2024. Completely unacceptable

[HBZUG]

Today I made my first flight with the new version v1.0.2 (MSFS 2020), prematurely delivering the first SWISS A350 from LFBO to LSZH. This flight went absolutely uneventful, completely under managed mode. I’m convinced that this airplane is going to be fantastic after initial problems have been resolved by the  development team. I’d also like to mention that introducing the HB-IFA iivery parallel to the SWISS announcement was a very nice surprise!

I must say that most of my previous A350 flights since the introduction of this airplane were very frustrating, always due to problems with the autopilot system and managed flight, which sometimes resulted completely unusable. Even so, I always managed to get the airplane to destination in one piece …

I don’t know if this success is due to the new version or has other reasons (like I did never switch to an external view during this flight, except to silence the still unnerving AP off alarm). Also other possible causes like liveries are discussed in the forum (the only uneventful flight before this one was with a non-iniBuilds ITA livery (which by the way did overwrite the A350-900 entry in my MSFS Airplane selection menue).

Thanks to the team, I’m convinced that you will get it right!

 

[LineDX]

Same. Getting freezing and jitters after update 

[SkyKing33]

Same. Here is video of what just happened to me. The only way I've been able to complete a flight is to turn NVIDIA DLSS Frame Generation off but then I get far fewer frames in the A350 than I did in the previous version. 

 

[Pianoman]

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.

 

 

   

 

 

 

 

     

 

  

 

   

Edited Sunday at 05:02 PM by Pianoman