What a Disaster

[hipshot845]

This plane just goes from bad to worse a whole lot more readily than it flies from A to B.

I hadn't flown it for about the last 6 months because it was so bad. I thought some updates might have improved it but even now, if its not having a WASM crash it's flying in cruise with a crazyass bank on it 8000 feet below programmed cruise altitude and 50 knots below programmed speed with an uncommanded descent or autopilot switch-off about to happen at any moment.

Maybe i'll give it a try after the next 25 updates if they specifically state that these faults have been rectified but until then, I'm done with this stupid thing.

Richard

[leo5now]

Yeah, I gave up on it technically. I honestly cannot be bothered to test or fly it again, wasted way too much time to find causes for it. The same goes for the 340. I have no idea what's been causing it; it wasn't this bad in the previous versions. I heard it had to do something with the plane losing "connection" with the simulator. I'm still trying to figure out if this is a 'me' problem or another asobo issue.

[fukai]

Agreed

[dectenor2]

I prefer to try and keep my posts constructive rather than just criticism, but also feeling extremely frustrated.

Was doing a flight today and nipped downstairs for 30 mins, when I came back the aircraft was completely off the route, still flying but nothing functioning in the flight deck, displays frozen, none of the FCU dials able to move etc. Didn’t have the orange WASM screens but it was all frozen up but with the aircraft still flying.

How is this still happening when the aircraft has been out for so long and had so many updates??

 

And this is to ignore the problem of so many bugs and errors even when everything is working properly and it doesn’t freeze up.

One notices so many bugs on every flight it’s just really hard to comprehend how the aircraft ever gets through any testing, the basics just aren’t there.

Really disappointing.

I’ll be happy to test the aircraft after updates, but for now I can’t justify flying it when it freezes up like this, and even when it doesn’t is just jam packed full of bugs. 
 

It shouldn’t be the case that people even consider parking the aircraft after how much we have spent purchasing it.

[IniJamir]

44 minutes ago, dectenor2 said:

I prefer to try and keep my posts constructive rather than just criticism, but also feeling extremely frustrated.

Was doing a flight today and nipped downstairs for 30 mins, when I came back the aircraft was completely off the route, still flying but nothing functioning in the flight deck, displays frozen, none of the FCU dials able to move etc. Didn’t have the orange WASM screens but it was all frozen up but with the aircraft still flying.

How is this still happening when the aircraft has been out for so long and had so many updates??

 

And this is to ignore the problem of so many bugs and errors even when everything is working properly and it doesn’t freeze up.

One notices so many bugs on every flight it’s just really hard to comprehend how the aircraft ever gets through any testing, the basics just aren’t there.

Really disappointing.

I’ll be happy to test the aircraft after updates, but for now I can’t justify flying it when it freezes up like this, and even when it doesn’t is just jam packed full of bugs. 
 

It shouldn’t be the case that people even consider parking the aircraft after how much we have spent purchasing it.

Hello, this is a known issue that we are still actively investigating, I've only had it happen to myself once and that was in the last version of A340 when VIP had come out. It behaves in the same way as WASM, however it doesn't throw the errors as demonstrated when WASM does crash with the Orange Screens which were added in it's own in SU4.

An update is already in works for A350 which includes fixes regarding WASM crashes, but these are tricky crashes and any aircraft can experience issues with WASM, this isn't to deflect the issue, we do work on them as with the most recent STAR/APP/RWY Change WASM Crashes; which in our internal testing where he had reproduced reported issues, applied fixes, and then could no longer repro them. Thank you for understanding