Jump to content

Recommended Posts

Posted (edited)

I've re-done the flight and I was able to replicate the issue.

I've selected the LAKL1T STAR in OOMS with ILS approach runway 08L via BUBIL

I've started the descent in V/L mode to be over BUBIL at 9000ft, just before BUBIL, reaching 10.000 ft I've applied the spoilers to reduce to 250knots.

This is the point, like the first flight where the freeze occurs (spoilers extended). systems, autopilot and FMS were completely unusable and unresponsive.

I hope this will help to finally solve this issue

1250410_20240906154344_1.png

Edited by FoRnA88
Posted

Just happened to me as well, on the latest version on the A300, using the PW engine variant.

I was on the ground at SDF, was in the process of putting in the departure which was EEVAA1 out of 35L. When i clicked on the button scroll down on the list of RWY's and SID's. The FMC went tits up and froze as well as the rest of the plane, EFB was the only thing working. I could hear the switches but nothing was happening. Gave it a few minutes incase it recovered but nothing.

Am also on Navigraph's 2409 version 1, scenery is FSDT Louisville.

Posted

It would be nice if Inibuilds can confirm or try to replicate the issue, the airplane is almost unflyable and that's a pity.

Posted

Hello everyone,

I've shared your reports with the team and we'll get back to you once we have more information to provide. Apologies for the inconvenience and we appreciate your patience! 

 

Thank you

  • Like 1

Eddie
Community Manager 
IniBuilds Ltd. | inibuilds.com

Posted

Yes the problem persists. Today I got the same freezing when I clicked on DES FORECAST on the MODE page.

I don't want to start a 6hr flight and end up like that, so I am kind of putting the A300 aside. I am not a programmer, but I am not sure what "WASM crash" means. Can it be restarted? Can you think of a workaround, like adding a button that reinitialises everything rather than having to abandon the flight?

  • Sad 1
Posted
18 hours ago, Mike Papa said:

Yes the problem persists. Today I got the same freezing when I clicked on DES FORECAST on the MODE page.

I don't want to start a 6hr flight and end up like that, so I am kind of putting the A300 aside. I am not a programmer, but I am not sure what "WASM crash" means. Can it be restarted? Can you think of a workaround, like adding a button that reinitialises everything rather than having to abandon the flight?

WASM is a code format used in MSFS for a number of planes. Unfortunately it turns the A300 into a plane that may be rendered unusable at any moment.

Posted

This issue, I believe, is not limited to only A300 in MFS2020, but to the A310 and A320Neo V2 as well. I would appreciate, if you could possibly look into this problem, because those are fine aircraft, but this renders them inoperable for the rest of the flight

  • Like 1
Posted

Indeed, this is the reason why I've never performed a full flight on the 320 Neo V2.

From my side i do confirm the impossibility to use the A300 and the A310, since this issue is present in each flight, and in case of my UAE-Oman Flag, i was able to reproduce it.

A pity, considering also the cost of the A300 and the level of details included in the plane.

  • Like 1
  • 2 weeks later...
Posted

First flight with the A300 after the AAU3 and I got the freeze right after landing just after disengaging reverse thrust. That was the first time I got a WASM crash without manipulating any systems - just the flight controls and throttles. This time I could not even control engines / flight controls any more. Until now it was only the instruments but you could still control the plane. 

  • 1 month later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...