Post Reply
Changes in the CRU do not apply (V rate)
04-12-2025, 01:26 PM
Post: #1
Changes in the CRU do not apply (V rate)
Hello everyone, I hope someone can help me
I'm trying to narrow the adaptive sync range (freesync) in CRU (48-170Hz ---> 70-170Hz)
I'm doing everything right (CRU, "Edit..." button at the top near the active monitor, edit V rate, "Include if slot available" enabled, save (ok x2), restart64(or restart PC)
But no matter how much I try to edit v rate - the settings are simply not applied by the monitor (I checked in tests/games, before/after edits - no changes), although in CRU everything is saved without problems
Maybe someone has any thoughts on this? Monitor Asus Tuf Gaming VG27AQA1A (1440p, 170Hz, VA), GPU RTX 3070 (Driver 566.03), displayport, Windows 10
Find all posts by this user
Quote this message in a reply
04-12-2025, 02:13 PM
Post: #2
RE: Changes in the CRU do not apply (V rate)
What sort of change are you expecting? NVIDIA should apply LFC below the range. How are you testing the range?
Find all posts by this user
Quote this message in a reply
04-12-2025, 02:42 PM
Post: #3
RE: Changes in the CRU do not apply (V rate)
(04-12-2025 02:13 PM)ToastyX Wrote:  What sort of change are you expecting? NVIDIA should apply LFC below the range. How are you testing the range?

I test the range in the AMD FreeSync test (wind generator) and in the game (zzz for example)
In theory, changing the lower range from 48 to 70, LFC should turn on up to 69, doubling the monitor's Hz, right?
But this does not happen after changes in the CRU
Setting the lock to 60 frames in the test or in the game, I do not get LFC 120 Hz
With the default range of 30 fps - LFC 90 Hz (x3), 45 - 90 Hz (x2) and so on, after 55 fps LFC turns off in my case
After changing the range, nothing changes, everything remains exactly the same
I want to change the range to minimize screen flickering when the frame rate fluctuates with gsync on
Find all posts by this user
Quote this message in a reply
04-12-2025, 02:49 PM
Post: #4
RE: Changes in the CRU do not apply (V rate)
Run reset-all.exe and restart. Then run this and post the edid-test.txt file here: https://www.monitortests.com/edid-test.zip
Find all posts by this user
Quote this message in a reply
04-12-2025, 03:48 PM
Post: #5
RE: Changes in the CRU do not apply (V rate)
(04-12-2025 02:49 PM)ToastyX Wrote:  Run reset-all.exe and restart. Then run this and post the edid-test.txt file here: https://www.monitortests.com/edid-test.zip

done, here is the test result


Attached File(s)
.txt  edid-test.txt (Size: 1.2 KB / Downloads: 10)
Find all posts by this user
Quote this message in a reply
04-12-2025, 03:54 PM
Post: #6
RE: Changes in the CRU do not apply (V rate)
There is a FreeSync data block in the extension block. Does editing that have any effect?
Find all posts by this user
Quote this message in a reply
04-12-2025, 04:09 PM
Post: #7
RE: Changes in the CRU do not apply (V rate)
(04-12-2025 03:54 PM)ToastyX Wrote:  There is a FreeSync data block in the extension block. Does editing that have any effect?

Sorry, i'm a complete newbie to all this
What do you mean? What can i try to edit?
Find all posts by this user
Quote this message in a reply
04-12-2025, 06:02 PM
Post: #8
RE: Changes in the CRU do not apply (V rate)
In the CTA-861 extension block, there is a FreeSync data block. Does editing the range there have any effect?
Find all posts by this user
Quote this message in a reply
04-12-2025, 06:27 PM (Last edited: 04-12-2025, 06:29 PM by Makchiken)
Post: #9
RE: Changes in the CRU do not apply (V rate)
(04-12-2025 06:02 PM)ToastyX Wrote:  In the CTA-861 extension block, there is a FreeSync data block. Does editing the range there have any effect?

ahh, yes
if I'm not mistaken, then this is the block responsible for hdmi
I also tried to edit 70-170 Hz in it and unfortunately this also did not change anything
Find all posts by this user
Quote this message in a reply
04-12-2025, 06:57 PM
Post: #10
RE: Changes in the CRU do not apply (V rate)
The only thing I can think of is maybe NVIDIA put in a specific workaround for this monitor and is preventing changes to the range. In that case, sometimes changing the device ID ("Edit..." button at the top) to something else such as ABC1234 would allow changes to take effect.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 1 Guest(s)