geirrosset

Don't know what to say, that has not been said in the subject. After uninstalling and reinstalling the latest update I have frequent WASM crashes. They had all but gone away on 1.0.2. Now they are back worse than ever. Every other flight never even gets off the ground.

@iniKyle I was trying to be funny. Everything worked great once it was disabled. Noticeably smoother than that other free 380 on my RTX5080/9800X3D system in VR.

Why would I be running an unofficial app like that, let alone put it in my startup script so that I forget it is even there... Now if you'll excuse me I have to start my decent into Heathrow.

Tried again. Same flightplan. This time I stayed at 6000 feet well past the point when the error occurred the previous times and everything worked as it should. Smooth sailing. Then I set FL320 and started the climb. At around FL090 the cockpit glitched out. Again. Tried on the ground before takeoff. If I switch to external view, and then switch back to cockpit view, for just a few tenths of a second all the lights in all the buttons are lit. Then go back to normal. At FL090 this samer thing happens but without switching views and it stays like that.

Tried again. Quit MSFS, restarted in VR. Same flightplan. Took off from OMDB. Just below FL100 every button on the flight deck lights up. Some switches and knobs are floating in the air. EFB works as normal, all the screens seem normal. Flight continues and everything is ok in 2D.

Update for this. FYI I only fly in VR. Thought I might have got it right. Spawned in at a gate at you Dubai v1 (still can't see an update for this airport on the Marketplace). Started the flight. Got to FL100. Suddenly all the lights and switches lit up. Some were floating mid air. Unflyable obviously. 2D was unaffected. Quit the flight restarted at the same airport with the same flightplan. WASM crash after clicking Ready to fly.

Needing to do this begs the question: Why couldn't thin initial startup be scripted somehow? How many support questions and "angry" customers would you avoid by just scripting this procedure so that it can't go wrong. Eliminate the variables.

Downloaded. Deleted the WASM folder between each try. So when it says load on any runway you are not supposed to hit "Ready to fly"? Just let it sit there for X minutes and then exit to menu without clicking "Ready to fly"?

In the WASM folder I only get one folder (work) but no files. No matter how long I let it sit on the runway.

I have tried all the suggestions. Load in on runway. Let sit (for a long long time). Exit to menu. Loaded back in on runway. Saw the screens. Exited to menu. Loaded back in at a gate. WASM crash. Then I get it every time no matter where I try to start. Tried several airports. 3rd party and default. 5080, 9800X3D, 64G, Steam.