(10-11-2024 10:17 PM)krisdee1981 Wrote: [ -> ]Guys I have some serious issues with fresh install of 24h2 and CRU. I wanted to add 120Hz as always and I had black screen 3 times in a row with different drivers.
After few hours of fighting with this problem I finally figured out that if gsync is enabled I can't add anything with CRU in 24h2.
I disabled gsync and this worked fine, but once I activate gsync I get black screen and need to remove drivers with DDU.
Dynamic refresh rate in the Windows advanced display settings was disabled.
You really need to report these issues to NVIDIA. I can't do anything about them. Their drivers are causing so many headaches with EDID overrides.
(10-11-2024 06:13 AM)Jen Wrote: [ -> ]1) do the back porch, front porch, and blanking values affect the pixel shift functionality in OLED monitors? For me, I notice the pixel shift effect more often in the native resolution than say, a wierd custom resolution like 1178x663. This is also the case in other standard resolutions like 1080p and 720p.
They shouldn't, but that would depend on what the monitor's firmware does.
(10-11-2024 06:13 AM)Jen Wrote: [ -> ]2) What is the purpose of non-integer refresh rates like 358.98hz? Why couldn't it just be 360 or 359?
It's just rounding because the pixel clock can only have 2 decimal places. It can be exact if they made it that way, like with CRU's "Exact" timing.
(10-11-2024 06:13 AM)Jen Wrote: [ -> ]2b) Do certain monitors have such specific refresh rates in its EDID for image smoothness purposes? Do the decimal refresh rates even affect image quality in some technical way?
No, it's just the way certain standards say to round.
(10-11-2024 06:13 AM)Jen Wrote: [ -> ]3) Why is it that I see faint vertical lines evenly spaced out in certain dark scenes on my OLED monitor? I know that it is caused by my custom resolution's timings, but I don't know which timing value(s) are causing it.
That seems like a monitor-specific limitation. The timing parameters don't inherently cause that sort of thing.
(10-09-2024 11:27 AM)topmeme Wrote: [ -> ]this bug is bypassed by some purely random stuff, we all know that nvidia doesn't care about the problems of users using some third-party programs
CRU is just an EDID editor. I can't do anything about NVIDIA driver issues. The issue doesn't have to involve CRU at all. You can export an .inf file and say installing the monitor .inf file also causes the problem.
(10-15-2024 04:49 AM)funkerwolf Wrote: [ -> ] (10-14-2024 10:49 PM)ToastyX Wrote: [ -> ] (10-11-2024 08:29 PM)funkerwolf Wrote: [ -> ] (09-27-2024 12:07 AM)ToastyX Wrote: [ -> ] (09-26-2024 12:35 AM)funkerwolf Wrote: [ -> ]It is all in place, but on the latest versions in Windows and through the Intel panel does not give just select 75 hertz, there is no such item to select.
Show me what you have. Run this and post the test.txt here: https://www.monitortests.com/EDID-test.zip
That was the old URL. I have an updated version here: https://www.monitortests.com/edid-test.zip
You didn't set the max TMDS clock in the HDMI data block like I said to do. You said it was all in place.
(10-14-2024 10:49 PM)ToastyX Wrote: [ -> ] (10-11-2024 10:17 PM)krisdee1981 Wrote: [ -> ]Guys I have some serious issues with fresh install of 24h2 and CRU. I wanted to add 120Hz as always and I had black screen 3 times in a row with different drivers.
After few hours of fighting with this problem I finally figured out that if gsync is enabled I can't add anything with CRU in 24h2.
I disabled gsync and this worked fine, but once I activate gsync I get black screen and need to remove drivers with DDU.
Dynamic refresh rate in the Windows advanced display settings was disabled.
You really need to report these issues to NVIDIA. I can't do anything about them. Their drivers are causing so many headaches with EDID overrides.
I'm pretty sure it is something to do with 24h2 because I used CRU extensively on previous versions of Win11 and Win10. Yeah sometimes Nvidia driver did break after changing things with CRU, but after reinstalling drivers everything was working ok eventually.
hello, help with my problem, if you can
- after CRU no signal (black screen) on the 1st monitor (display port 165 hz), when 2nd monitor connected (HDMI 60hz), instead of the welcome screen
- if individually apply changes and only on the 2nd monitor (when two monitors connected) ---> all will be okay
- i deactivate the 2nd (multimonitortool) or pull out the HDMI cable, when turning off PC
- problem with monitors priority at the welcome screen (win 10, dp 2sd, hdmi 1st), i am thinking
- with two DP monitors, i cann't turn off monitor without problems (the programms from 2nd jump on 1st)
(10-15-2024 07:56 AM)Merculian Wrote: [ -> ]hello, help with my problem, if you can
- after CRU no signal (black screen) on the 1st monitor (display port 165 hz), when 2nd monitor connected (HDMI 60hz), instead of the welcome screen
- if individually apply changes and only on the 2nd monitor (when two monitors connected) ---> all will be okay
If this is an NVIDIA GPU, you need to report the issue to NVIDIA because it's a bug in their driver.
(10-15-2024 07:56 AM)Merculian Wrote: [ -> ]- with two DP monitors, i cann't turn off monitor without problems (the programms from 2nd jump on 1st)
That's normal because DisplayPort monitors disconnect from the PC when turned off, so Windows moves the windows to another monitor.
Playing with the AOC Q27G3XMN. It ships with 180hz (already oc'd I believe because timings are vastly different to 170hz).
Ive got 182 working on the same timings as 180 but cant go further. It just goes black saying 'Input not support'. Timings:
https://ibb.co/18dx5tK
Is there anything obvious I can do to push it? Im running DP 1.4 on a 7800xt.
Also if the panel can do 182, does that mean its not locked to 180 by AOC?