(10-08-2022 03:50 AM)simon52min Wrote: [ -> ]Can you tell me in detail what is the difference between the HDMI 2.1 and the HDMI2.0 emulator? I had added CTA-861 block via cru tool, and add data block hdmi2.1 support. Is there a parameter that is not set correctly?
You can't add FRL support with CRU. The device has to support it. HDMI 2.0 is limited to 600 MHz pixel clock.
(09-18-2022 02:28 PM)ToastyX Wrote: [ -> ] (09-18-2022 02:05 AM)egagah Wrote: [ -> ]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).
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.
Hi ToastyX,
Is me again. So I was experimenting to see if I could get both monitors to be at 144Hz and not have GPU ramp up. I only manage to achieve 1 of the 2 monitors to be 144Hz, the other one shall be 60Hz. I'm guessing this is what you were talking about when you mentioned different resolutions causing issue with syncing and hence back to high memory clocks again right? Right now, the PRISM+ 2160p is 144Hz and the AOC 1080p is 60Hz exactly.
Both monitors are set to the CVT-RB Standard. I wanted to try the RB2 settings but the PRISM+ 2160p one shows red on the refresh rate (can only take up to 110Hz). So I left both at RB.
You reckon there are anything else I can try?
Hi There, I only recently stumbled across this utility - It worked for me when I tested it under Windows 11 21H2, but seemingly, after auto-updating to Windows 11 22H2 (...and the plethora of headaches that bought with it!) CRU no longer shows my custom resolutions in the windows display settings resolution drop down. I downloaded the latest 1.5.2 version (Previously I used 1.5.1) - I ran reset-all.exe, I rebooted, I then ran CRU and added my custom resolution. I then ran restart.exe and restart64.exe then decided to reboot again for good measure, but alas, my newly created resolution still doesn't show. For what it's worth, I'm thinking it's a Windows 22H2 thing because my AMD Radeon software that also has a custom resolution function that previously worked, also no longer works and won't show any custom resolutions in windows display settings.
(10-12-2022 09:44 AM)IAmOrion Wrote: [ -> ]Hi There, I only recently stumbled across this utility - It worked for me when I tested it under Windows 11 21H2, but seemingly, after auto-updating to Windows 11 22H2 (...and the plethora of headaches that bought with it!) CRU no longer shows my custom resolutions in the windows display settings resolution drop down. I downloaded the latest 1.5.2 version (Previously I used 1.5.1) - I ran reset-all.exe, I rebooted, I then ran CRU and added my custom resolution. I then ran restart.exe and restart64.exe then decided to reboot again for good measure, but alas, my newly created resolution still doesn't show. For what it's worth, I'm thinking it's a Windows 22H2 thing because my AMD Radeon software that also has a custom resolution function that previously worked, also no longer works and won't show any custom resolutions in windows display settings.
I'm not aware of any issues with 22H2. Use the latest version of DDU to clean out all the old drivers:
https://www.wagnardsoft.com/forums/viewtopic.php?t=4142
Then install the latest AMD driver:
https://www.amd.com/en/support/kb/releas...in-22-10-1
(10-14-2022 07:57 PM)ToastyX Wrote: [ -> ]I'm not aware of any issues with 22H2. Use the latest version of DDU to clean out all the old drivers: https://www.wagnardsoft.com/forums/viewtopic.php?t=4142
Then install the latest AMD driver: https://www.amd.com/en/support/kb/releas...in-22-10-1
Hmm interesting...
I already did that - although due to fortnite *still* being buggy with any AMD driver later than 22.2.2, I re-installed 22.2.2. But I was always on 22.2.2 as I disabled windows updating drivers etc so my only change is that Windows upgraded to 22H2
Anything later than 22.2.2 - for me at least, causes random 2-3 second freezes, where FPS drops to *ZERO* like it's a stutter or something.
I already overclocked the GPU (6700XT) and set min to just 50 lower than the max overclocked value and tweaked the rest and turned off ULSS (I think it was called ULSS from memory - was done via msi afterburner) - but again, all that was done prior to 22H2 and was fine without issue.
Perhaps I'll reinstall latest AMD just to see if CRU works again - maybe there's an issue with the combination of 22H2 and AMD 22.2.2
I'm encountering a weird issue since upgrading to 22H2. Well, at least, I'm only now noticing it and am certain it wasn't present previously.
I can't think of anything else that has changed.
Making ANY change to the EDID of my LG CX using CRU causes issues with gsync.
It causes gsync to make the screen go black at any fps below 40fps.
This includes flickering black if the fps fluctuates even a moment to what would equal less than 40fps.
EXCEPT for 20fps exactly, this will show an image.
While this issue is present (a.k.a. after any alterations to the EDID using CRU) will also cause the PC to completely freeze and need a hard restart then toggling gsync on or off in the NVCP.
Literally all I did was change the HDR Metadata to suit my display.
What's extra odd, is even reverting the changes using CRU, does not fix the issue of the screen going black.
I need to use CRU's 'reset-all.exe' and NOT edit the EDID again whatsoever for gsync to operate properly.
I tested and this issue continues across the last 3 nvidia driver updates so I doubt it's driver related.
I'm happy to perform additional troubleshooting.
Hi, I have a similar issue after "upgrading to 22H2" - so many issues, what a nightmare...
Before, I had 119.88hz and 120.00hz refresh rates available that I could switch between freely, after upgrading I thought it best to use DDU and start the graphics drivers from scratch
Now, when I try to add these custom refresh rates it does add but they will always override one another:- I can have 120 but not 119.88, or I can have 119.88 but not 120
I guess whenever I want to change I can go into CRU and change it out but that's an extra step that wasn't required before.
Hope this can be fixed
(10-16-2022 11:37 AM)trenx Wrote: [ -> ]Now, when I try to add these custom refresh rates it does add but they will always override one another:- I can have 120 but not 119.88, or I can have 119.88 but not 120
CRU does not have control over this. It's up to the graphics driver whether or not it can support multiple fractional refresh rates. Historically, Windows would consider both to be 120 Hz so only one would take effect.
(10-16-2022 08:16 AM)Chunky1311 Wrote: [ -> ]I'm encountering a weird issue since upgrading to 22H2. Well, at least, I'm only now noticing it and am certain it wasn't present previously.
I can't think of anything else that has changed.
Making ANY change to the EDID of my LG CX using CRU causes issues with gsync.
It causes gsync to make the screen go black at any fps below 40fps.
This includes flickering black if the fps fluctuates even a moment to what would equal less than 40fps.
EXCEPT for 20fps exactly, this will show an image.
While this issue is present (a.k.a. after any alterations to the EDID using CRU) will also cause the PC to completely freeze and need a hard restart then toggling gsync on or off in the NVCP.
Literally all I did was change the HDR Metadata to suit my display.
What's extra odd, is even reverting the changes using CRU, does not fix the issue of the screen going black.
I need to use CRU's 'reset-all.exe' and NOT edit the EDID again whatsoever for gsync to operate properly.
I tested and this issue continues across the last 3 nvidia driver updates so I doubt it's driver related.
This is 100% an NVIDIA driver bug and should be reported to them.
(10-06-2022 02:21 PM)ToastyX Wrote: [ -> ]Yes, but NVIDIA stores its settings in the registry.
Just made a try on the SD CRT Tv. Couldn't make anything to work
When I load the modified EDID with nvidia CP, it sees the actual original resolutions of the device from which I exported the EDID, it doesn't see any modification I made with CRU (only CRU see the modifications).
So, either I'm doing something wrong or there's some incompatibilities with my configuration.
I'm not even sure if the EDID from file function on nvidia CP, actually sends a signal (maybe is just an edid emulator for remote control...).
Anyway, I can keep trying hotswitching the cable from a VGA connected monitor, using CRU Automatic CRT settings as a clue to correctly tweak the values on Nvidia cp custom resolution tab.
That's the only way I'm 100% sure it could work (since I managed to perfectly see a 320x240 image on the SD CRT once).