AlexJBerry

This is something which has been an issue in the sim for a while. However, unless it’s coincidence, it appears to be resolved in SU9 beta

I tried the similar approach to OPs, but the difference I had was too great, and would require me to fly at too high altitude for aircraft. So now, I get clearance to desired cruise altitude. Then either, a) wait until you receive a hand-off, at which point you can acknowledge the hand-off, retune but don't contact new controller. This means you remain on IFR plan with no ATC. When it comes time to descent, contact controller and then carry on as normal. Or (b) retune to empty channel and go silent. This will obviously work, but likely find your IFR plan cancelled. Not a big issue and there's usually the option to retry IFR clearance once you tune back in later. This approach goes back to old FSX days and still works. Just goes to show the ATC implementation is taken directly from old FSX with little or no change since. I'm sure it will get updated one day as there's so much that could be done to improve it. Anyway, that's an entirely different, and lengthy topic.

Only Paracetamol, to ease the headache of trying to get the sim to work. Sorry, couldn't resist...

Having built my current PC back in March with a 3900X and 2070 Super GPU coupled with 32Gb @ 3600Mhz RAM, I'm getting really decent FPS (30+) in Flightsim at mostly Ultra with one or two sliders pulled back a little to their High setting. BUT, I'm also so tempted with the upgrades coming out now. Without the need to upgrade motherboard, I could go to the 5900X (or even 5950X, though that would be total overkill), coupled with the new RTX 3080 (again tempting to go all out for the 3090 but again, probably overkill). Want to maximise potential of the current PC in terms of motherboard (X570), ram etc, and I think this would take it as far as it'll likely go before a complete rebuild next time. Might as well spend the cash that would have gone on holidays and travel given that's off the cards in the current circumstances...

Yeh, you’re right; I must be running a different version of Microsoft Flight Simulator after all.

Surely the point is this: in a situation where a load of people are running exactly the same app on different machines and one group are getting on just fine whereas the other are suffering CTDs, then the obvious place to look is differences in their setups. It could be any one of the following: - hardware and config, including overclocking and non-standard bios settings, drivers etc - software environment, including OS version and config, other apps running in background or foreground - app mods and non-standard setup and any conflicts there The evidence from the thousands of people running MSFS2020 just fine is that fundamentally the software is sound save for some feature improvements required. those suffering CTDs however must, in the first instance at least, look to their own setup and ask themselves “why me?”. The answer is almost certainly one or more of the causes outlined above. It’s very difficult to diagnose the specific issue impacting one person’s PC experience, but almost impossible for the software developers to do it on entirely different systems and setups. Broad-based testing and diagnostic tools can help, but it’ll never help everyone. finally, remember the few with the greatest issues (plus the trolls, of course) will always shout the loudest and cloud the impression given on forums such as this. Unfortunately, in more ways than one, the spotlight‘s on them.

Definitely an issue with FacetrackNoIR. Even if not using it, just having it installed can cause this issue. Fully uninstall FacetrackNoIR from PC and problem goes away.

Yes, I noticed that almost immediately, and posted on the main MSFS forum... Nobody else commented though. I'm glad I'm not the only one!