(01-27-2026 07:46 PM)EeK Wrote: [ -> ]What are VICs?
VIC = Video Identification Code
These are numbers defined in the CTA-861 standard to define specific signal modes without requiring Detailed Timing Descriptors (DTDs).
For example, VIC #118 means 3840 x 2160 @ 120 Hz for the graphics driver (with specific predefined timing parameters). VICs are displayed in CRU as
TV resolutions and can be added or removed as such. Anything not included in the CTA-861 standard cannot be added in the CTA-861 extension block if it would have a pixel clock higher than 655 MHz. This is why the input fields turn red when you attempt to define such a DTD in the CTA-861 extension.
(01-27-2026 07:46 PM)EeK Wrote: [ -> ]Never deal with the issue of Nvidia's driver ignoring EDID overrides when DSC is active and the maximum resolution and refresh rate combination exceeds the GPU's single-head pixel clock limit, since I have a 4000 series card.
As far as I could determine experimentally with an RTX
30 card, ignoring an EDID overwrite depends solely on this pixel clock limit (1350 MHz). DSC itself plays no role.
(01-27-2026 07:46 PM)EeK Wrote: [ -> ]I believe DSC is active at my display's maximum resolution and refresh rate combination (3840x2160 @ 144 Hz) with Full RGB 10-bit (necessary for HDR). The goal was to create a new ultrawide resolution (1600p) still running at 144 Hz with Full RGB 10-bit, but without the need for DSC.
The raw EDID of the S90F shows that 3840 x 2160 @ 144 Hz corresponds to the CVT-RB standard (1332.75 MHz). This works at 8-bit without DSC. It's a close call. However, it's true that the TV needs DSC if you want to output 10-bit (HDR). The interface shows a maximum of FRL5 (40 Gbps). At 10-bit, the signal would be at
112% of FRL5.
You can check it here:
https://tomverbeure.github.io/video_timings_calculator
3840 x 1600 @ 144 Hz is no problem. The original EDID shows 987.25 MHz. That's also CVT-RB. At 10-bit, that means
83% of FRL5.
(01-27-2026 09:38 PM)kristianity1977 Wrote: [ -> ]As soon as I do the regedit and import the EDID, HDR is showing as working still, but it isnt working in games and RTX HDR vanishes from the Nvidia APP and doesnt work in the Nvidia Overlay.
Ah, okay, I see.
With the test setup described above and my RTX
50, I see "RTX HDR" both with the EDID override and with
EnableTiledDisplay = ZERO.
The signal diagnostics of the LG TV I'm using for testing also show the reception of an HDR10 signal (see attachment). I can also see it visually. However, I'm not a gamer, so I can't test any games.
Unfortunately, I don't know why the Nvidia driver is behaving this way for you. Only Nvidia themselves can probably explain it in the context of games in full-screen mode. You can, of course, experiment with the EDID and, for example, remove unnecessary parts. That might make a difference.