June 17, 20205 yr So it will load from time to time but the majority resorts to p3d using less then 1% of the cpu and the screen just freezing. Deleting config worked once, did it again today and no luck, tried restarting and no luck. Edit: I am also loading up the F22 then the aircraft, as straight from scenario screen is 100% no load. Anyone got any suggestions as to why this would be happening / fixes? P3D is on a separate drive but I don't believe that would effect it anyway, or would it? Thanks ppl! Edited June 17, 20205 yr by CptJackSparrow
June 17, 20205 yr You can select the PMDG aircraft directly from the menu without having to load a default aircraft first. Have you tried this? Jude BradleyBeech Baron: Uh, Tower, verify you want me to taxi in front of the 747?ATC: Yeah, it's OK. He's not hungry. X-Plane 12 and MSFS2020 🙂 System specs: Windows 11 Pro 64-bit, Ubuntu Linux 20.04 i7-13700KF Gigabyte Z790 RTX-4060-Ti , 32GB RAM 1X 2TB M2 for X-Plane 12, 1x256GB SSD for OS. 1TB drive MSFS2020
June 17, 20205 yr 2 minutes ago, Jude Bradley said: You can select the PMDG aircraft directly from the menu without having to load a default aircraft first. Have you tried this? I can conform that too, as I just loaded the 747-400 that way you describe. And no issues whatsoever. Rick Almeida
June 17, 20205 yr Jack, I suggest you contact PMDG at support.precisionmanuals.com Give them as much information as you can, including your P3D and B737 versions (i.e. the original 737 or their newer 737NGXu). Bertie Goddard
June 17, 20205 yr Author Thanks for the fast replies! I will give it try now. Funny thing is PMDG support said to try the former, which works from time to time. After loading from the scenario screen I've been stuck at 18% for about 3 mins now. This usually happens or at 26%. Tried reinstalling and all that but nothing seems to work. Guess its back to the fslabs a320 for the meanwhile. Just strange how it works then all of a sudden it doesn't. Edited June 17, 20205 yr by CptJackSparrow
June 18, 20205 yr Author ran a check for updates on windows and this seems to have fixed it. Fingers crossed
Archived
This topic is now archived and is closed to further replies.