Custom Resolution Utility (CRU)

[ToastyX]

(07-08-2022 09:14 PM)NJDeac Wrote:  That's in the 120hz setting. Nothing shows up at all in the extension block section when the monitor is switched to the 165hz mode. I've attached an export of the default settings in 165hz mode.

That's with HDMI? The EDID as reported can't possibly work with HDMI, so it must be using DisplayID. I haven't seen a monitor use DisplayID with HDMI before. Try switching back to 120 Hz mode. Then edit the extension block and delete the "Extension override" data block. That will give you 3 bytes left. Then you can add a DisplayID extension block and try higher refresh rates in there. The monitor reports that it supports up to 40 Gbps, which should allow at least 1485 MHz pixel clock without DSC, but it also reports that it supports DSC, so you might be able to exceed that. I don't know what it will allow in 120 Hz mode.

[Nintendo Maniac 64]

Random thought - I don't suppose AMD's unofficial freesync-over-HDMI that predates and is signal-incompatible with HDMI 2.1 has anything to do with DisplayID over HDMI?

Or alternatively the opposite considering you're use of an Nvidia GPU - maybe HDMI forum VRR uses DisplayID?

Another thing I'm wondering is the whole "Gsync compatible" certification that LG TVs have - I wonder if it's actually not straight-up plain HDMi forum VRR but is in fact a slight variation of it whereby, when available, it prefers to use DisplayID?

[ToastyX]

(07-08-2022 09:54 PM)Nintendo Maniac 64 Wrote:  Random thought - I don't suppose AMD's unofficial freesync-over-HDMI that predates and is signal-incompatible with HDMI 2.1 has anything to do with DisplayID over HDMI?

Or alternatively the opposite considering you're use of an Nvidia GPU - maybe HDMI forum VRR uses DisplayID?

Another thing I'm wondering is the whole "Gsync compatible" certification that LG TVs have - I wonder if it's actually not straight-up plain HDMi forum VRR but is in fact a slight variation of it whereby, when available, it prefers to use DisplayID?

DisplayID is just a replacement for EDID. It doesn't affect the video signal or how VRR is implemented. HDMI uses the CTA-861 standard, and the CTA-861 standard says to use EDID 1.3.

[NJDeac]

(07-08-2022 09:51 PM)ToastyX Wrote:  Try switching back to 120 Hz mode. Then edit the extension block and delete the "Extension override" data block. That will give you 3 bytes left. Then you can add a DisplayID extension block and try higher refresh rates in there.

No dice - I edited the CTA-861 as you suggested and got the 3 bytes left, but adding the DisplayID block (tried both 1.3 and 2.0) didn't do anything (closed CRU, restarted display driver, checked monitor properties, NVidia control panel, and display settings for a new entry but nothing shows up).

Attaching a screen cap with the full set of settings for the DisplayID block in case there's some user error here.

[ToastyX]

(07-08-2022 10:35 PM)NJDeac Wrote:  No dice - I edited the CTA-861 as you suggested and got the 3 bytes left, but adding the DisplayID block (tried both 1.3 and 2.0) didn't do anything (closed CRU, restarted display driver, checked monitor properties, NVidia control panel, and display settings for a new entry but nothing shows up).

Attaching a screen cap with the full set of settings for the DisplayID block in case there's some user error here.

You're not doing anything wrong. There's something different about the monitor and the way NVIDIA's driver handles it. Try adding 3840x2160 @ 55 Hz to see if it shows up. Just want to see if it's ignoring any change.

[NJDeac]

(07-08-2022 10:53 PM)ToastyX Wrote:  

(07-08-2022 10:35 PM)NJDeac Wrote:  No dice - I edited the CTA-861 as you suggested and got the 3 bytes left, but adding the DisplayID block (tried both 1.3 and 2.0) didn't do anything (closed CRU, restarted display driver, checked monitor properties, NVidia control panel, and display settings for a new entry but nothing shows up).

Attaching a screen cap with the full set of settings for the DisplayID block in case there's some user error here.

You're not doing anything wrong. There's something different about the monitor and the way NVIDIA's driver handles it. Try adding 3840x2160 @ 55 Hz to see if it shows up. Just want to see if it's ignoring any change.

55 worked! I also tested various increments and everything worked up to 145. 146 and higher all failed.

[ToastyX]

(07-09-2022 12:32 AM)NJDeac Wrote:  55 worked! I also tested various increments and everything worked up to 145. 146 and higher all failed.

When you say failed, do you mean the driver doesn't add it? Then it must be some pixel clock limit. 40 Gbps is supposed to allow at least 1485 MHz, but it sounds like you're getting around 1440 MHz, which doesn't make sense for HDMI 2.1. You can still get 150 Hz under 1440 MHz if you try the different timing options.

[IIISi Z16 HF LE]

Guyyyyz
Iiiiiiiiiitttt woooooooorrks I just used HDMi 4 port and it suddenly started to work !!! aaaaaaaaaaaaaaaaaaaaaaa
But I think I have tried it I don't remember I had it connected in HDMi3 becsue my desktop PC perfectly works via HDMi 3 4k@120 vrr

But one thing I did yesterday I have installed official IIISi drivers from my support website of laptop and driver is from 22.3.2021
Before I have used that stupid intel driver support assistand and it updated to version 30 which is probably bad I will try it with that driver and see if they aded restriction !
When I turn HDR on it will revert back to 60 Hz but I don't use HDR so that's good !
BUT DAMN I AM HAPYYYYY !!

[chalermla24]

Having problem with audio formats, no matter what I set the display will use the audio formats from its edid. Trying to use higher audio depth. I'm Using Asus VG259qm via DisplayPort on RX580.

[ToastyX]

(07-10-2022 12:21 AM)chalermla24 Wrote:  Having problem with audio formats, no matter what I set the display will use the audio formats from its edid. Trying to use higher audio depth. I'm Using Asus VG259qm via DisplayPort on RX580.

The resolution you're using might need more horizontal blanking to transmit the audio format. Edit the detailed resolution matching the resolution/refresh rate you're using and try "Native (PC)" timing.