Changes in the CRU do not apply (V rate)

[Makchiken]

(04-12-2025 06:57 PM)ToastyX Wrote:  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.

I tried that too... unfortunately also without results.
Anyway, thank you so much for your time and for trying to help me.

Upd. I was able to get it works
All I had to do was add DisplayID 1.3 with my resolution and frequency to the extension blocks instead of the default grey block

[ToastyX]

What is the default grey block you're talking about?

[Makchiken]

(04-12-2025 08:54 PM)ToastyX Wrote:  What is the default grey block you're talking about?

I removed the default extension block and created a DisplayID 1.3 block, sorry if I didn't formulate the sentence correctly

[ToastyX]

What version of CRU are you using? Are you using the latest 1.5.2 and not 1.5.1? There shouldn't be a default extension block. NVIDIA will ignore all changes if one exists. There should have already been a DisplayID extension block.

[Makchiken]

(04-12-2025 10:07 PM)ToastyX Wrote:  What version of CRU are you using? Are you using the latest 1.5.2 and not 1.5.1? There shouldn't be a default extension block. NVIDIA will ignore all changes if one exists. There should have already been a DisplayID extension block.

I'm using version 1.5.1
is there a version 1.5.2 yet? looks like I missed it

upd. tried version 1.5.2, everything works as it should!
It turns out the whole problem was my inattention...
Thank you so much for your patience!