I’m sorry to confuse you with my CTD’s informations. Seems to be my private problem(?) and my system seems to have much more problems, as for a bigger part of the Comunity. But I’m surely not alone in this forum with the CTD Problems of my(!) installation.
Anyhow, my System (Core I9, Radon 5700 XT, 64 GIG RAM, 1 TB SSD) all Standard PC - Components in high quality and - from this - very expensive for me (>3000 Euros), runs since 1 year complete stable w/o any problem for so many other things than the FS, and it was well updated & never tweaked or overclocked. I’m an Informatics engineer with deep computer experience.
The messages, i wanted to tell were:
a) Now (after full clean Re-Setup of my system) the reported Bug (Aerolite at Eastfrisean Island Apt) is NOT! occuring for me.
b) I have Many Flights simulator CTD’s (…never seen in this amount due to 35 years of Fligth simming, and surely no fun with them now…)
c) I invested 12 hours of Time after World Update 3 for re-installing my whole system, and it runs the FS now “a little” better, than before.
I know, that you are frustrated, but - sorry - I’m too.
My Only hope: Microsoft and Asobo work hard to improve their product. I can only hope for us all, that they will improve the situation due to the next months and years.
I have had 0 in flight CTD, only ctds in the options - control menu after my chargeable wireless mouse needed the USB c cable inserted for charging. After that it took me some (too much) time to figure out a work around for this : remove dongle for wireless mouse, plug in another mouse, boot up fs2020 and enter controller menu, exit fs2020, swap back to the first mouse (without charging cable) : good to go. Need to make sure mouse have plenty ow power at all times
@ConveyedEarth80, forgive what may be a stupid question, but what does this even mean? I feel like it’s something I should probably know about, but I do not!
It is a file dealing with some sort of scenery or object that is shared among airports. Including payware. Like a common building, truck or some object found at large airports causing the problem. For instance my KATL by Imagesim has no CTDs. But when I deactivate it and load MSFS KATL I encounter CTD. Almost all of the handcrafted airports for me are causing CTD before or several minutes after takeoff. It could even be a car in traffic on the roads. Some people have put traffic to zero and not having any problems. I can fly with no CTDs as long as a stay away from payware and handcrafted airports.
I reported three CTDs to Zendesk last weekend alone. The number of CTDs has increased continuously since the December update. I habe problems to finish the flights for my VA with the A320NX all over Europe.
Since launch in August 2020 I have had 2 or 3 in total, that’s it, and I have flown alot. This was in the beginning, none since November.
I put it down to the fact that I bought a brand new computer for FS (and DCS) and have 0 in the community folder and only 2 airports installed, and a fast connection.
To be frank with you, I keep reading that people CTD all the time. In my case with my rig (I9, 2080TI, 64gb RAM and G2 VR) I experienced no CTD at all… The only CTD happens when I am on the scenery editor which is extremnly buggy, but not flying…
I don’t how you put up with that. I would have given up a long time ago.
But given that so many here report (almost) no CTD experiences, I would not hold my breath in waiting for Asobo or MS to fix yours.
Clearly, there must be something your system chokes on and mine doesn’t.
My first suspicion goes to your hardware, in particular an overheating CPU or memory. So I would open the case and all the windows, put on a warn coat and go flying, just to see if it makes any difference.
May be more truth to this than at first glance.
I mentioned i had random CTD’s, but i found one particular flight plan that would CTD every time i attempted it. I turned off my CPU boost and ran at base speed only, and was able to fly that particular flight plan without a CTD. That’s what led me to believe the issue, for me, was a thermal issue, despite not having any issues with any other CPU intensive apps.
I’ve come to the conclusion that this sim doesn’t play nice with boost technology.
I reduced buildings and trees one notch in graphic settings, to medium, and have not had a driver timeout since. I still get CTD’s, maybe about 15% of my flights.
I’m more amazed it lasted that long (I have 16GB ram, game has 41GB allocated)
No clue what Bad_Module_Info is. Never seen that before. Usually it’s an exception or the game simply disappears. Reducing terrain detail a bit or flying slower lets it survive (was racing at 187 knots at 500ft over London at max draw distance to trigger memory leaks)
this was normaly the issue with the full screen optimization since…I forgot… a while ago. Can be disabled within file settings ( right mouse on exe ). Possible happens also in case low memory. You have overall ( RAM + pagefile ) 40GIG memory ?
Yes it was low memory. I have 16GB physical ram, windows managed pagefile on SSD. There was still plenty room on the SSD but not surprising stuff breaks at some point. When FS2020 goes over 40GB it’s game over (and unplayable long before that ~2 fps)
FS202 only goes that high (with my settings, normally 30GB is about the max it allocates) when something is wrong, in this case, me pushing it beyond its limits. But it does happen normally as well, although rarely. There seems to be a memory leak in certain areas with lots of trees / bushes. Out of 1500 hours flying I’ve only naturally triggered it under 10 times.
At first it was due to the rolling cache updates falling behind, the game hanging on to the data queued to be stored, pushing memory use ever up. Yet I still got it a few times without any cache. The last 2 were over the Australian outback, made no sense (not many tress, maybe all the shrubs?) and before that over Borneo which is an ocean of trees. Hence my suspicion it’s vegetation related. (Maybe autogen related, cities don’t stretch on for miles and miles, hence it survives those)
I found one place where I could consistently trigger the condition, flying from Cazombo FNCZ to Lumeje FNLM low over the terrain. Flying too fast triggered the runaway memory use. No clue if it still does that there, flying higher solved it.
Anyway, if the sim falls behind in preparing the terrain for whatever reason, it will keep allocating more memory than freeing up behind it, which leads to a downward spiral.
I see also this amount of usage, but it is not “persistent”, only a short time. In my case it is ok because I own lots of RAM. But normaly the app-memory-managemt should avoid that if the amount of memory not physical exist. The pagefile lies on SSD and a SSD have limited write-cycle => lifetime.
Yep, normally the high load comes back down, it’s all the hard faults that slow it down, causing it to fall behind, allocates more (unless I pause the plane letting the sim catch up), more hard faults, etc.
Normal load is more in the low 20 GB range. Still more than my physical ram but a lot of that is inactive and hard faults / sec usually stays at 0.
I’m waiting for a memory upgrade to be shipped. It’s this bloody pandemic and shortage of PC components. “Waiting for Carrier Pick-up” for nearly a month now. Newegg usually seems to be reliable, everywhere else was simply “out of stock”. Shipping from China
