Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
It seems on flights longer then 4 hours the simulator crashes right at landing or once landed. This using the MS 787 and the new PMDG 737-700. Not sure if it is memory problem.
Provide Screenshot(s)/video(s) of the issue encountered:
There is no way to grab the screen
Detailed steps to reproduce the issue encountered:
I flew from LAX to EWR and it crashed; Rome to EWR; France to Seattle (The challenge) and various other long haul trips.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
Over the past 3 weeks. Latest Build. It seemed to start after the last update. I have the Deluxe version
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
CTDs are very hard to fix or diagnose. You really need crash logs to know what was the culprit. It could be one bad model loaded into memory or one bad memory location.
I have CTD’s on long flights as well. However I was able to complete a 2,5 hour flight the other day.
I had one CTD flying from KSLC/Salt Lake to KBOS/Boston (1825 mi). It CTD’d at 900 ft just before I was going to disengage the AP. The flight got invalidated (flying on FS Charter) which is very frustrating…
Had a flight from LPMA/Madeira to EDDF/Frankfurt (1533 mi) that CTD’d around Paris just before the descent.
Today from PANC/Anchourage to KORD/Chicago (2467 mi) I had a CTD around 3 hours in flight (mid flight, somewhere over Canada).
I’m pretty sure it is a memory leak of some sort. I never have this on short flights. The only CTD’s other than these are from the menu pages. That is also a bit frustrating, but nothing like a long flight with all the preparation, etc. that gets invalidated… It always puts me off flying for a week or so before trying again.
I’ve had similar issues, only with the PMDG 737-7. I love the aircraft, but it only seems to CTD on longer flights. I tried flying from KMDW(Chicago) to KLAX and it crashed about 10 mins into my descent. However on shorter flights there’s no issues.
The only 3rd party add on I was using was PACX, and I confirmed my internet and pc didn’t have any issues.
What’s strange is I’ve taken the 747 on numerous flights that are 6+ hours with the same add-ons and pc/internet settings and never had any CTD’s. I hope this is something that can be addressed.
It seems it is a memory leak. It seems to happen when I have to make adjustments to the FMC based on Approach Control’s instructions for landing. I also think it adds to the issue by changing views between internal and external. This is a guess on my part
I have had an issue similar to this. After I am on ILS and Glide, when I turn off AP and AT, the place goes crazy. First thing is it pitches up hard with no control over it. The trim on my yoke has no effect, though I can manually turn the trim wheel with the mouse, although I never get it under control as it will enter a dive. No control over throttle and, of course, the AP / AT will not enable.
I fly only long haul and 99% of the time that would be in a PMDG aircraft because they just work as they should. It is beyond frustrating to get within sight of the field only to turn into a grease stain. I think this happened in the 787 last time I flew it last week.
I did not have this experience before the latest update. I can try something if you need, just ask.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
