I am using AMD RX5600XT and only once since 1.27.21.0, a dialog appeared while playing music in the background.
Also, I have had a few instances where it hung with a “beep” sound while playing Youtube using Firefox in the background, although no dialog appeared. sound when playing Youtube using Firefox in the background.
I have never had hangs with versions prior to 1.27.21.0, but I remember that I had a similar hang with red dead redemption 2 and Ark, and could not start them no matter what I did.
At that time it was the sound driver that was causing the hang up because it could not recognize the device (graphics card), but after the msfs dialog appeared, the device was not recognized in the same way, so I think it has something to do with the communication with the device driver as well.
I also tried changing the registry at that time, but it did not fix the problem. In the end, I deleted the RX5600XT sound driver and switched to the onboard sound device, and the hangs stopped.
But this time, msfs didn’t hang up after that…
My native language is not English, translated at DeepL
I’m using an external yamaha AG03 usb sound mixer device for all sounds.It has it’s own driver.
Ive done a full reinstall of the Geforce Nvidea driver too, without success. Got a Nvidea 2080GTX soundcard.
Never had problems since SU10 beta (3rd release). SU9 was causing heavy stutter, thats why I take part in BETA.
I am sorry. I guess my English is not good enough to communicate well.
I don’t think the sound driver has anything to do with this msfs dialog.
In my environment, after the dialog appeared, the graphics card was not recognized in the device manager.
This is a rare problem that has happened in other games, and in my environment, it was happening especially when I used the graphics card in the background.
This may not be fixable by us.
It has happened with both nvidia graphics cards and AMD cards, so I’m sure the developers will fix it.
I love msfs. It seems you do too. I hope it will be fixed, but I think you should wait until the developer fixes it. If you change the settings too much, you will break Windows.
I have had this CTD three times - at the moment I am testing limiting FPS in the Nvidia panel to 35 FPS - so far seems ok.
Not saying this is a fix - just commenting on my progress, Anyone else who experienced the CTD tried this?
I feel the same as you and love MSFS since FS2004 Yes , you may be right. We cant fix it, because it has nothing to do with our windows installation nor with our hardware. I think most have a common and actual PC and GPU, so it is just a programming failure that has to be fixed by Asobo. Anyway Ive written a Zendesk report.
I believe that reducing the performance is decreasing the possibility getting CTD or this erroro message. But if you try higer settings, complexer scenery or aircraft than the risk increase. Thats my expirience.
This is the first time I’ve had to look at this since the one and only previous time, and that flight resulted in this error. I’m absolutely confident that settings and RAM/VRAM usage has nothing to do with this.
I’ve just done a cold start up etc at inibuilds LHR in the Fenix A320 with live traffic (AIG models), live weather, GSX Pro and Navigraph all going. I’ve not changed my settings (which are effectively Ultra with TLOD of 250) since before .18 and in this example my VRAM was full the whole time in DX11. At close to 4K resolution it really doesn’t get much heavier at the minute than this in terms of performance draw. It won’t surprise anyone to know that there was no crash. I’m now airborne so we’ll see what happens.
This is nothing other than an issue in the game code introduced with .18 and later. I’ll keep saying it until I’m blue in the face…this has absolutely nothing to do with graphics settings.
ps My Nvidia GPU is overclocked (as it always has been) and my AMD CPU is undervolted allowing it boost to 5.1ghz. Again, the issue is the game, not our systems.
Ive tried it - but than I ve got average fps about 18 :-/ (with Kodiak 100 - which is payware and may use more fpm)… Of cause - its a beta and should only use default to test. But who uses default? Fact is, the more performance an addon need the higher the risk of this error message and CTD. Indepentend from the hardware, drivers or windows settings - Ive tried all - and without overclocking. My system is 2 years old an fits the specifications of MSFS (i7 with GTX 2080).
Usally I always had between 35-65 fps - before the last beta - and never had CTD/error.
Maybe there is also a Problem with the Kodiak 100:
When trying to start a flight in the Kodiak, I crash to desktop.
The main reason for this is running MSFS in DirectX 12 mode. DX12 is an experimental, incomplete implementation and therefore it could crash for unknown reasons. We recommend not using DX12 with the Kodiak. Another potential reason are nVidia’s latest drivers at the time of release. These have been known to cause crashes and FPS problems with MSFS in general, so we would recommend rolling back to the previous version.
I’ve been running the SU10 beta in VR in a mix of ultra and high settings until today with no issue. Amusingly, today I dropped all the ultra settings to high and had this graphics error window when I exited my flight to the main menu. Strange that it did it with lower settings!
With medium settings the chance to get this error is decreasing - with higher settings CTD are there more often. Also if using complex addons. So I believe that FSMS are not optimized to handle the GPU effective this time (since Beta .19 and till Beta . 21)
I was having this issue very single time I opened the sim… I’ve deleted the driver via DDU and install the 472.12, just made a 4 hours flight without any issue so far… I have 5600x with the GTX 2060Super and 32gb of ram…
”
