The resolutions there are the same on both cases. But it is static and not the timings that I'm running in the moment.k2viper wrote:Nvidia control panel is known as innacurate in reporting exact refreshrate timings. I recommend using CRU to find any differences in current (240hz) refreshrates under Extension blocks.
But, should resulutions under CRU ever be different when freesync/gsync is monitor enabled?
If I turn on the monitor using my Macbook Pro (RX 560) running Windows and DISPLAYPORT adapter it fixes the problem immediately even when Freesync is off. Using the default apple usb-c to HDMI it did not fix the problem (the HDMI of the adapter don't support freesync and is limited to 144hz). If it is running on OSX then the monitor got overshooting even using displayport.
It persists after I remove the macbook cable and plug the desktop, the display stills good and softMCCS reports the same values it reported when I have enabled and disabled g-sync.