Custom Resolution Utility (CRU)

[ToastyX]

(10-05-2017 08:13 PM)Archon75 Wrote:  3) Using CRU, I created a new detailed resolution of 3440x1440 @ 100.000 Hz (Hsync automatically set to 148.100). Results: less flickering, although still present, and no difference between Vsync on and Vsync off.

Don't add a new detailed resolution. Edit the existing one, and use "LCD native" to get the same 148.100 kHz timing.

(10-05-2017 08:13 PM)Archon75 Wrote:  4) Using CRU, I edited the l'extension block CEA-861 by adding a FreeSync value (it wasn't there) and setting it to 48-100 Hz. Results: as soon as I started the Windmill demo, the display went crazy, images were constantly appearing and disappearing. Had to press Esc to exit the demo.

The FreeSync data block is for HDMI only. Use the "Edit..." button at the top of the main window to edit the range limits for DisplayPort.

(10-05-2017 08:13 PM)Archon75 Wrote:  5) Using CRU, I edited the detailed resolution I had previously created and set it to Hsync 148.00 (so the resolution is now 3440x1440 @ 99.932 Hz); at the same time, I edited the extension block CEA-861, detailed resolution, and set Hsync to 148.00 here as well (so now the resolution shown is 3440x1440 @ 98.013 Hz). Demo results: light flickering, still present but not as heavy as before, no difference between Vsync on and off.

You don't need the same resolution in two places. I'm not sure which one FreeSync will use in that case.

(10-05-2017 08:13 PM)Archon75 Wrote:  Now, I am not that expert with CRU, but I am starting to believe that my issue is tied to these CRU settings... for instance, maybe the Hsync values (between Detailed resolution and Extension blocks) must be the same?

This should be working correctly out of the box. CRU really shouldn't be used to fix problems that shouldn't exist in the first place. Unless I know the specific cause of the flickering, I can't recommend any particular solution.

(10-05-2017 08:13 PM)Archon75 Wrote:  Unless... can it be an issue with the DisplayPort cable I am using? It was the one that came with the monitor, but I read somewhere that you might look for other (better?) cables. I have tried using a HDMI cable but the problem is still there.

It could be a cable issue, but if it's also happening with HDMI, then it's either a monitor problem or a FreeSync implementation problem in the graphics driver.