Try rebooting your computer. I didn’t have it until i did that.
Thanks for the suggestion. I had actually restarted my PC after Rebar switching in the NVIDIA App wasn’t working the first time and before my post: no go. After your post I restarted again but again no go. Restarted again and enabled Rebar in BIOS and the option to change the Rebar setting became available in the NVIDIA App.
So in the case of my ASRock X670E PG Lightning motherboard at least, IT SEEMS Rebar has to be enabled in the BIOS to enable NVIDIA App to do Rebar switching.
I am getting more flickering on side screens (triple monitor) with this driver.
5090 / TAA / Max Frames 30 / FSR FG 3.1 x2 (target 60)
I’ve noticed the same with my Quest 3 on VD, when I first start a VR session it’s just a blank image with MSFS sounds coming through, If I go back out of VR then back in it’s okay, so rolling back to the previous working driver.
Same setup as you but running DLSS Qualty and I’m not seeing any flickering on the side monitors. Two flights in and so far no issues for me.
For anyone experiencing flickering as I was with 616.56, go into Settings - System - Display - Colour Management and change ‘Automatically manage colour for apps’ to On if it was Off. It stopped the flickering for me.
Pro tip:
As we know, Resizable BAR works well with MSFS 2024. But we don’t only play MSFS 2024 - many of you also play other games and you may be wondering how to check whether a particular game is configured to use Resizable BAR.
This is where NVIDIA Profile Inspector comes in handy.
Releases · Orbmu2k/nvidiaProfileInspector
Simply enter the game you’re interested in into the search field
and check the “Resizable BAR (rBAR)".
If it shows Enabled, the game is configured to use Resizable BAR.
If it shows Disabled, it isn’t.
Hello,
For me, MSFS 2024 don’t works with this new NVIDIA driver.
MSFS is locked on the first screen and never starts when i come back on driver 610.88 all works fine.
Try clean install via DDU
How to > https://forums.flightsimulator.com/t/nvidia-geforce-game-ready-driver-610-62/768896/3?u=tenpatrol
Exactly the same issue for me.
And that was with a clean install using DDU (in safe mode).
I’ve reverted back to 610.47
I am glad that it is not just me that has this issue.
I have spent 2.5 days now, including 4 system restores. I eventually proved to myself that it was the driver. It did not get past the main screen, once I left it for 50 mins but nothing happened.
Now I have tried, deleting reinstalling Gaming Services, deleing reinstalling Xbox App, deleting reinstalling MSFS2024, and finally doing a Windows 11 recovery build.
Works fine with 610.74, fails miserably with 616.56.
Now the only things to note here is that I use the driver package that has been run through NVCleanstall. I have been doing this for a couple of years without any issues. When it fails and I fall back I then get a Windows error on every reboot. Nothing seems to be major with that requestor as everything seems to work but this explains the 4x restores.
My current thinking is that something has changed in the new driver structure that NvCleanstall doesn’t yet take into account, however I have no proof on this yet. I have checked if there is a new version but there is none so far.
So my question is for the people that have it working, how did you update, Nvcleanstall, Nvidia App or direct download?
Direct download with a DDU clean first, it’s working great for me.
Thanks for the reply. One of the things I tried was using DDU, but it did not work.
Direct download.
-
Download NVIDA Driver 616.56
GeForce Game Ready Driver 616.56 | Windows 11 | NVIDIA -
Uninstall NVIDA driver via DDU and restart PC.
How to > https://forums.flightsimulator.com/t/nvidia-geforce-game-ready-driver-610-62/768896/3?u=tenpatrol
There’s a new version of DDU available, so please download the latest version rather than the old version linked above.
Download Display Driver Uninstaller (DDU) 18.1.5.7
Display Driver Uninstaller (DDU) V18.1.5.7 Released. - Wagnardsoft Forum -
Install NVIDIA driver 616.56 - restart PC.
Thanks. I have tried that, but now my system backup is new with all Windows updates and MS Store updates, maybe I will try something along those lines again. A failure is a lot quicker to recover from now.
P.S. Yes I have the latest version of DDU.
Me too. I’ve rolled back to 610.88. Seems to be quite widely reported at NVidia with a 0.1s flicker every minute or so.
I updated through Nvidia app, express install. Deleted caches and shaders and rebuilt shaders in the app after installing. No issues here.
Thanks for the info.
I have done some searching and there seems to be quite a lot of reports with either a game getting stuck on opening screen or crashing. I even found a report that FG was affected.
The reports are mainly about the GRD but the NSD is not without its problems. The general status seems to be if you get affected then fallback. Somebody using the NSD found that their app would crash, they did manage to find away around it by going back to the old driver, then uninstalling their app, then reinstalling the new driver and finally reinstalling the app and it works fine.
I don’t think that I want to upgrade bad enough to go through that rigmarole.
My instincts tell me that there will be a hotfix fairly soon.
I haven’t updated the driver on my flightsim rig yet, but guess I’ll wait because I did update to the 616.56 studio driver on my other pc (my old flightsim rig) and I got periodic screen flickers with this driver that persisted across reboots and over several days, so I just rolled back to the previous driver a few hours ago and haven’t had a flicker since.
I know this thread is about game ready driver but since this studio driver is the same version number and also has flickering, I thought I would mention it.
I did see a post above in this thread saying a color management setting change fixed the ficker, but I could not find a setting with that name in the nvidia app on this pc which has a 3090 card.