Kevin B Posted Sunday at 06:07 AM Posted Sunday at 06:07 AM Hello, honestly inibuilds I'm fed up! I had to fly the 350 every day for two weeks between the beginning of March and March 20, a few MCDU freezes but it was rare. I'm back since March 20 yesterday so 04/26/25, A real disaster! A round trip Paris CDG Chicago. The MCDU froze on approach to Chicago, the plane did not climb as planned even though everything is set up correctly. With each update I delete the entire 350, WASM and everything related to the 350 for a clean installation. On the outbound flight I had to restart the flight 3 times on approach as soon as I touch the MCDU it freezes. I'm doing the return flight, having uninstalled it again. I'm already planning steps, for a final altitude FL400, I find it at FL444 .... Impossible to enter the approach and the runway at CDG because everything is grayed out with nothing to offer me. Navigraph is up to date. I decide to go back in manually. 4 times the MCDU freezes! I give up. Between the 350 that does anything and your 330 that resets in flight and also does anything. Inibuilds stop making planes and concentrate on the scene. I regret so much fenix who canceled their 350 ... It's shameful on your part that a plane like that is completely missed! We're more than fed up! Moreover, in 2 months you are already in 1.08! there is a problem! in 1 year we will still be at the same rendering in v1.84? 1
Der Michel Posted Sunday at 07:19 AM Posted Sunday at 07:19 AM Hi, have you tried this? Please report any WASM crash (freeze of avionics) according following, only then they can track and solve it: 1
Kevin B Posted Sunday at 07:35 AM Author Posted Sunday at 07:35 AM Hello, I did the first thing, but not the second.
haza2 Posted Sunday at 07:40 AM Posted Sunday at 07:40 AM 1 hour ago, Kevin B said: Hello, honestly inibuilds I'm fed up! I had to fly the 350 every day for two weeks between the beginning of March and March 20, a few MCDU freezes but it was rare. I'm back since March 20 yesterday so 04/26/25, A real disaster! A round trip Paris CDG Chicago. The MCDU froze on approach to Chicago, the plane did not climb as planned even though everything is set up correctly. With each update I delete the entire 350, WASM and everything related to the 350 for a clean installation. On the outbound flight I had to restart the flight 3 times on approach as soon as I touch the MCDU it freezes. I'm doing the return flight, having uninstalled it again. I'm already planning steps, for a final altitude FL400, I find it at FL444 .... Impossible to enter the approach and the runway at CDG because everything is grayed out with nothing to offer me. Navigraph is up to date. I decide to go back in manually. 4 times the MCDU freezes! I give up. Between the 350 that does anything and your 330 that resets in flight and also does anything. Inibuilds stop making planes and concentrate on the scene. I regret so much fenix who canceled their 350 ... It's shameful on your part that a plane like that is completely missed! We're more than fed up! Moreover, in 2 months you are already in 1.08! there is a problem! in 1 year we will still be at the same rendering in v1.84? Hello Kevin, firstly sorry to hear your having some issues with the A350, with such a complex aircraft there is always going to be bugs, unfortunately sometimes there is no quick fix to address all of these and some take longer than others. What I can say is that everyday all these bugs are being worked on and everyone is committed to making the aircraft as good as it can be. A lot of people are arnt having any issues and some are, yesterday over 260 A350s crossed the pond. What would help us is if you did a WASM report as described in the link above and please let us know any other feedback you have. Kindest. H
David Cherrie Posted Sunday at 08:04 AM Posted Sunday at 08:04 AM 17 minutes ago, haza2 said: A lot of people are arnt having any issues and some are, yesterday over 260 A350s crossed the pond. A lot more than 260 started but never reached their destinations. Looking at the statistics from VATSIM is indicating a huge widespread problem with A350. Hundreds of connections flying the A359/A35K quickly dropped connection in the first two hours then eventually being overtaken by the B77W. 1
Rainerb Posted Sunday at 09:51 AM Posted Sunday at 09:51 AM I tried the Version 1.08. but it was Not stable on my System, I Reporter this allready in another thread. Therefore i switched back to the Version 1.07. (recovered it from previous Backup). With this Version i took Part on the Cross of the pod yesterday without any issues. Hopefully the next Version is stable, until this i do my flights with the Older Version. 1
David Cherrie Posted Sunday at 12:58 PM Posted Sunday at 12:58 PM 3 hours ago, Rainerb said: I tried the Version 1.08. but it was Not stable on my System, I Reporter this allready in another thread. Therefore i switched back to the Version 1.07. (recovered it from previous Backup). With this Version i took Part on the Cross of the pod yesterday without any issues. Hopefully the next Version is stable, until this i do my flights with the Older Version. iniBuilds really needs to have the ability to rollback versions or pull their v1.0.8. I'm not going to update their aircraft anymore without taking a save of a working build. 1
Peter Posted yesterday at 01:20 AM Posted yesterday at 01:20 AM 15 hours ago, Rainerb said: I tried the Version 1.08. but it was Not stable on my System, I Reporter this allready in another thread. Therefore i switched back to the Version 1.07. (recovered it from previous Backup). With this Version i took Part on the Cross of the pod yesterday without any issues. Hopefully the next Version is stable, until this i do my flights with the Older Version. would you please send me 1.07? Or show us how to recover it? 1.08 is broken for me.
David Cherrie Posted yesterday at 02:07 AM Posted yesterday at 02:07 AM 46 minutes ago, Peter said: would you please send me 1.07? Or show us how to recover it? 1.08 is broken for me. Sharing files is software piracy… you can’t recover it unless you purposely saved it yourself. Going to have to wait till a new update. 1
Swisspilot1986 Posted 16 hours ago Posted 16 hours ago or wait on the 1.0.9. Eddie, at this end of week?
SUB750T Posted 14 hours ago Posted 14 hours ago (edited) Luckily 1.08 -1000 works perfect for me 6000 NM long hauls 14 hours flights perfect now after very harsh comments for the devs in the past. Make sure you use the none corrupted drivers from Nvidia 576.02 or later. Mainly this was my issue before... Edited 14 hours ago by SUB750T LG-48GQ900-B 48" AMD 9900X3D ASUS TUF Gaming X870-PLUS Wi-Fi AMD AM5 AORUS GeForce RTX™ 5080 XTREME WATERFORCE CORSAIR Vengeance DDR5 6000MHz CL30 AMD(2 x 32GB) 2X 2TB 970 EVO Gen 4 (FS 2024) 1X 1 TB 990 EVO Gen 5 (WIN 11) 3TB SSD (MOVIES/APP) Marantz HD-DAC1 Beyerdynamic T1 Tesla (2nd Gen) Thrustmeter TCA Captains Pack Thrustmeter TFRP Rudder MiniCockpit (miniFCU V2 + miniEFIS) WinWing MCDU FS2024 (AMD FSR3) X2 (90 FPS on ULTRA/HIGH @4K)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now