PMDG 737 frozen sim

[DarkMantle 24]

No luck for me with this 737. Wondering if anyone else is having this problem. I click set departure on any airport. It starts to load and the blue line goes all the way to the end and just sits there. Locks it up. 

[FlyingGoose 405]

First load can take some time. Even up to 30 min. 
 

But once that’s done, subsequent loads are normal. 
 

just sit there and let it load. Give it at least 45 min. 

[Mroberts95 136]

Hi Dark.

The first load for the 737 can take 10-30mins depending on PC specs.

 

It happens with all addon aircraft etc. Once you do the first any after are fast.

 

[DarkMantle 24]

Oh ok. Thanks for the heads up. I've never experienced that with other aircraft. Even the Concord started fast but I imagine this is much more intense. I'll try it again in the morning. So you're saying when the blue load line reaches the end just let it sit?

[FlyingGoose 405]

Yes just let it sit. If it doesn’t load after 30-40 min then you have an issue. 
 

on my machine (5600x, 32 GB, NVME, 3080 Ti) first load took about 15 min. After that it’s been normal 

[DarkMantle 24]

3 minutes ago, FlyingGoose said:

Yes just let it sit. If it doesn’t load after 30-40 min then you have an issue. 
 

on my machine (5600x, 32 GB, NVME, 3080 Ti) first load took about 15 min. After that it’s been normal 

Ryzen 3700, AMD 5700XT and 32 GB as for me as well. Sounds like I'm in the same boat. Thanks again

[JRBarrett 3,048]

51 minutes ago, Mroberts95 said:

Hi Dark.

The first load for the 737 can take 10-30mins depending on PC specs.

 

It happens with all addon aircraft etc. Once you do the first any after are fast.

 

Not all add-on aircraft, but add-on aircraft written in WASM have to be compiled by MSFS itself, the first time they are run. This includes the Aerosoft CRJ, the Leonardo Maddog and the new PMDG 737. It will also apply to the Fenix A320 whenever it releases. The more complex an aircraft is, (meaning the WASM source files are larger) the longer it takes. On my system, the CRJ takes about 10 minutes on first run, and the Maddog takes about 25 minutes. The 737 is probably more complex than either in terms of the amount of WASM code, so I would expect it would take as long (or longer) than the Maddog.

This long wait period only happens the first time you load a particular aircraft. Once the compiled files are created, subsequent loading is quick.

[JBDB-MD80 1,470]

47 minutes ago, DarkMantle said:

Ryzen 3700, AMD 5700XT and 32 GB as for me as well. Sounds like I'm in the same boat. Thanks again

Hardrive? HDD, SSD, NVMe, HD speed plays a role also.

Edited May 10, 2022 by jbdbow1970

[Drumcode 1,892]

It took at least 20 minutes on my box before I was able to fly it. 

[DAD 2,650]

5 hours ago, DarkMantle said:

No luck for me with this 737. Wondering if anyone else is having this problem. I click set departure on any airport. It starts to load and the blue line goes all the way to the end and just sits there. Locks it up. 

check this from PMDG: 

 

[DarkMantle 24]

Great info! Thanks everyone

[pmplayer 9,398]

You just have to wait 10-15 mins some patience could be helpful..

cheers 😉

[Aamir 2,907]

7 hours ago, JRBarrett said:

Not all add-on aircraft, but add-on aircraft written in WASM have to be compiled by MSFS itself, the first time they are run. This includes the Aerosoft CRJ, the Leonardo Maddog and the new PMDG 737. It will also apply to the Fenix A320 whenever it releases.

Heya, it doesn't actually apply to the Fenix - we will not have long loads at first launch. First load is the same as the all the others - snappy. 

[JRBarrett 3,048]

Interesting! You are not using WASM? I assume  that the ProSim core is a stand-alone package that does not run as an in-sim process, but I thought that you would need WASM to drive the graphics at least. 

[Tom Wright 438]

55 minutes ago, JRBarrett said:

Interesting! You are not using WASM? I assume  that the ProSim core is a stand-alone package that does not run as an in-sim process, but I thought that you would need WASM to drive the graphics at least. 

WASM isn't for the graphics. As I understand it it is used to program the aircraft systems and more complex instruments such as the FMC etc.

Presumably as the ProSim is simulated external to the MSFS environment they don't use WASM.