After battling this problem myself, I've learned a few things. Maybe this will help, and please correct me if any of this is wrong!
First off, this issue seems to be discussed in detail (with a few misleading comments) here:
https://www.reddit.com/r/nvidia/comm...gsyncfreesync/
This monitor isn't certified by anyone that it will work with an NVIDIA card through its FreeSync capabilities. That's gonna be the first thing the support people tell you.
The monitor has a "Game Mode" -> "Frame Rate" feature that I've mapped to one of the buttons to quickly show me the actual framerate the monitor is rendering at. This is helpful for debugging.
It's possible to change how the NVIDIA Freesync support behaves by making some changes to the EDID data (basically, this is the bit of monitor data that the OS uses to determine resolutions and such). You can modify this data with a utility called "Custom Resolution Utility", available here:
https://www.monitortests.com/forum/T...on-Utility-CRU
What you're going to want to do is modify or add a CEA-861 extension block so that it contains a new data block called "FreeSync Range". The value will need to be the frame rates that the monitor can support through NVIDIA's FreeSync compatibility layer. This is the thing that threw me off the most, as the other thread discussed dropping the lower range down really, really low... like to 40 Hz. This will have no benefit on this monitor and you'll continue to get blackouts and flickering.
The key thing that seems to understand is:
This monitor seems to not support Freesync for frame rates below approximately 65-75 Hz. This is the cause of the blank-outs and flickers!
Without any limits being set the drivers seems to be fine sending frames at any frame rate with FreeSync enabled, thus causing problems.
Once the frame rate drops below around 70 Hz I start to see some flicker. When the frame-rate hits below around 60 Hz, there is very noticeable flicker and dimming, and eventually the monitor seems to just go black briefly as it attempts to re-synchronize. (This can be tested with the pendulum demo and using the FPS sliders with manual entry)
Using this "CRU" utility it is possible to establish a "safe" range of refresh rates that will be honored by the NVIDIA driver.
The stable low-end seems to be around 76 Hz where I can't perceive any flicker.
The secret sauce to why this works seems to do with how the NVIDIA driver handles the situation when the frame-rate drops below the low end of the safe range. With the "Game Mode > Frame Rate" feature enabled it becomes a little clearer. It appears that below the lower end of the Freesync Range, the driver will just double each frame to achieve a frame rate within the safe range just before it sends the frame to the monitor! So 40 fps becomes around 80 fps according to the monitor. This seems to be the method it uses to ensure that even at low frame rates, the actual frames being sent to the monitor are within the defined range. Pretty clever.
And this is how I solve it:
Launch CRU utility and you should see a list of monitor profiles. For whatever reason I have three entries for my DELL S3220DGF. The first one will likely say "(active)". (I just apply this setting to all three, to cover the case where they might be used)
For each of the entries for this monitor, do the following...
Look for "Extension blocks" listed at the bottom
If nothing is listed, you can "Add..." an entry
If you already have an extension block listed, just edit the existing one (press "Edit...")
Once the editor opens, in the section labeled "Data Blocks" you will want to add a value for "FreeSync Range" by clicking "Add..."
The value you enter here for "Range limits" control the "range of refresh rates supported by the monitor for use with FreeSync enabled". I'm currently using 80-164. Remember, the video card and/or driver will double the number of frames being sent out below the lower limit to keep the actual frame rate within the defined range limit.
"Okay" you way out of the windows and exit the utility
(ADDED later): Make sure your windows desktop is running at 164Hz!!!! Not sure why this is needed but it seems to be needed, even for when it switches to full screen!
You'll need to restart the video drivers for the change to take effect... and in my case, I found that I had to disable and re-enable GSync support. Even after a restart the change didn't stick until I toggled the "Enable settings for the selected display model" (applying the change between toggles) NOTE: The only reliable way I have found to make sure the driver picks up the settings is by doing this, or using the toggle on the monitor to turn FreeSync on then off*!*
It's possible to use that pendulum NVIDIA demo to see the results of the tweak. Once these limits are defined, the frame rate reported on the monitor should be roughly doubled the reported range in the demo. So when you click the "simulate 40 fps", the display should show you around 80Hz with that "Game Mode > Frame Rate" feature on. Then, if you enable the FPS sliders, you can set a range of something like 60Hz to 100Hz.. you should see the actual frame rate go from the doubled value to the actual value when it hits that bottom threshold.
So there ya have it. With this setup it's not a perfect solution, as I still get periodic weird blips in menus in Overwatch and the likes, but it's vastly VASTLY improved the situation.
So instead of the menus running at 60fps, the monitor is now getting 120fps with freesync enabled, which is a stable refresh rate.
I hope this helps! It's been annoying and a painful path to discovery, but I learned a little about freesync along the way and now it works well enough that I don't have to rage quit out of menus of a game.
*UPDATE* Although this was working fine for me over the last couple of days I'm now seeing the flicker again. I'm having some trouble today getting the Pendulum demo to realize the proper refresh range. I'm continuing to research what's going on, but it looks like the NVIDIA driver might not be picking up the EDID overrides that are being set with the CRU. I'm pretty sure the EDID overrides are working, but it's something with the driver. So... YMMV...
*UPDATE 2* After lots of playing around with it today I found two things:
For this to work at all, I had to set my Windows desktop resolution to run at 164Hz! I actually noticed this had to be done for Fortnite to work with it a while back, but this seems to be the only way to allow the transition to work into Freesync mode, even to full screen.
Once it's enabled, after a reboot, I found that I had to toggle FreeSync off then on, either from the NVIDIA control panel, or more simply, using the FreeSync on/off option on the monitor itself. I just mapped it to a custom button to make it easy.
Another interesting find is that if you use the "restart.exe" programs that come with CRU, they will cause new monitor EDID entries to get created in the registry, and the list in the app. You can just delete those and only edit the top one (says "active"). This really bothered me as well. Good luck! It's a messy mess, but hopefully things will get better.
). Unele teste beneficiaza de refresh rate mare.
Linear Mode
Viziteaza-ne pe Facebook
Urmareste-ne pe Twitter
Vezi ce facem pe YouTube