5 hours ago, GCBraun said:

The files that need to be deleted are in the AppData/Local/Packages/Microsoft.FlightSimulator_XXXXXX/LocalState/Packages/pmdg-aircraft-73X folder, as seen below:

Deleting those files in red before each sim launch solves the problem for me. Hope it works for you as well.

well done someone buy this man a pint. 

never ceases to amaze me how random people can find the solution within a few hours, yet the beta testers and program devs cant find in weeks and weeks of beta testing.

again well done.

Edited May 25, 20242 yr by fluffyflops

Long thread on this issue,       https://forum.pmdg.com/forum/main-forum/pmdg-737-for-msfs/general-discussion-no-support/296791-su15-yokes-turned-hard-left

I was on the SU15 beta and had to stop using the 737, it just locked up every time I tried a flight.

5 hours ago, GCBraun said:

The files that need to be deleted are in the AppData/Local/Packages/Microsoft.FlightSimulator_XXXXXX/LocalState/Packages/pmdg-aircraft-73X folder, as seen below:

Deleting those files in red before each sim launch solves the problem for me. Hope it works for you as well.

Thank you so much for your dedication.

On my laptop, it did work perfectly. When I get back home, I will try it on my desktop and let you know. Again, much appreciated.

8 hours ago, GCBraun said:

The files that need to be deleted are in the AppData/Local/Packages/Microsoft.FlightSimulator_XXXXXX/LocalState/Packages/pmdg-aircraft-73X folder, as seen below:

Deleting those files in red before each sim launch solves the problem for me. Hope it works for you as well.

I think I know why deleting those files solves the problem for those affected. It is not the files themselves which are the problem. 

The issues that some people are seeing: yoke turned fully left and all systems inop, are a symptom that the 737’s DRM check failed. The aircraft was unable to verify that a valid PMDG license for that aircraft exists. I don’t know whether that license check is done locally or online, but for whatever reason, for some users it is failing in SU15.

Perhaps the license check subroutine is not running at all due to a bug, or (more likely) it is a timing issue — I.e. it is not completing before the rest of the initialization finishes.

I pretty sure that the license check is done after the aircraft is selected to load, and before the aircraft actually appears at the selected airport. During that initialization period, some developers display a text billboard highlighting various aircraft features, or semi-humorous messages, such as Fenix: “Did you know that over 1000 people fly on airplanes every day”. 🙂

The four files you highlighted are the WASM files which contain all the aircraft’s internal logic. Most of that is contained in the file with a DLL extension. The other files contain various configuration and other runtime information.

These files are created by a C++ compiler built into MSFS itself, using WASM source  code supplied by the developer in the aircraft’s installation directory. The files exist with any aircraft written in C++ using WASM. There are usually 4 files. Sometimes there are more than 4. The files are created (or re-created) under three scenarios:

1. When the aircraft is first installed.

2. When the MSFS executable file version changes.

3. If a user deletes them.

In the latter case, it is the same as if the aircraft has just been installed for the first time.

Once these files are created, they are not “touched” again by MSFS except as read-only. I doubt very much that these files are becoming “corrupted” or otherwise damaged between runs of the sim. That is not likely to happen unless the computer has a serious hardware problem with disc or SDD drive access. If the files were corrupted, MSFS would probably CTD immediately when the aircraft tried to load.

That is why I think the license check validation failure is a “timing” issue. IF the WASM files do not yet exist when an aircraft is loaded, the aircraft initialization routine calls the MSFS built-in compiler to create them. Otherwise, it skips the compilation step.

Compiling those files takes quite a bit of extra time. On my system, the 737 loads in 15 seconds if the WASM files already exist. If they do not exist, it takes almost 2 minutes. 

I suspect that the extra delay (waiting for the WASM files to be created) allows the license validation routine to run to completion for those affected the “twisted yoke” bug.

Fixing this is ultimately PMDG’s responsibility, but it may not be easy for them to do - especially if it does not happen on their own production computers. They would have to look closely at how their license check routine is coded, and where it “fits” in the overall initialization code. It would be much easier if they had at least one production computer affected by the bug, so they could test any potential “fix” before releasing an update to customers.

Edited May 25, 20242 yr by JRBarrett

9 minutes ago, JRBarrett said:

I

Fixing this is ultimately PMDG’s responsibility, but it may not be easy for them to do - especially if it does not happen on their own production computers. They would have to look closely at how their license check routine is coded, and where it “fits” in the overall initialization code. It would be much easier if they had at least one production computer affected by the bug, so they could test any potential “fix” before releasing an update to customers.

Someone on t he PMDG forum just posted that he could get the problem to go away and reappear by removing GSX. I wonder if this is a GSX issue. ( which I don't use and have no problem). PMDG might not have GSX installed on their PC's.

 

 

Edited May 25, 20242 yr by Bobsk8

4 minutes ago, Bobsk8 said:

Someone on t he PMDG forum just posted that he could get the problem to go away and reappear by removing GSX. I wonder if this is a GSX issue. ( which I don't use and have no problem). PMDG might not have GSX installed on their PC's.

 

 

I don't have, or use, GSX and I have the problem since SU15

Just now, StoneDoor said:

I don't have, or use, GSX and I have the problem since SU15

Well that answers that question....

1 minute ago, Bobsk8 said:

Someone on t he PMDG forum just posted that he could get the problem to go away and reappear by removing GSX. I wonder if this is a GSX issue. ( which I don't use and have no problem).

 

Possibly. I do have GSX, but don’t have the “license check” problem. When GSX is present, it takes MSFS itself quite a bit of extra time to load, but that delay is in the initial MSFS loading screens - before the aircraft selection UI appears. But, perhaps GSX is having an affect on the 737 initialization too - at least for some users.

Forcing a re-build of the PMDG WASM files (by deleting them), does seem to fix the problem for those affected, I do think that is because of the extra time required to build the files, rather than any problem with the files themselves.

I loaded each aircraft and they were fine. Have to see what happens as time goes on.

14 minutes ago, JRBarrett said:

Forcing a re-build of the PMDG WASM files (by deleting them), does seem to fix the problem for those affected, I do think that is because of the extra time required to build the files, rather than any problem with the files themselves.

Interesting theory, that could explain why the issue is worse with SU15 as it loads much faster.

G

10 hours ago, GCBraun said:

The files that need to be deleted are in the AppData/Local/Packages/Microsoft.FlightSimulator_XXXXXX/LocalState/Packages/pmdg-aircraft-73X folder, as seen below:

Deleting those files in red before each sim launch solves the problem for me. Hope it works for you as well.

is this the same for the 738 ?  thank you

The other thing that has worked for me is to hit esc and just hit restart (Home key on US keyboards by default)  and allow it to reload at the gate. 

That has worked every time so far and doesn't require exiting all the way out to the home screen....

Edited May 25, 20242 yr by psolk

Should we expect any official patch from PMDG or use this work-around?

12 hours ago, GCBraun said:

The files that need to be deleted are in the AppData/Local/Packages/Microsoft.FlightSimulator_XXXXXX/LocalState/Packages/pmdg-aircraft-73X folder, as seen below:

Deleting those files in red before each sim launch solves the problem for me. Hope it works for you as well.

Those files are present at my B737/700 folder, which I bought from PDMG, and have no problems with it, my problem is with B737/800 bought from MSFS Marketplace, and found that those files are not present at its folder. Should I have to reinstall it ?