solved A340 WASM Crash (Red Screens) on Runway Spawn

[rerem2]

hello :)

When I enter the flight plan and try to add the AMKEN waypoint, everything turns red.

 

 

 

[iniSteven]

Hi, could you provide the full flightplan you tried to enter? And is this repeatable or it just happened once? Were you on Navigraph or Sim Default navdata?

-Steven

[rerem2]

Actually, the AMKEN waypoint was considered nonexistent.

I tested with PPPPP (you know, to enter a custom waypoint), and the next page works fine, but when you click the back button, everything turns red and the whole system locks up.

I don’t know why the AMKEN waypoint was treated as a custom point.

But there’s a major bug and it’s 100% reproducible.

[rerem2]

 

[iniSteven]

1 hour ago, rerem2 said:

Actually, the AMKEN waypoint was considered nonexistent.

I tested with PPPPP (you know, to enter a custom waypoint), and the next page works fine, but when you click the back button, everything turns red and the whole system locks up.

I don’t know why the AMKEN waypoint was treated as a custom point.

But there’s a major bug and it’s 100% reproducible.

Thanks Rerem, I've found the issue. If you're on the NEW WAYPOINT page and press LSK R5 the key BELOW return, it crashes. I've passed it on to the team.

[Tiago2]

It also happened to me with the pmdg 777F and inibuilds A340

[khakans]

On 12/3/2025 at 3:16 AM, iniSteven said:

Hi, could you provide the full flightplan you tried to enter? And is this repeatable or it just happened once? Were you on Navigraph or Sim Default navdata?

-Steven

I've been experiencing this issue for a few days. The latest one just happened on my EDDH-LTFM flight. It happened while trying to change the LTFM approach procedure from the MCDU during the flight. I'm using the Sim Default navdata.

Route: EDDH/23 N0453F390 AMLU2B AMLUH M852 DENIX DCT ZUCKA DCT OMELO DCT ODLIV DCT MAVOR DCT UVERA DCT BIVBU DCT BUVAK DCT RIXEN RIXE2A LTFM/34L

 

Edited December 5, 2025 by khakans

[cpuwolf]

I found if I start A340 from ramp, there is no WASM crash, but If I start A340 from runway, it always crashes with reds

[wolfko]

Same here! After the SU4 update yesterday I am getting those red screens with WASM crash notofication, whenever I load the A340 at a runway. Also the landing gear is missing. When I start from a gate everything is fine.

Also autosave does not work. When loading an autosaved scenario, the captain's side window will open, no matter if midair or on the ground and the PFD screen goes blank.

Just for info: I have the A340 downloaded, not streamed. After having above issues yesterday I uninstalled the A340. The plane was then autonatically streamed and everything was fine. I then downloaded the plane again and it also worked for one time when starting on a runway. After then loading an autosaved scenario, all the issues were back.

 

Edited December 9, 2025 by wolfko

[Airbumps2501]

22 hours ago, cpuwolf said:

I found if I start A340 from ramp, there is no WASM crash, but If I start A340 from runway, it always crashes with reds

This has been reported a number of times during SU4Beta and discussed in various forums. The response from people during the beta was, predictably "its a Beta - expect issues". Unsurprisingly, its now a problem for everybody....

[Eddie]

Hello,

We're taking a closer look at this. Your patience in the mean time is very much appreciated! 

[Airbumps2501]

On 12/10/2025 at 8:54 PM, Eddie said:

Hello,

We're taking a closer look at this. Your patience in the mean time is very much appreciated! 

Hi Eddie,

 

Hows that closer look going? This is a pretty simple thing to replicate it would seem.

[papabear]

I get red screens when I spawn on the runway, but when I spawn on a parking positions "cold and dark", all works fine.

[richboy2307]

Hi all,

Red screens appear when a WASM crash happens. The WASM crash on the runway spawn is an issue that was introduced in SU4 and affects many WASM aircraft.

For the A340, there's a potential fix available in the v1.0.7 update. We recommend updating to the latest version and trying again.

If the issue occurs again, please submit a new post following the guide below. Make sure to include all the requested information, especially autosaves and OFP files if you have them. This information is essential for us to try to reproduce the crash and work towards a solution.

There is no one-size-fits-all solution to WASM crashes as its not a "singular" issue. Most WASM crashes are due to corruption in sim memory, and each is unique to its circumstances hence why all this additional information is required to re-create the conditions that may lead to this.

Thanks!