Custom Resolution Utility (CRU)
|
09-17-2022, 08:40 PM
Post: #6901
|
|||
|
|||
RE: Custom Resolution Utility (CRU) | |||
09-17-2022, 08:41 PM
Post: #6902
|
|||
|
|||
RE: Custom Resolution Utility (CRU) | |||
09-17-2022, 08:55 PM
Post: #6903
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(09-17-2022 08:40 PM)ToastyX Wrote:(09-17-2022 08:28 PM)Zireael61 Wrote: Yes, it is enabled. I also increased the range. I tried some refresh rates, and I can only increase refresh rate to 146 Hz without any frame skipping issue.Then the limitation is built into the monitor's firmware. Can I do anything to that? There is an usb socket at the back of the monitor. |
|||
09-17-2022, 10:32 PM
Post: #6904
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(09-17-2022 01:32 PM)ToastyX Wrote:(09-16-2022 08:10 AM)Lorgra93 Wrote: Removed HDR, HDMI, Colorimetry and edited the color depth to 8 bpc.I don't see a problem with the changes. AMD's driver is not listening to the override for some reason. I also tried completely cleaning up drivers with DDU and reinstalling the latest ones, but still no change... |
|||
09-18-2022, 02:05 AM
(Last edited: 09-18-2022, 02:09 AM by egagah)
Post: #6905
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Hi Toasty,
I have dual monitor setup and RTX2070super as below: PRISM+ X270 PRO (running at 2560x1440 @ 119.988Hz) AOC2402 24G2W1G4 (running at 1920x1080 @ 120.000 Hz) NVIDIA driver vers. 516.94 When I set my PRISM+ to 59.951Hz, my gpu can downclock, but at 119.988, it won't downclock. Both monitors can go to 144Hz but I dare not set this since the GPU will never down clock at those Hz. Problem arise is for the PRISM+ monitor, the target resolution of 1440p 120Hz above is only found under Extension blocks, and in here, even adding just 10 to the blanking vertical lines will cause the following events AFTER using restart64: 1) PRISM+ goes totally dark 2) AOC flashes quickly, mouse move super slow, flash again, repeat 3-5 times, then PC freezes. A restart after above event will cause the pc to load up to the login screen where it just freezes the moment the windows time appears on the AOC screen (PRISM+ stays dark the entire time). Any advise on this? screenshot of prism+ settings screenshot of the AOC settings. This one for some reason i cant find 120Hz exactly but windows has it? |
|||
09-18-2022, 10:34 AM
(Last edited: 09-18-2022, 10:36 AM by Lorgra93)
Post: #6906
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(09-17-2022 10:32 PM)Lorgra93 Wrote: I also tried completely cleaning up drivers with DDU and reinstalling the latest ones, but still no change...Okay, so could this setting be the cause? ![]() Maybe setting it like this force HDR with some specific flag that the CRU doesn't know about? Setting it as 1.1 obviously works, but it also disable many other things like 165Hz. At this point I'm groping in the dark... |
|||
09-18-2022, 02:28 PM
Post: #6907
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(09-18-2022 10:34 AM)Lorgra93 Wrote: Okay, so could this setting be the cause?I just realized what it is. It's the FreeSync data block. It has additional data for HDR that CRU doesn't show because it's undocumented, but this is AMD-specific. Delete the FreeSync data block. The data block shouldn't be needed for DisplayPort if you don't want HDR. If that disables FreeSync for some reason, add the FreeSync range back in manually and it won't have the HDR information. |
|||
09-18-2022, 02:28 PM
Post: #6908
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(09-18-2022 02:05 AM)egagah Wrote: I have dual monitor setup and RTX2070super as below:Normally for the GPU to clock down with multiple monitors, both monitors have to be perfectly synchronized so the vertical blanking periods happen at the same time, but this is hard when the resolutions don't match. I don't know how it clocks down at 59.951 Hz because that doesn't match the other monitor exactly. Freezing would be an NVIDIA driver bug, but that might be happening if the monitor isn't staying connected properly. If the PRISM+ can't handle custom parameters, that makes it much more difficult to synchronize both monitors, and I can't even guarantee synchronizing them would allow the GPU to clock down because the driver might not handle all cases where the resolutions are different. If the PRISM+ can handle a very slight tweak to the timing parameters, making all the parameters and the pixel clock a multiple of 4 would allow making a 1920x1080 equivalent by multiplying the parameters by 0.75 and the pixel clock by 0.5625. Technically these two are perfectly synchronized: You should also check the TV resolutions and delete 1920x1080 @ 120 Hz if it's in there. I don't know if that's enough blanking for the GPU to clock down, but if it isn't, I'm not sure what you can do if the PRISM+ won't accept higher vertical totals. |
|||
09-18-2022, 02:36 PM
Post: #6909
|
|||
|
|||
RE: Custom Resolution Utility (CRU) | |||
09-20-2022, 12:23 AM
Post: #6910
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
Hi guys, im first time here and was wondering if there was any way to fix/reduce ghosting on VA panel via CRU?
Thank you. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 106 Guest(s)