Custom Resolution Utility (CRU)
|
08-26-2025, 07:55 PM
Post: #9221
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-26-2025 07:04 PM)sethssl Wrote: I'm trying to get a new resolutions by making it my native resolutions. What I've been doing is I go to extension blocks and copy one of the detailed resolutions (the one with the Hz I normally use which is the highest). Then delete all extension blocks, delete all standard resolutions and detailed resolutions. then I make a new standard resolutions that matches my monitor but leave it at 60Hz. Then I make a new Detailed resolutions and paste what I took from the extension block and instead of having 1920 x 1080 I swap it to something I want.Are you using DisplayPort or HDMI? HDMI requires the HDMI data blocks in the CTA-861 extension block. |
|||
08-26-2025, 08:31 PM
Post: #9222
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-26-2025 07:55 PM)ToastyX Wrote:(08-26-2025 07:04 PM)sethssl Wrote: I'm trying to get a new resolutions by making it my native resolutions. What I've been doing is I go to extension blocks and copy one of the detailed resolutions (the one with the Hz I normally use which is the highest). Then delete all extension blocks, delete all standard resolutions and detailed resolutions. then I make a new standard resolutions that matches my monitor but leave it at 60Hz. Then I make a new Detailed resolutions and paste what I took from the extension block and instead of having 1920 x 1080 I swap it to something I want.Are you using DisplayPort or HDMI? HDMI requires the HDMI data blocks in the CTA-861 extension block. you are awesome! thank you. |
|||
08-26-2025, 09:00 PM
Post: #9223
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-26-2025 06:37 PM)GGoki Wrote: I just came here to inform you the exact figure!!Thanks. I've updated the first post. The problem shouldn't affect Pascal since it doesn't support DSC or using multiple heads. I also added a workaround to disable multiple heads. |
|||
08-28-2025, 12:19 AM
Post: #9224
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
What is the best method and options to use for custom resolutions?
I have RTX 5090 and a zowie 600hz TN monitor via HDMI 2.1. The monitor also has DP 1.4, but I think it uses DSC either way. My aim is to use 1728x1080 @ 600Hz with Dyac2 and the lowest input lag and possible! With previous GPUs, I did the registry hack NV_Nodes and everything worked fine. The RTX 5000 cannot do the Nv_Nodes hack anymore. So I use CRU. What timing should i use? Automatic PC or Exact, or Exact reduced? Etc. Does using CRU and the reccommended timing for my setup affect operation of Dyac? I would just like the best possible outcome for competative fps gaming. Would appreciate any help here, thank you! |
|||
08-28-2025, 04:53 PM
Post: #9225
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(08-28-2025 12:19 AM)snoopi Wrote: What is the best method and options to use for custom resolutions?You're talking about three different things. 1. For timing parameters, use whatever works. Normally it's not important, but at 600 Hz, there might be bandwidth limitations that require non-standard timing parameters to reduce the pixel clock. NVIDIA GPUs don't actually support the full HDMI 2.1 bandwidth without using Display Stream Compression (DSC) and multiple heads internally. You might have to disable using multiple heads as described in the first post for CRU to work, but then you'll be limited to the single-head limit. 5000-series GPUs support up to 1620 MHz pixel clock without DSC. For 1728x1080 @ 600 Hz, CVT-RB2 fits just within the 1620 MHz limit. For 1920x1080 @ 600 Hz, you'll have to try the non-standard options if the monitor's default doesn't fit within 1620 MHz. 2. DyAc is for motion clarity at the expense of very slight lag because the backlight needs to be off while the pixels are changing. DyAc works best when the frame rate matches the refresh rate to avoid the double image effect, so you might need to use a lower refresh rate to see the benefits, but that also reduces responsiveness slightly. If variable refresh rate (VRR) is enabled, that is handled automatically, but I don't think DyAc works with VRR. For DyAc, increasing the vertical blanking might reduce ghosting/crosstalk slightly, but it's hard to increase the blanking when the bandwidth is limited, and CVT-RB2 already has the blanking quite high at 600 Hz. 3. For least lag, you would need to disable DyAc and use the highest refresh rate with no frame rate caps. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 298 Guest(s)