(09-29-2024 08:46 AM)christpunchers Wrote: [ -> ]I see. Has this always been the case (perhaps there’s an older driver that doesn’t ignore EDID override)?
I don't know because I don't have the hardware to test it myself. Someone mentioned an older driver working but I haven't been able to confirm it. I first heard of the problem over a year ago, and there were some major changes to the driver after 528.49, so maybe around that version, but older drivers might not support your GPU, and Windows Update is a pain and will automatically update older drivers.
Hi Toasty!
Thank you so much for the prompt response. I actually away from home right now so I don't have access to my monitor (it was connected to my laptop via DisplayLink dock and HDMI). With that being said, I'm currently testing just on my laptop's internal display and it doesn't seem to work either. The output of the exe program for this case is:
DISPLAY\LEN40A0\4&1A7D5A82&0&UID265988:
00 FF FF FF FF FF FF 00 30 AE A0 40 00 00 00 00
00 1A 01 04 95 1F 11 78 E2 7E 45 93 55 53 94 28
23 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 DA 1D 56 E2 50 00 20 30 44 2D
47 00 35 AE 10 00 00 18 E1 17 56 E2 50 00 20 30
44 2D 47 00 35 AE 10 00 00 18 00 00 00 0F 00 8C
09 30 8C 09 30 16 09 00 0D AE C3 14 00 00 00 FE
00 4E 31 34 30 42 47 41 2D 45 41 33 0A 20 00 4F
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(09-29-2024 03:41 PM)ToastyX Wrote: [ -> ] (09-29-2024 02:30 PM)mrmonitor Wrote: [ -> ]I have been trying to use CRU to add resolutions to a 3440x1440 monitor to no avail (I cannot see the custom resolution in the Windows resolution settings). I am trying to add the resolution 2734x1824.
I have tried adding this resolution multiple times using different methods. I've added it to every single entry (Display1.3, Display2.0...) and it doesn't work. I've also added it to detailed resolutions and it doesn't work. And yes, I have tried both restarting my GPU using the given exe, and in fact I even tried restarting my computer, all to no avail.
Does anyone know what the issue in my case might be?
Also, I use an Intel UHD 620 for graphics. I have tried the export method already.
What monitor is it and how is it connected? (HDMI? DisplayPort?) Run this and post the edid-test.txt here: https://www.monitortests.com/edid-test.zip
(09-30-2024 02:25 AM)mrmonitor Wrote: [ -> ]Thank you so much for the prompt response. I actually away from home right now so I don't have access to my monitor (it was connected to my laptop via DisplayLink dock and HDMI). With that being said, I'm currently testing just on my laptop's internal display and it doesn't seem to work either.
DisplayLink products use a proprietary method to transfer video over USB using their own driver, and their driver does not support EDID overrides. CRU should work if the monitor is connected directly to the laptop.
Laptop displays normally don't have scalers and can only display the native resolution, and Intel's driver often ignores EDID overrides for laptop displays. CRU should work for external monitors though.
I've done some further testing with the XG27UCS monitor (using HDMI 2.1 cable) that I thought worth reporting since my last
post.
1. At 720p it seems that the lowest accepted Horizontal Blanking is 80 pixels (same as CVT-RBv2), anything lower results in blank screen.
2. Vertical Blanking must be at least 11 lines.
3. Maximum Vertical Back porch is limited to 2047 lines.
4. Although lowering the input lag might not be very significant (I can't really detect a difference) by increasing the vertical totals (
QFT) at 1440p, 1080p and 720p resolutions by adding them (in addition to 4k) in the DisplayID 1.3 extension block, there is a benefit of having faster transition when changing resolutions. I'm not sure if this is something related to Windows, but switching between these four resolutions happens almost instantly more often when all four 158Hz resolutions are present in the DisplayID 1.3 extension block than when it's only the 4k resolution. I'm not sure if those resolutions with their increased vertical totals are actually used, it could be that the 4k 158Hz resolution values are used for everything else, but it seems there is some benefit of having them added.
[
attachment=1430] [
attachment=1426] [
attachment=1427] [
attachment=1428] [
attachment=1429]
Edited with some further testing.
Hi all!
I'm sorry if that question has been already resolved, but I've searched it through several sites and couldn't find a solution.
I own a Samsung S95C from last November and recently a new gaming pc with a RTX 4070 Super.
TV and PC works correctly but I have two problems with resolutions:
1) nVidia settings panel, doesn't allow me to set a custom resolution (it's grayed out). I have tried different things and none of them works. Thats the reason I ended up here, trying to use CRU to get custom resolution for my TV.
Reading the forum, I think that's because it's using DSC over HDMI 2.1 and DSC automatically disable custom resolution on nVidia panel?
2) If I want to output 1440p resolution, I can do it, but only at 100, 120 or 144 Hz on nVidia panel. It doesnt offer me and 60 Hz option, with has no sense as I can set 1080p@60 or 2160p@60 with no problem, but for some reason, no option to 60 Hz at 1440p.
The TV works perfectly at 1440p@60, as I tried with PS5 or Xbox and works fine.
I opened CRU and tried to add the custom resolution I want (1440p@60). After restart several times app and computer, it doesn't matter, on nVidia panel I can't find that new resolution. I'm using Windows 11 by the way.
In Windows, even if I don't use CRU, I could setup 1440p@60, but it's not real, Windows use 3840x2160 and downscale to 1440p.
The reason to try to use 1440p@60 (or 2160p@60) and not 144 Hz (the max of the panel and the apparently better option) its because OLED panels at more than 60 hz on several games, flicker a lot (for example Alan Wake 2).
Please, it's giving me mad that a simple thing as select a basic 'native' resolution as 1440p@60 hz its no possible to do in windows, in nvidia app or in CRU. ¿Someone know what I'm doing wrong or it's this a bug with nvidia drivers or?
I really don't know where to report that or how to fix it. Maybe another S95B, S95C or S95D user here with same issue?
Thanks a lot in advance!
(10-01-2024 05:08 PM)Solid Wrote: [ -> ]1) nVidia settings panel, doesn't allow me to set a custom resolution (it's grayed out). I have tried different things and none of them works. Thats the reason I ended up here, trying to use CRU to get custom resolution for my TV.
Reading the forum, I think that's because it's using DSC over HDMI 2.1 and DSC automatically disable custom resolution on nVidia panel?
2) If I want to output 1440p resolution, I can do it, but only at 100, 120 or 144 Hz on nVidia panel. It doesnt offer me and 60 Hz option, with has no sense as I can set 1080p@60 or 2160p@60 with no problem, but for some reason, no option to 60 Hz at 1440p.
NVIDIA's driver disables custom resolutions and EDID overrides when DSC is active if the pixel rate is beyond a certain point, and DSC can affect what resolutions and refresh rates are available. These are issues NVIDIA needs to resolve. The only way around this is to disable DSC. It's possible to disable DSC through the service menu by changing the firmware to S95B:
https://www.reddit.com/r/OLED_Gaming/com...ay_stream/
windows 11 24h2 is out now and it still displays refresh rates not defined in CRU.
disabled VRR in windows settings does not remedy this
(10-01-2024 07:02 PM)ninjabyte587 Wrote: [ -> ]windows 11 24h2 is out now and it still displays refresh rates not defined in CRU.
disabled VRR in windows settings does not remedy this
What about if you disable G-SYNC in the NVIDIA control panel? I think this might be related to quick media switching, which uses VRR/G-SYNC to add virtual refresh rates that can switch instantly without interrupting the video signal. There shouldn't be any way to do this if VRR/G-SYNC is disabled.
Hi, I needed to reinstall windows and I ran into a bug again that causes a gray screen in front of the desktop, if you unplug the second monitor everything works fine. Somehow magically on the old system I bypassed this error by simply adding the 2 resolutions I wanted on the main CRU screen to the detailed resolution, and after a reboot everything worked as it should and no longer gave me any problems. Now it's not working, any suggestions on what can be done about this once and for all?
main 1440p165 displayport
second 1080p60 dvi-hdmi
rtx 4070ti super
(10-06-2024 04:00 PM)ToastyX Wrote: [ -> ] (10-01-2024 07:02 PM)ninjabyte587 Wrote: [ -> ]windows 11 24h2 is out now and it still displays refresh rates not defined in CRU.
disabled VRR in windows settings does not remedy this
What about if you disable G-SYNC in the NVIDIA control panel? I think this might be related to quick media switching, which uses VRR/G-SYNC to add virtual refresh rates that can switch instantly without interrupting the video signal. There shouldn't be any way to do this if VRR/G-SYNC is disabled.
i can confirm the strange refresh rate behavior with 24H2. normally i remove everything but 1920x1080@120, 2560x1440@120 and 3840x2160@120 on my LG OLED (which i have been doing for a couple years now.) but now after doing the same (fresh install of Windows and Nvidia driver) Nvidia Control Panel shows 120hz correctly, but the display is actually running at 60hz. i have to fiddle around with changing resolutions and/or clicking the refresh rate (even though only 120hz is displayed in NVCP) to get it to actually operate at 120hz.
i also had a strange bug where the display was operating at 120hz, but the desktop was updating at 60hz.
basically it's just all kinds of messed up right now - i assume this is "just how it is" with Windows 11 going forward with 24H2 so CRU might need an update to address whatever MS has added with refresh rate reporting