Why can't I use my DP resolution at 160Hz over HDMI? My monitor does not have 160Hz over HDMI out of the box (even though HDMI 2.1 has more bandwidth than DP 1.4), and every time I put in a detailed resolution under the DisplayID 1.3 extension block over 150Hz it ignores it. I know my monitor can do 160Hz over DP, so I used that exact resolution/timings and pasted it on my HDMI custom resolution, but it doesn't show up in NVCP. What gives?
Monitor: Acer 4K 160Hz XV275KP3
GPU: 3060 Ti
EDIT: Here is where I'm getting stuck on. Works on 154, does not work on 155.
https://imgur.com/a/0KOnL9Y
(11-25-2024 04:36 AM)ToastyX Wrote: [ -> ] (11-24-2024 09:03 PM)MeelyMee Wrote: [ -> ]Hello everyone, I was hoping maybe someone could help me.
I upgraded my laptop from a 60Hz panel to a new 144Hz panel - BOE NV156FHM-NY1
Now this isn't an officially supported upgrade but does work, I have display. This laptop does not seem to have any sort of profile for displays beyond 60Hz though so I assume I will have to create a custom profile with CRU?
I tried copying the settings from the existing 60Hz profile and simply changing the refresh to 144Hz but this does not work, the image appears to be doubled/distorted. Could anyone help me? I think I might need some more settings to fill in in CRU.
Thank you
You would need the datasheet for the recommended timing parameters, but panels usually aren't that picky. Have you tried the different timing options? If "Automatic PC" and "Native HDTV" don't work correctly, then the connection might not have enough bandwidth. You can try different refresh rates and see if you hit a certain limit.
I think I've been ripped off. The sticker may say NV156FHM-NY1 but the EDID says:
Code:
Detailed Timing Descriptors:
DTD 1: 1920x1080 60.041908 Hz 16:9 67.727 kHz 149.000000 MHz (344 mm x 193 mm)
Hfront 108 Hsync 48 Hback 124 Hpol P
Vfront 10 Vsync 10 Vback 28 Vpol N
Empty Descriptor
Alphanumeric Data String: 'BOE HF'
Alphanumeric Data String: 'GV156FHB-NZ0'
Fun... now I've got to remove it and return it.
(11-22-2024 09:40 PM)ToastyX Wrote: [ -> ] (11-22-2024 04:28 PM)willianwojcik Wrote: [ -> ]Hello
Did anyone solve it?
NVIDIA has no answers, I'm tired of asking
And I'm stuck with the 556.12 driver because it's the last one that works perfectly with DSR
You didn't say what you tried. Show me what isn't working. Export files with the changes and post them here.
Right, 556.12, the last one that is scaling perfectly with DLDSR
I do two things to make it work. I pull up the 3840x1600 resolution to the first place in the "Detailed resolutions (2 slots left)" tab. Necessary to appear as native on the NVIDIA panel, otherwise the 2560x1080 resolution will appear as native, scaling incorrectly in the DSR. If you don't do this simple 1 second step, it won't work.
In the "Extension Block", "TV Resolutions" tab, I delete all 4096x2160 resolutions
In the "HDMI Support" tab, I do the same
That's all, I click on "restart64" and everything works as it should
https://imgur.com/a/MFzoJTs
(11-25-2024 05:49 AM)ebombzor Wrote: [ -> ]Why can't I use my DP resolution at 160Hz over HDMI? My monitor does not have 160Hz over HDMI out of the box (even though HDMI 2.1 has more bandwidth than DP 1.4), and every time I put in a detailed resolution under the DisplayID 1.3 extension block over 150Hz it ignores it. I know my monitor can do 160Hz over DP, so I used that exact resolution/timings and pasted it on my HDMI custom resolution, but it doesn't show up in NVCP. What gives?
Monitor: Acer 4K 160Hz XV275KP3
GPU: 3060 Ti
EDIT: Here is where I'm getting stuck on. Works on 154, does not work on 155. https://imgur.com/a/0KOnL9Y
That's a GPU limitation. The pixel clock is limited to around 1350 MHz.
(11-25-2024 03:26 PM)ToastyX Wrote: [ -> ] (11-25-2024 01:42 PM)willianwojcik Wrote: [ -> ]Right, 556.12, the last one that is scaling perfectly with DLDSR
I do two things to make it work. I pull up the 3840x1600 resolution to the first place in the "Detailed resolutions (2 slots left)" tab. Necessary to appear as native on the NVIDIA panel, otherwise the 2560x1080 resolution will appear as native, scaling incorrectly in the DSR. If you don't do this simple 1 second step, it won't work.
In the "Extension Block", "TV Resolutions" tab, I delete all 4096x2160 resolutions
In the "HDMI Support" tab, I do the same
That's all, I click on "restart64" and everything works as it should
https://imgur.com/a/MFzoJTs
Export a file from CRU.
Okay, done
It created a bin file, correct?
How can I send it to you?
Thanks
(11-25-2024 07:02 PM)willianwojcik Wrote: [ -> ]Okay, done
It created a bin file, correct?
How can I send it to you?
Thanks
Any format is fine. You can upload it as an attachment here.
(11-25-2024 08:45 PM)willianwojcik Wrote: [ -> ]Done!
Thanks
I don't see 3840x1600 @ 120 Hz anywhere. Only 60 Hz.
(11-25-2024 09:54 PM)ToastyX Wrote: [ -> ] (11-25-2024 08:45 PM)willianwojcik Wrote: [ -> ]Done!
Thanks
I don't see 3840x1600 @ 120 Hz anywhere. Only 60 Hz.
From the beginning, when I use the C2's 21:9 ultrawide, the native resolution that appears on the NVIDIA panel is 2560x1080, not scaling correctly with DLDSR
To display 3840x1600 as native, you need to select the 3840x1600 resolution first in the "Detailed resolutions (2 slots left)" tab. Just pull it up and leave it as the first one, instead of 2560x1080. Nothing more
Doing this in CRU after 556.12 driver, the 3840x1600 is stuck at 60Hz
When I contacted NVIDIA, they initially told me it was a bug in the driver, but so far no solution, no answers
Strange isn't it? I don't know what to do to fix it
I found some people with the same problem on Reddit, with no solution. They tried everything
Thanks