I just tried it and as you described a dialog box popped up warning developers not to develop new things for the marketplace with this version of MSFS. I clicked “Don’t show again”, moved on and my mouse continues to work normally.
Sounds like it might be a glitch in your system.
Are you using an increased resolution?
Yes. 2880 x 2160 with DLSS (quality), my 32" HDTV does an excellent job of downscaling it to it’s erstwhile native 1080p . Performance is about the same as 1080p TAA but with a better than 1440p picture. Even recording isn’t a problem as OBS can downsize it on the fly.
DLSS + DLAA does much the same thing but to my eyes the texture filtering is considerably inferior on larger 1080p monitors.
Just trying to see if Bodobear70 has the same issue is all.
1 Like
Hi Salem, I could get into the Developer Mode just switching into windowed mode and return to fullscreen after activating.
Thanks for the help !
I´m running the sim with my 1080Ti now in locked 30fps / 1440p in Ultra settings. Seems like the graphic card error is gone for now.
In the FPS activity window from the developer mode my graphic card is using only 4gb of the 11gb gpu ram. Maybe I can chose any higher setttings like higher locked fps or higher resolution until the graphic card is getting to the max ? Anyway everything is looking nice now and playable in 30fps.
Sorry Salem … I was obviously half asleep
Haven’t tried SU11 yet.
Is this still a problem?
It shouldn’t be if you take the steps to guard against it. Hags off, gpu overclocks undone and if needed rollback a driver or two. It also helps if your gpu isn’t constantly at 100% usage so consider a frame cap.
I’m not getting this while playing it happens when on the load screen when starting a flight, usually when the loading bar hits 75-80%. I’m not even close to 100% GPU usage
I still don’t see it when using DX12 but i still can’t start a flight on DX11 without that message and a CTD. Not a huge deal but I get worse performance with DX12 so I’d like to switch back eventually
1 Like
Without framecaps the menus are worse than anything. As far as I can make out there is a driver issue still to be resolved by Nvidia where some cards are reporting wrong voltages for memory chips and hitting fly or even flying into heavy clouds could be enough to trigger a fault. A slight overvolt might help but it’s entirely at your own risk.
This issue was around before SU11 .
It just seems SU11 has made it worse.
So here it is the real reason lots of you are having problems with recent Nvidia drivers:
More fps = considerably more stress particularly on the non processor parts of your graphics card e.g. memory. MSFS not mentioned but Cyperpunk +18% is a big indicator.
Newer Nvidia drivers bring significant gaming performance boost to RTX 30 GPUs | KitGuru
I also imagine this is not just confined to the 3 series.
1 Like
That in mind, I hope THIS is just confined to the 4 series!!
Nvidia investigates melting graphics card cable reports - BBC News
1 Like
3 Likes
Now I don’t suffer from this unless I’m testing out my usual (modest) overclock but this definitely helps.
If your own card doesn’t have similar software there is always Afterburner, just tweak the voltage slightly and leave everything else at their normal setting … As I said earlier, it’s entirely at your own risk and if you are considring an RMA then leave it alone as this will likely void your warranty.
Yep, I’m still getting this too. Just crashed with the nonsense “overclocking” message (never have, never will be, nor is it a factory-“overclocked” card, just a bone-stock 3060) about 75% through loading my first flight since reboot (first flight in days, actually) with identical settings, aircraft and location that I’ve used with no issues flying for multiple hours in VR previously.
Asobo, PLEASE FIX THIS.
2 Likes
Corrected for you, in the meantime turn off Hags in Windows
right now NVIDIA has Updated… pls Update your driver and run the game. hope now works MSFS without the Warning!
Which version is it?
AMD users have had the issue, my last Windows install* turned HAGS on default so I had not realized I had been using it (without getting the message). There’s no gotcha or at fault … at least if there is I’ve seen no conclusive proof of it?
*I refresh Windows often, multiple drives makes it simple and quick.