This error for me is being rather fickle. Didn’t run into any issues this morning, then 8 hours later it kept popping up. Hard PC reboot didn’t change anything. Using default AC didn’t change anything. Using standard graphics card settings didn’t change anything.
Finally I started without the Map enhancement running and I was able to actually load a flight. Then I went back and tried with the PMDG 737… it worked. reenabled my 3080 overclock… it worked. Reenabled the Map Enhancement… it worked.
Now I’m (for the time being) back to 100% operational status. Idk what could have possibly worked, but something did.
I had to try a long haul out to make sure this bug wasn’t interfering with that. For me anyways, I’m finding this CTD is only appearing when loading up a flight and doesn’t happen once I’m fully loaded up. Not sure why that is.
In the moment is it hard to locate the error. Ive tried with and without mod, with DX11/ DX 12 and mdeium setting and high end settings. Sometimes the error appears at start screen, sometimes in flight, sometimes when loading the flight. Yesterday after a nearly complete flight - than suddenly this error message appears. Ive reinstalled the NVIDEA driver. Now I did a flight with FS9.1. - without any problems (PMDG737) and it so sad, that I had to go to this oldtimer. Even this oldtimer do not have the memoryleak anymore , the ATC is nearly the same. So where is the step forward when I cant use FS2020 with addons like PMDG. BY the way, why the ATC is nearly unchanges since 2003? (20 years!!!).SOrry, I love FS2020 but its not all about eye candy , it also should be a good and stable platform for complex add ons as a IFR and VFR simulation and not only just 4 fun for X-box gamers. And sad is, that since SU9 everythink getting worse, but is was already good before. What and where is the improvement? How can it be, that the first release/build of SU10beta was running so smooth and stable and now everything is spoiled? Since I getting the error message and then CTD , FS2020 is unplayable for me. It should not only be a softwar as service , it should also be a stable platform for develloppers and users.
People shouldn’t have to do this, this eternal dalliance with settings, troubleshooting etc. It completely destroys any sense of fun or enjoyment. Which is what using the sim is meant to be about. But instead, people waste hours of their time troubleshooting idiotic errors that in most cases have nothing to do with their settings, or their hardware.
It’s incredibly disappointing to me that this happens, without fail, whenever there is an update due.
I accept that. But it won’t be ‘fun and enjoyment’ if this issue is prevalent when it comes out of beta, will it. That and the fact that the release version is imminent, is my point.
I have been using SU10 since its release and had never encountered this problem until very recently. The only element that I changed was trying to use charts / navigraph in working titles CJ4 . It may have been a coincidence but this appears to be the only time this error occurs on my system. Food for thought.
you see right that this is a beta test but unfortunately there are also countless bugs for months that do not play in the beta e.g. MSFS Application Error - memory could not be read
and if we are completely honest MSFS never came out of beta version
Yeah, I disabled it via the bios as well and had a fine hour plus flight MD-80 KBOS CYYZ both FlyTampa no issues … fly around London once and head back to EGLL in a 172 and
The feedback to the developers was done 3 working days ago (and given there’s a time difference between Washington, USA and France - probably only 2 days since submission) at the start of the weekend. I would imagine they have received that feedback and perhaps working on it.
Also bear in mind that many these recent posts are, most likely, coming from people who are still on 1.2.7.18.0, due to the debacle around the MS Store for PC 1.27.20.0 version that had to be rolled back to 1.27.18.0.
I don’t think we have a clear picture here, yet, on this message and the related CTDs that may have been addressed by 1.27.20.0.
It’s unfortunate that the beta reporting has now been heavily clouded by there being two different versions in play.
But on main server (SU9) it was also no fun for me, because of stutters and bad performance. I dont know what and when they have changed it to worse but I think that it was starting to get worse since X-box feature(s) was implemented. That is not against x-box users (my 13 years old son is playing with it) but the should seperate things that may not work together. That’s only my opinion - Im not a programmer.
Without our complains there would be nothing changed. For me its no fun, to test and write, find out what would cause the error. Without our complains Asobo even would not know about that, normallly they should test it by themselves - even - yes - it is a BETA. But even a BETA should not be unplayable. Abd it speaks foritselves , that they declare this post/chat as “problem solved” - no, nothing is solved. Because the problem is not the error message itself but the cause for the error message that leads to CTD. It seems that Asobo want to give the responsibility to us users - we just have not the right fitting GPU/EQ . But it is bad programming. There is just a wrong code or something that’s causing CTD (even without mods and any addons). But you are right - it’s now wasted time for discuss that. Sme users might not have the problem, so they don’t care, its understandable. But for many it is frustrating - because even SU9 (not Beta) is not the alternative because of stutters and bad perfeormance - that was the reason I change to BETA. Normally I would not do that, as long the old version runs stable. But that wasnt the case.
This statement was only concerning the confusing “Text Message” but not accepting that there must be a problem behind - without this text we would just have a CTD - now we have a (maybe wrong) analysis and when we tick “yes” the CTD comes
