For most people, the game just works, and the silent majority is happy with the last update! If you have specific issues, please report them.
2 Likes
I also have noticed the blurry mess of dash and nose.
OK. It actually doesn’t take a “gaming specialist” to build a modern gaming PC. Maybe 20 years ago. But now a days 30 min on the internet will tell you all you need to know. Order 4 compatible components (processor, ram, video card and a motherboard) online, slap a power supply in a chassis and load Win10 on it. Bam…done. What it takes is money and availability, and the more money, the faster the rig.
If someone has a Frankenstein rig built from old gutted PCs then they may have issues. But honestly most anyone serious about building their own (new) gaming rig, and serious enough about Flightsims to be on this forum, knows enough to put together a working computer that’s compatible with MSFS.
And what about other games? Are they having issues with those too? It doesn’t seem so from what I’ve read. It would stand to reason that if all their games except MSFS are working as expected then it’s probably not a compatibility issue due to not being built by “a gaming specialist”.
6 Likes
The audio crackling after 1 hour flights is going to give me ear cancer
Exactly! Why is this issue only happening with FS2020, and not other products also being used on the same PC?? Never had any issues in the past FS2020 updates. But Update 5 definately impacted me.
Envy the guys who are enjoying a smooth transition…
My Dear Co - Simmers, I am not very Tech Savvy! Those who understand the technicalities…can you answer these 02 questions…
- If, during the process of FS2020 Updating, the internet is lost, would FS2020 restart updating from the point the internet was lost? I had started the UPdate 5 on 27th JUL, but was not present when there was an internet down time…so was not sure if Update 5 was fully installed or not. When I start FS2020, I do get the updated screens and map etc, but when I press the FLY button…it’s always CTD.
- I have the following system (which did not have the CTD issues before 27th JUL). Is it compatiable for FS2020? Never had any issue with FS20202 prior Update 5.
Video Card - Ge Force GTX 1050 Ti
Video RAM 4.0 GB
CPU - Intel (R) Core ™ i7-10700F CPU @ 2.90 HGz
RAM 32GB
OS - Windows 10
Free Disk Space 418 GB
Any advice or suggestion most welcome as am desperate to fly!
1 Like
yes, and guess what, suddenly they have problems. Everything in a PC setup matters from the type and quality of the cables to the compatibility of all the components.
I keep reading that its NOT the hardware and frankly it doesnt make any sense. The simple fact is that we
all run the same software. The only, ONLY difference is local setup. So I do wish if it isnt hardware as so many keep telling me, someone would kindly explain, given the fact that we all run the same software why people like me can run everything on Ultra + without any CTD, stutters, crashes or any other problems with a rock steady 30 or 60 FPS what the differentiating factor is if it isnt hardware. Wish someone would explain that now because saying that someone can run another game without issues is not very relevant. We are talking about this SIM.
The only differentiating factor is local. Now I dont discount that this may be because people frig around with things, or install mods that suddenly interfere, or have indeed via the internet cobbled together a so called ‘gaming PC’ just because they have bought ‘top’ components, or heaven knows what else. But the cause of all the problems are local, not the Software. It runs fine with thousands of installations.
People complain and then in the next post happily explain how they alter the CFG file.
So somebody explain, if it isnt your local setup why then does everything work 100% fine in ULTRA somewhere else?
1 Like
If Hardware was the issue here for CTD’s, why on earth wasn’t there a single CTD since DEC till 27th JUL, that I experienced. FS2020 was updated several times and all worked very well on ULTRA settings. But since Update 5…wham…game over!
No Offense to all who are having a brillant time with NIL issues…good for you, and I hope it always remains that way…but when the plug is pulled out without any reason…it’s frustrating man.
2 Likes
Just remember this: we’re not running the same software.
Unless all the settings are the same, the airplane is the same, the location we start from is the same, the presets are the same, the weather is the same, the data-streaming is the same, Windows is exactly the same, Windows settings are the same, the drivers are the same, the BIOS is the same, the speed we’re running at is the same, and so on… and all that doesn’t make it hardware… it’s software interacting…
I’ve had CTDs on the FBW airbus. Some tried to blame my hardware. Guess what (I already knew): it was the software after SU5… they solved it…
the quality of the cables? So the bugs showing up in MSFS is NOT software related? but actually could be due to the cable quality?
1 Like
CynicalLake solved it. it’s your hardware, It’s the ONLY possible explanation. 
It did for me from what I can remember, I restarted the download and the folders it created and files loaded before the download froze were still there and picked up where it left off.
As far as th CTDs and your setup, the only thing I can suggest is make sure your 1050Ti is not overclocked. My video card was OC’d (using MSI Afterburner) prior to SU5 and it was fine, then after the update it crashed constantly until i set it back to default.
However the difference in the components you listed and mine is the Video card, Mine is a RTX 3090FE. Everything else is identical.
Also had to remove the summer and spring foliage addons i bought in market place. This also caused immediate CTDs.
Read what I wrote before commenting please.
no I said the only differentiating factor is local, not the software. I mentioned that there are many different factors that influenze the local setup. I was making the point that keeping on blaming the software doesnt make much sense if running the same software runs fine with thousands of installations. The only differentiating factor is local.
For once read what I actually wrote please. 
MS sorted the ACTUAL bugs in the software that affected EVERYBODY fairly quickly with two hotfixes. Anything else is down to your local setup.
If its NOT then please explain why the same software works fine for others and not for you? What is the differentiating factor? Could it possibly be local setup?? I still havent seen an answer to that question.
A fine list of LOCAL setup differences.
If its NOT then please explain why the same software works fine for others and not for you? What is the differentiating factor? Could it possibly be local setup?? I still havent seen an answer to that question.
That’s the issue! No answer to that question. Surely It’s not for me to explain, I’m not the developer. Ask them…then please hold your breath for their response.
In NVCP set it to 16. Don’t let application control…alot better but not quite like before update.
1 Like
Now you see, to me that is an interesting answer. You are sidestepping the obvious. We all download the same software and according to one of your previous replies its child’s play to build a good gaming computer.
But there are only two variables: the CTDs and other ‘hardware’ failures (cause thats what they are) are either due to the SIM software or due to the local setup. I and thousands others dont have CTD or other issues.
All I want to demonstrate to people is that the local setup, and I mean that in its widest sense, is the only real demonstrable variable in all this, which means that the answer ‘why do I have CTDs’ lies locally and bashing hell out of MS wont alter that and probably wont fix it.
Q.E.D. I think.
Does anyone know when the next Q and A is?