Anyone else experiencing crash to desktop?
-
I've been flying in VR on 2024 SU4 for ages, but when flying the Caravan Pro, I always crash to desktop after ~10-15 minutes. Anyone else experiencing this?
Tomorrow I'll start eliminating other add-ons to see if I can isolate it to a specific conflict...
Thanks,
jaz -
To close the loop here, after another day of experimentation, I believe I've narrowed the problem down to memory corruption between SU4 and the 59x.x series of Nvidia drivers, not a problem with the Caravan Pro.
After dropping back to 591.86, I haven't experienced a crash since.
-
For me, the Black Square Caravan Professional is causing msfs 2024 to freeze or ctd when ending one flight and starting another in the same session. This is even happening with an empty community folder except for the Black Square Caravans and it occurs every single time that I go to end a flight and start a new flight at another location. If I do the same thing with the BS TBM850 the issue is gone. I have not experienced it with any other aircraft either, just with the Caravan. This is in SU4.
-
Sadly, my CTDs are back. I've tried several combinations of video driver version (always after running display driver uninstaller), emptying my community folder, clearing the rolling cache, reinstalling msfs, etc. and it always crashes after ~15 minutes, sometimes earlier.
Wondering if SU4 issues (e.g. cockpit persistence problems) are causing stability issues. CoherentGTJS.dll is often the culprit, which makes me suspect javascript conflicts. I'm using Beyond ATC in VR through the toolbar, which is dependent on javascript reliability.
-
-
I hope you guys don't think I've been ignoring you. Unfortunately, I wish I had better advice to offer. The code in the Caravan that might have anything remotely capable of producing a CTD is identical to my other aircraft, and the Caravan has even less in the way of avionics than most of my other aircraft. I know several of you are seeing symptoms that appear limited to the Caravan, but I have also seen similarly limited behavior with my other aircraft in the past that resolved themselves in various different ways. Luckily, I haven't had any consistent and persistent CTD reports (other than v1.0 Starship) with my aircraft over the years, largely in part to their architecture, which avoids WASM, where CTD's are most likely to happen. I would encourage you to keep looking for outside applications or system-level issues that might be causing this, but in the meantime, I will be watching this thread closed to see if there is anything I can learn, or anything I can suggest for testing. Sorry that you're dealing with this right now. I just wish I had more to offer.
