i think that MS needs to establish separate division for the sim maintenance, and not to put all the sim pressure to Asobo, MS have experts in all the fields.
well, Xbox studios CEO, admitted that this is the way the industry should & well be going to.
Iām pretty sure Asobo donāt go anywhere near these advanced memory optimisations ā¦ that will be Microsoft all the way. Remember Direct Storage and all it entails? Itās all pretty new and relatively untested in RL but Iām pretty sure MSFS has been using elements of it since SU5.
yea, more technical revolutions are coming, & specialization is what is needed for stability & premium performance.
Do you have the same issue if you follow the OPās steps to reproduce it?
Provide extra information to complete the original description of the issue:
Got this Error since SIM Update 10. My flight sim crashes instantly when it has loaded successfullyā¦When Iām in the Main Menu, this Error shows up directly.
SPECS:
GPU: RTX 2080 Super MSI Gaming X Trio
CPU: i9 9900K
RAM: 32GB 3200Mhz Corsair Dominator Platinum RGB
My MSFS runs on a 1TB Nvme SSD (WD SN750)
Are you using DX12?
Yes
Are you using DLSS?
Yes
If relevant, provide additional screenshots/video:
Anyone already tried the latest Nvidia driver 526.47?
B.t.w im still following this thread although my CTD crash is solved since i disabled HAGS almost 2 weeks ago!
Tried with the new Driver, same result as before. HAGS is disabled. Shame the devs donāt seem to take the stability of this simulator seriously.
Yes, itās really very frustratingā¦ Unfortunately we have to wait at least 2 weeks for the SU11. If it works at all then again!!
If developers didnāt take stability seriously, then they would have a very difficult time developing and publishing updates and delivering fixes. I think that if the developers had a CTD every time they started MSFS or had a CTD at the Main Menu it would be fixed ASAP.
Update from my end. I installed the latest Nvidia driver 526.47 and managed to fly for an hour+ YSSY to YMML.
CTD 30 seconds after I landed.
An improvement from 15 minutes of flying!
Changes I made was turning off HAGs, and turned off the second monitor.
My settings were;
DX11
Ultra
Vsync on
Going to try a few more flights over the weekend.
I can almost confirm that the old 496.76 does not produce this issue after two days of flying with plenty of flights. Deadly stutters are gone so the sim just doesnāt crash.
I know this is quite an old driver but thereās always the option to use it and remove it as needed at least until there is a proper fix for the issue.
If somebody reports the issue with 496.76 then I was just lucky but so far I think this driver can let us use the sim without interruptions.
When installing 522.25 and 526.47 my sim doesnāt even fire up and instantly gives out the warning at title. After installing SU11 Beta it seems that problem is gone for me for now.
This. Enough with the excuses. The party of excuses has ruined so many things in this world. These people need to stop making excuses. Itās not peoples computers, itās coding.
With that said, I want to be very clear, this is the best msfs to date.
This company has done more updates, given away more free content, far more than any other version of msfs, since launch and has been supported WAY more than FSX ever was supported by Microsoft.
My first statement doesnāt reflect my view of the sim or the company that makes it given that Bethesda games that have been around for many more years than this, and have 20 or more iterations of the same game, still have the same bugs. What I have a problem with and why I made that first statement was being complacent or even defensive of the problems doesnāt fix them, and only hurts the sim and the company in the long run. The fan boys arenāt helping by making ridiculous statements such as āitās your computer.ā
Itās NOT your computer, itās the sim. I can fly around Sidonia for two hours without a crash however if I go into flight training I crash every other flight training mission when flying in the same area that I can freely fly in free room without issue. That clearly has nothing to do with my computer and the settings that Iām running, it has to do with some sort of coding with those flight training missions that for whatever reason crash when loading every second mission I try and load after completing a previous one. I can back out and change aircraft, load the same area up repeatedly and never have a crash, only when I go into fight training. Plus it crashes even before it loads (again only when doing flight training missions?)
Itās like I think everybody in this country is finally figured out, we know weāre getting screwed, and weāre used to dealing with it, but when theyāre screwing us and then telling us itās our fault, that weāre the bad ones, that we deserve it, and that they deserve to do it to us, then it gets infuriating. I want to state very clearly that itās not coming from the company in this case, itās coming from some fan boys, so again grain of salt, but I had to jump in too and agree with this guyā¦ itās NOT your PC, itās coding.
We can support the simulator, support the company making it, and still be critical. I understand that certain party has problems with criticism, but itās OK itās time to put on their big boy pants, grow up, and take a deep breathā¦ everything will be all right. Itās ok to be critical. Itās ok to have a different opinion. Itās not the end of the world musk bought twitter. ; )
Too much hyperbole. Thank you for pointing out itās definitely not peoples computers.
Iām not sure if this is related but I think it may be due to the high amount of posts in the last couple weeks (including mine earlier in this thread).
Anyway, I setup my plane (FBW a320) at KDFW, and taxied all the way to the runway. I began to take off by throttling up. At this point, the entire sim froze, then crashed to desktop. I went to check my GPU stats in MSI Afterburner and this is the message I received.
Iām running DX12. When using DX11, I get the "graphics card my be overclocked, overheating, or driver faultā error like so many above this post.
My entire computer is up-to-date with the latest drivers for everything. I havenāt had so many problems since the latest MSFS update. I had to do a reboot to get my GPU stats back.
Dedicated FS machine - Never overclocked:
ASUS TUF gaming X570 plus @ 3600x
MSI Geforce 2600 Super
Hello together!
I have to agree. I am the one who discribed this āerror message problem /CTDā the first time. Very quickly this problem was marked as āsolvedā by a moderator, which of course is not true when you see how many flight sim users here have described the problem.
I must say that I have always received very quick responses from Zen Desk Support, so I canāt blame Asobo / Microsoft in that regard. I have received at least 3 different answers or suggested solutions from support. I have also posted these here in the threat.
The hardware of my system has not changed since the first release of the flight simulator. There has always been sometimes CTD in former versions of MSFS, but this error message regarding the GPU has only been there since the 2nd build of the SU10 BETA. My system is neither overclocked nor overloaded. The error message also occurred with older GPU Nvidea drivers.
Since I changed a few Windows settings and GPU settings (also regarding power management), I get this error message very rarely. Interestingly, it is often only in the start or pause menu, when the simulator does not demand much from the graphics card.
I can now make longer flights with FBW Airbus or other more complex add-ons.
It seems to me that this error occurs very irregularly. It is probably a combination of many settings in the flight simulator, the GPU and the Windows system settings. However, the cause should be an error in MSFS. Maybe also regarding the GPU / driver. But then Asobo would have to get together with Nvidea and find out.
I havenāt done a reinstallation yet, because it hasnāt helped many people. I have the penultimate GPU Nividea driver version. Since it works with it, I donāt dare to install the latest version yet. Never touch a running systemā¦
I hope Asobo solves the problem once and for all. Itās strange that I had the error message very often in the beginning and it seems to have fixed itself now - or I happened to make the right settings.
Thank you for your comment.
As a matter of fact, I was still with TAA and now I switched to DLSS.
And it works now !
Difficult to understand what they do as developersā¦
DLSS is no āsolutionā as than you have very blurred displays (like Garmin and PFD in Airbus).
I have a stupid question that deserves a stupid answer (it may have been asked before). Since this problem still exists why is it marked as solved. Is it too hard to un-solve it?
Where do you see it as solved?
Iām not seeing it marked solved by a moderator. I do see a post marked as solution by Microsoft.
Every time I reply.
