-Switching to full screen doesn’t help
-Reinstalling Nvidia drivers doesn’t help
-Clearing/disabling rolling cache doesn’t help
-Turning HAGS off doesn’t help
Asobo it’s your turn. It can’t be that hard to reproduce this error.
-Switching to full screen doesn’t help
-Reinstalling Nvidia drivers doesn’t help
-Clearing/disabling rolling cache doesn’t help
-Turning HAGS off doesn’t help
Asobo it’s your turn. It can’t be that hard to reproduce this error.
So all is needed now is patience for the patch, because while the sim can work fine sometimes, it is not sauitable for everyone to take a risk & to lose a hours of flight due to the bug.
However, all the sim gets more advanced and leveling up, so with complexity, it will be an understoodable thing to have some bugs or errors here and there, sometimes.
having that said, MS Fligh Simulator Still the Ultimate Experience in the 0’s & 1’s Computing World .
So was I … used to have a 1080 installed 2 monitors … not having the issue recently
Bought the 3060 replaced the 1080 2 monitors … not having the issue ever
The 3060 has only been installed for a couple of days the 1080 was 6 or 7 years old.
After the last SU10 update, after choosing aircraft and airports (or loading a flight plan) on loading MSFS reports the error below and closes after a couple of seconds. I relaunch the simulator, without restarting the pc, and this time there is no problem.
I have not overclocked anything. It happens regularly.
In the event log, the executable that caused the error is the one from the sim
Updated nVidia drivers and I do not have NGExperience.
Do you have any idea what it could be?
It’s a well documented error, which Asobo are aware of.
a guy sure hopes so!
some feedback from them would be nice…
“hey guys, ■■■■ sucks we know, but we got this! fix is on the way!” …or something…
Beside the Gpu bug in SU10, & the release notes being missing inside the simulator, that will be fixed in the upcoming updates & patch, it will be nice to fix the missing backgrounds when the sim launchs, because not always they will appear, sometimes yes and sometimes no. & a always yes will be nice
Another non vital issue, but it will be nice to smooth & boost, the lag that it takes the aircraft untill to be fully shown, its true the lag is only seconds, but ultimate smoothness is always a nice thing to have. maybe increasing the resources that the sim uses from the system will boost this up a little bit, because i dont think the lag is due to a lack in specs.
my specs:
8 cores cpu up to 4.5 GHZ in all cores.
32 GB Ram 3200 Mhz running in Dual Channel.
16 GB GDDR6 up to 14000 Mhz Memory speed, RTX 3080 GPU Runnig @ 1700 Mhz.
Samsung SSDS in Raid 0 with Hyperdrive Technology that boosts the storage speed up to 10.5 Gb/s.
This is the thing…why the silence? First rule of customer service is, even if you don’t care about your customers, at least pretend that you do. Otherwise you appear to be ignoring them, and that’s not a confidence builder.
We know that they’re PROBABLY working on the issue, but they’ve never said definitively that they are, as far as I know. It would be nice just to get some word from them.
It must have t do with a failed GPU Management of MSFS
I had three time a crash at the same situation and scenery/plane. I think it is importtant to make a full start of your PC to avoid one more CTD. Now I-m flying after new start of my PC without problems, but so it has not to do with scenery, add ons, etc.
Have used Asobo / CERENADO Cessna 195 , default scenery (Canada SU) and some addons like VFR Objects and powerlines / solar … But anyway, even without any mods the error can appear.
Ok - now the fourth time this error
this error appeared several times with me. these are some situations that contribute: scenery loading during flight (mostly add-ons), abrupt camera moves and changing views. When i have a youtube video on background, it´s 100% sure that will happen. i guess it´s something related to SU10, it never happened before the update.
OBS: No overclock, last driver installed and no overheat. Texture resolutions at Medium, 5gb of 6gb vram usage
Many posts here.
Don’t forget to try what helped me and others previously
1 Disabling Hardware Acceleration GPU scheduling
2 Disabling Game mode.
Mats
I have had both of these turned off for some time and still it crashes.
yea, changing settings wont help, the randomity of the error can give some hours of flight without interrupting with crashs, while many think that the settings they have changed did the fix.
Agreed. A lot of “magic cures” being tossed out in these forums, but the fact is that one day you can play the game with no issues, yet the next day, without having made any changes whatsoever to the game or your PC, you can have CTD and/or fps drops.
On Sunday I had a good day playing with no issues. The next day, Monday, I had to reset/reload my flight twice because of fps drops to low teens, and then a CTD. Tuesday, a great day again with no issues. What changes had I made to my system or game? Absolutely nothing.
I run three monitors on the 3070 and do not get this popup.
Why is there so much silence from Asobo and Nvidia with this particular problem. Its almost like nobody wants to take responsibility for the problems we all seem to be having. Totally agree that the problem is extremely inconsistent to the point it is a luck of the draw whether the sim will fire up today or not. Never had this issue till the last update and previously ran on ultra. Now I’m down to High End and still am getting the same error message.
Hi there,
Since the SU10 update, I also have this problem:
Here is my config: Intel I12700KF - 64Gb DDR4 RAM - MSI GForce RTX 3090 - NVMe SSD - Windows 11
Lookin at the steam db site I see that they have uploaded nvdida_2 along with a few other things in the last 15 hours, so maybe just maybe, there close and we’ll see a patch soon.
So i checked my crash logs (DX11), and guess what ? The error seems to always refer to the same compute shader “compute_01” shader-hash: 4456501539687578903
It seems to me more than a coïncidence… And if i read the previous posts, it is the same shader tag involved in the crashes for other users (cf. Warning: Your graphics device has encountered a problem - #644 by PL4444)