in windows setting — GPU planning off and settings like screenshot (sorry it is German, before it was on high performance =hohe Leistung but now on “windows”:
Than I switched in MSFS to “high end” settings and from DX11 back to DX12 (before that Ive swichted from DX12 to DX11).. Of cause new start of system and FS included…
I m flying now for a while, but as always, there can be a surprise: tomorrow the error may be back again… very strange…
Yes i have found turning off the Hardware accelerated GPU scheduling has worked for me for the moment, i have been able to put the options back to DLSS - Balanced - and been able to load in to the sim with no issues earlier on
just to say my specs are:
AMD Ryzen 5 3600 CPU
Geforce RTX 2070 GPU
16GB 2400Mhz RAM
Same here, sometimes yes, sometimes no. And if they are on this, they might fix sound issues during launch, there are short time spans where sound gets pretty loud and back to normal shortly. Doesn’t really impact simming but gives the software an nonprofessional touch.
not really, its true that the sim uses up to 10 GB VRAM as a minimum with Epic Settings in DX11, But the Error also happens in GPUs that have 16 GB and also 24 GB in 3090 & 3090 Ti, so as for AMD.
you can even try the Beast RTX 4090, it will have the same issue because its not a hardware bug its a programming bug.
I have completed two flights now with no CTD. Whatever I did seemed to have worked. I removed all permissions from all three microsoft edge folders and any other edge folder I could find. (C:\Users(Username)\AppData\Local\MicrosoftEdge) and (C:\Users(Username)\AppData\Local\Packages) were the only Edge folders I could find. Uninstalled Edge WebView2 runtime. I also disabled MSI afterburner clocking at startup. Reset it back to stock and re enabled all of the overclocking settings and enabled apply at startup. Doing good so far in DX11.
Make sure to have another web browser installed and restart your PC once you disable permissions.
You have to take ownership in advanced settings, disable inheritance, select the top option in the pop up box and then delete all permissions.
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes.
Provide extra information to complete the original description of the issue:
Whenever I move the camera quickly while flying, the error message pops up and the sim crashes. It has happened several times within two hours.
Are you using DX12?
No.
Are you using DLSS?
Yes.
If relevant, provide additional screenshots/video:
Care to provide a citation of them being “aware of” it, beyond just giving us incorrect info about the problem and then failing to acknowledge us at any point since?
"I donT know, but I believe, NOBODY of us have a real vanilla FS…!? Even when we rename the community folder - there are still add ons in the official folder, if we have bought somethink out of the marketplace store and many payware addons installing them in the officia folder. "
You believe so incorrectly. I have not purchased anything from the store. I have only one single payware addon so far, and that addon was purchased outside of the game and installs by hand in the community folder. So I have stock MSFS, and I still regularly get these CTDs with no rhyme or reason as to when.
The changes you are making are having no effect whatsoever. It’s an intermittent problem, and you’d have been able to play for those same periods without a single crash had you not made any changes, too.
Two flights without CTD is not enough to say you’re clear. Breathe easier when you’ve had no CTDs for a couple of weeks. I can go a fair few flights in a row or perhaps even a couple of days in a row with no CTDs, then get several in quick succession despite full reboots in between.
removal of the nvidia shader caches we mentioned daaaayyysss ago, and I assume all users tried that in meanwhile ( %LocalAppData%\NVIDIA\ DXCache + GLCache )
Hello. Sorry, but i did not read all the 857 replies to this topic to check this (and i guess in the beta step, this advice was also proposed). The last answer from DeFjeuber was good to me. And normally, it is up to Nvidia drivers to update the shader cache a soon as a shader has changed in a program, so will check if it helps, but normally, you don’t have to delete the DX shader cache. However, as this operation is non intrusive i think it is a good advice.
( %LocalAppData%\NVIDIA\ DXCache + GLCache )