First test with the new driver revealled good performance, *** it was night time ***, I loaded the PMDG DC-6, and while the engines responded to the control inputs with my hotas, the levers in the cockpit didn't move and the gages were all frozen?

Anyone with a similar experience?

Loaded a new flight with the default Citation Longitude and all worked fine.

WASM crash?

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/390136-please-assist-us-understanding-wasm-crashes-better-even-if-you-do-not-see-them?p=399243#post399243

Edited May 29May 29 by BMIBaby

Your best bet is to trawl through the PMDG DC-6 forum threads. Loads of people (including myself) having loads of problems with what (IMHO) was a rushed "update".

2 hours ago, jcomm said:

First test with the new driver revealled good performance, *** it was night time ***, I loaded the PMDG DC-6, and while the engines responded to the control inputs with my hotas, the levers in the cockpit didn't move and the gages were all frozen?

Anyone with a similar experience?

Loaded a new flight with the default Citation Longitude and all worked fine.

Yes sir this has been heavily posted on their forums even after the new update. Quite disappointed. Well, I am still hoping for the ATR 72 to be released

That PMDG forum thread is pretty grim reading - they don't seem to have a clue how to fix the WASM problem. In the meantime life is too short to delete the WASM folder after every flight.. back into the virtual hangar it goes!

Indeed, I wasn't aware of the wasm problem until this thread 😞

But indeed the first flight right after install was uneventful.

14 hours ago, BMIBaby said:

That PMDG forum thread is pretty grim reading - they don't seem to have a clue how to fix the WASM problem. In the meantime life is too short to delete the WASM folder after every flight.. back into the virtual hangar it goes!

well neither can the ini build 350 wasm issues as well, not only related to pmdg

Edited May 30May 30 by pete_auau

15 hours ago, Adamski_NZ said:

Your best bet is to trawl through the PMDG DC-6 forum threads. Loads of people (including myself) having loads of problems with what (IMHO) was a rushed "update".

just noticed the update in oc3 updated and cleared the wasm folder and all is good again, so don't know if it was the update or clearing of the wasm folder that fixed the issue i had with no responses with in the cock pit

Edited May 30May 30 by pete_auau

10 minutes ago, pete_auau said:

just noticed the update in oc3 updated and cleared the wasm folder and all is good again, so don't know if it was the update or clearing of the wasm folder that fixed the issue i had with no responses with in the cockpit

I also cleared the WASM folder and managed a couple of good flights (yay!!). I wonder whether we have to keep clearing the WASM folder <?>.

Well, my report after my 3rd flight in this GORGEOUS / AMAZING DC-6 :

0) Before I experienced the strange problem when loading the DC-6 for the second time since I had installed it on monday, during a night situation from LPPT, I had just updated my Nvidia driver to the latest 6xx version. After starting MSFS 2024 and choosing departure from LPPT 02 (Mk Studios scenery), the cockpit had all of it's instruments frozen, and the throttle levers were stagnated, although I could fly the aircraft, control th epower, etc...

1) I did not run OC3 again, since the installation of the DC-6 last monday, and I didn't clear any wasm folder(s);

2) I loaded MSFS 2024 yesterday and it worked flawlessly.

Now it is working great.

19 minutes ago, jcomm said:

1) I did not run OC3 again, since the installation of the DC-6 last monday, and I didn't clear any wasm folder(s);

2) I loaded MSFS 2024 yesterday and it worked flawlessly.

Now it is working great.

So how did you fix it? Or was it just the usual MSFS randomness?

2 hours ago, bobcat999 said:

So how did you fix it? Or was it just the usual MSFS randomness?

Pretty much that... Didn't do anything, and in my next session it was working just fine!

1 hour ago, jcomm said:

Pretty much that... Didn't do anything, and in my next session it was working just fine!

Hmmmm ... sounds like it's some other cache/corruption - maybe not in the WASM folder. I get one (or maybe two sessions at the beginning of the day, then no-go . Next day, I get the same single successful flight then not at all. Next I'll see if a complete PC power down/restart does the trick.

1 hour ago, jcomm said:

Pretty much that... Didn't do anything, and in my next session it was working just fine!

When it froze, we're the nav radios above the glare shield orange blocks? If not you haven't had a wasm crash.

It just locked your sim.🤷‍♂️

At the moment I can delete the contents of the wasm folder and have a successful flight. If I take another flight I get a wasm crash. Even if I make a successful flight, exit out of the sim and restart it, I'll get a wasm crash on the DC6.

The - kinda - good news is that you can delete the content of the wasm folder while the sim is running and then start another flight successfully.

I've never had a wasm crash in MSFS before. Not on the 737 or the 777 and I don't use any Inibuilds Airbus, nor GSX, active sky, etc.

Whatever PMDG are looking for as to the cause of it; it's something to do with their own aircraft. Since PMDG have a hard time admitting they might be doing anything wrong, I suspect the fix for this might be a long time coming....

4 hours ago, DD_Arthur said:

The - kinda - good news is that you can delete the content of the wasm folder while the sim is running and then start another flight successfully.

Sort of - correct me if I'm wrong but I believe this action also deletes the saved state data, so a major downside.