I have seen that in the past but so far with this version I can’t get the filters to work.
You just get 2 listed, RTX HDR and, RTX Dynamic Vibrance, none of these are useful for my setup.
You usually get about 20+ filters listed and I find the Colour, Details and Brightness/Contrast options enable me to adjust the image so I can see the cockpit and view the outside world without massive over exposure.
I’ve tried removing the driver with DDU in safe mode and reinstalling, checked the settings in the Nvidia app to make sure they are switched on and it’s just not working..
It’s a shame as the driver seems to be performing quite nicely on my setup fps/smoothness wise. Just can’t fly without the filters so I will have to go back to the previous version which was working fine.
Thanks, I did look at that a few years ago in MSFS 2020 but I could never get it to work. It was always asking me to allow permissions for the .exe file and no matter what I did I couldn’t get permissions for that file to work.
I’ve reinstalled the previous Nvidia driver for now and the filters are working fine.
Hopefully something will get sorted out with MSFS or Nvidia to allow them again in the latest drivers. If not I might have to revisit the reshade program.
The current temperature sensor read out bug can be dangerous since the fan curve will not work properly potentially overheating your GPU when temps are rising but the software thinks that temps are low and thus won’t speed up the fans.
My game crashed due to GPU overheating after some time playing with broken sensors.
You can reproduce the bug by sending your PC into stand-by/sleep whatever and then look at the temps. They are fixed on the value when entering sleep (not reproducable in HWINFO though).
There are already workarounds for this if you still want to use the driver and you will find them in this reddit thread:
One is by changing a setting in NVCP and another is installing a tool and running it once the bug hit you, both solutions will completely restart the gpu driver after sleep whoch will fix the bug until it hits you after another sleep mode.
The NVIDIA forum is also full of complains about this.
Personally I would recommend reverting to an older driver.
That’s interesting. The tempratures I see on my RTX 4090 right now are the same as they usually are with other drivers and I’m playing MSFS 2024 fully maxed out.
Yesterday, my flight was quite ok.
Today, it was a lot of stutters and something I’ve never encountered : the plane disappeared !!! The game was running but the plane, in the cockpit or in external view completely disappeared !!!
I rooled back to 566.14, did the same flight and did not encountered problems except it was not as smooth as before (was on 566.36).
I will roll back to 566.36 tomorrow.
I am not sure I understand what you mean it’s not reproducible using HWINFO?
I noticed when coming from sleep mode, starting the sim, and using the Alienware overlay to view GPU temps and fan speeds, they were both stuck with the fan speed showing 30% and GPU temp showing 30C.
I tried again coming from sleep mode and the GPU temp was stuck on 30C but the fan speed increased normally. Restarting my PC and all was back to normal.
However, everything looked normal when I looked at the sensor temps in HWINFO which I personally trust to give correct readings.
I don’t use afterburner and I can’t adjust GPU fan speeds with a curve using the native Alienware software. So, in my case I don’t believe I have anything to worry about.
What was your GPU temp when the game crashed?
Edited To Add: My Alienware Overlay is not correctly reporting GPU temps and fan speed even if not going into sleep mode. I updated Dell’s AWCC yesterday so it could be a problem with that or this latest driver.
I reverted back to Nvidia driver 566.14 because after installing the latest one, I noticed some stuttering in one of my games - specifically Elite Dangerous.
Well, how am I supposed to know when the temp sensor is not working?
What I do know is that I had two crashes after installing the new driver while I never ever had crashes in the SIM for months. Both crashes occured when the GPU temp was not readable (which I saw on the OSD data). The crashes did not crash the game entirely but a distorted messy image had frozen the display. I heard the game sounds going on from my speakers. So these were gpu-only crashes
But anyway I reverted back to the previous version and all is fine now. I will jump back on when a hotfix version is out.
In my case the Nvidia overlay is displaying correct GPU temps and fan speeds as well as HWINFO. I just completed a test flight that stresses the GPU and CPU and had no CTD’s. So I’m good and understand why you and others have reverted to an older driver.
I hope the hot fix will fix your issue and fix my Alienware overlay so that it reports the sensors correctly.
Yes as mentioned earlier, HWINFO is not affected. I do not use the Nvidia app so i can’t say anything about how it behaves after waking up from sleep mode. I use MSI Afterburner to undervolt my GPU, to apply a custom fan curve with options that are not natively supported normally and for OSD data. So for me this driver is obviously a no-go.
I had 2 crashes intermediatly. One with a complete system crash and one system freeze. I have now gone back to an earlier driver. Hope that helps. By the way: I am using a RTX 5080.
