(01-05-2024 09:48 AM)WJUI Wrote: [ -> ]Unfortunately my second monitor is no longer detected by my PC.
I used CRU to make a custom resolution for my 24" side monitor to go with my 27" main monitor for sim racing. I then set the 1080p monitor to go to 2343x1152 or so, so that I could use my 27" monitor at 1440p instead of 1080p. It worked, I played my game. Didn't know if the resolution was actually working correctly so was gonna go back and test it with other resolutions.
Then when I tried to get back on again it just showed a black screen on the side monitor. Soon after the monitor disappeared from my PC display settings, and detecting yields nothing.
To try to fix it, I used reset.all, restart.exe, restarted my computer. I pressed delete on the CRU UI because I heard that was a way to reset the settings for the monitor, now the monitor isn't on CRU anymore (before it was still on there with a * even though it wasn't detected by PC anymore).
I'm using an HDMI 2.1, Never had a problem before--I just plug it in and the monitor works right away. Didn't do anything except use CRU. (Mentioning because people were saying it's probably the HDMI cable, an issue with the monitor, etc.)
I searched for this and found a few discussions but no concrete solutions. Anybody know what to do?
I guess the GPU had an issue when making the 1080p monitor run at the weird and above-max resolution, but beyond that I don't know what it is or what to do to fix it. Isa clean install of graphics card drivers likely to fix it? Unfortunately I'm confused on how exactly to do that in my short time researching it so far
Edit: I have an Intel Arc a750 in the PC
You can't permanently downscale in Intel with higher-resolution PCs. You could have tried with setting Display1_DownScalingSupported to 1 (If you want to know where is it, I'll tell you) but I'm not sure if with higher-resolution PCs it even has an effect in making downscaled resolutions work. Intel's stance is that they don't support downscaled resolutions.
(01-03-2024 08:02 PM)ToastyX Wrote: [ -> ] (01-03-2024 07:22 PM)someone Wrote: [ -> ]I have already mentioned a key called DALNonStandardModesBCD1. It's a REG_BINARY key. Are you referring to that one? without vsr only resolutions with a lower width/height/both than the native can be added though (I added 1152x768 and the process was successful but in 1280x800's case it wasn't added)
No, SRE already uses DALNonStandardModes. I'm talking about custom resolutions in AMD's control panel.
But you mentioned finding the custom resolution in the registry. You can create them with DALNonStandardModes, just limited to higher resolutions.
(01-05-2024 04:31 PM)someone Wrote: [ -> ]But you mentioned finding the custom resolution in the registry. You can create them with DALNonStandardModes, just limited to higher resolutions.
DALNonStandardModes is not the same as custom resolutions in the control panel.
(01-05-2024 03:40 PM)Bibimbap Wrote: [ -> ]What is the correlation between the pixel clock and the resolution?
Does it means that I can't have a resolution of 5120 x 1440?
Pixel clock is the total number of pixels per second: horizontal total * vertical total * refresh rate
5120x1440 is possible at 30 Hz, but HDMI 1.4 only officially supports up to 4096x2160, so the graphics driver or the monitor might not allow it.
(01-05-2024 04:41 PM)ToastyX Wrote: [ -> ] (01-05-2024 04:31 PM)someone Wrote: [ -> ]But you mentioned finding the custom resolution in the registry. You can create them with DALNonStandardModes, just limited to higher resolutions.
DALNonStandardModes is not the same as custom resolutions in the control panel.
So the registry key that defines custom resolutions in the control panel is different? I tried to open CCC and I had to uninstall it because it didn't open (Windows 11 doesn't support Catalyst but when I had Windows 10 it worked the first time and afterwards it couldn't open)
(01-05-2024 04:41 PM)ToastyX Wrote: [ -> ] (01-05-2024 03:40 PM)Bibimbap Wrote: [ -> ]What is the correlation between the pixel clock and the resolution?
Does it means that I can't have a resolution of 5120 x 1440?
Pixel clock is the total number of pixels per second: horizontal total * vertical total * refresh rate
5120x1440 is possible at 30 Hz, but HDMI 1.4 only officially supports up to 4096x2160, so the graphics driver or the monitor might not allow it.
Thank you for this explanation.
So if I understand correctly, I can't have a resolution of 5120x1440 because of the HDMI 1.4 standard but not because of the pixel clock because there is less pixels with 5120x1440 (7.3M) than with 4096x2160 (8.8M).
Am I right?
(01-05-2024 08:01 PM)Bibimbap Wrote: [ -> ]Thank you for this explanation.
So if I understand correctly, I can't have a resolution of 5120x1440 because of the HDMI 1.4 standard but not because of the pixel clock because there is less pixels with 5120x1440 (7.3M) than with 4096x2160 (8.8M).
Am I right?
No, both are separate limitations. HDMI 1.4 officially supports 3840x2160 @ 30 Hz and 4096x2160 @ 24 Hz. The driver might allow 5120x1440 @ 30 Hz since it's within the pixel clock limit, but the monitor might not be able to display it because of scaler limitations. You'll have to try it and see. 5120x1440 @ 60 Hz wouldn't be possible without both the monitor and GPU supporting HDMI 2.0.
(01-05-2024 06:44 PM)someone Wrote: [ -> ]So the registry key that defines custom resolutions in the control panel is different? I tried to open CCC and I had to uninstall it because it didn't open (Windows 11 doesn't support Catalyst but when I had Windows 10 it worked the first time and afterwards it couldn't open)
They aren't the same at all. DALNonStandardModes applies to all displays on the GPU and doesn't let you specify timing parameters. Custom resolutions in AMD's control panel are specific to the monitor and let you specify timing parameters like detailed resolutions, and it also lets you specify the desktop resolution separately from the active resolution, but for some reason the control panel rejects downsampled resolutions even if the GPU can do it, so you'd have to create the custom resolution, find the value in the registry, and hex edit the desktop resolution part to be different from the active resolution. This is what people did many years ago before VSR was a feature, but the tutorials no longer work because the details have changed, and the helper utility they used no longer functions either. This method might still be possible, but you need to find a way to create a custom resolution first so it can create the registry value.
Old tutorials:
https://forums.guru3d.com/threads/downsa...on.366244/
https://forums.guru3d.com/threads/downsa...on.404125/
https://forums.blurbusters.com/viewtopic.php?t=2608
The last one has a screenshot that shows what the registry value looks like.
(01-05-2024 08:52 PM)ToastyX Wrote: [ -> ] (01-05-2024 06:44 PM)someone Wrote: [ -> ]So the registry key that defines custom resolutions in the control panel is different? I tried to open CCC and I had to uninstall it because it didn't open (Windows 11 doesn't support Catalyst but when I had Windows 10 it worked the first time and afterwards it couldn't open)
They aren't the same at all. DALNonStandardModes applies to all displays on the GPU and doesn't let you specify timing parameters. Custom resolutions in AMD's control panel are specific to the monitor and let you specify timing parameters like detailed resolutions, and it also lets you specify the desktop resolution separately from the active resolution, but for some reason the control panel rejects downsampled resolutions even if the GPU can do it, so you'd have to create the custom resolution, find the value in the registry, and hex edit the desktop resolution part to be different from the active resolution. This is what people did many years ago before VSR was a feature, but the tutorials no longer work because the details have changed, and the helper utility they used no longer functions either. This method might still be possible, but you need to find a way to create a custom resolution first so it can create the registry value.
Old tutorials:
https://forums.guru3d.com/threads/downsa...on.366244/
https://forums.guru3d.com/threads/downsa...on.404125/
https://forums.blurbusters.com/viewtopic.php?t=2608
The last one has a screenshot that shows what the registry value looks like.
Firstly, I don't have crimson. In CCC you can also create custom resolutions but you need to set advanced view.
Secondly, the user of the first tutorial had 1920x1200 as native which has the same aspect ratio as 2560x1600. That's NOT where my concern lies in.
Thirdly, I don't have the ModeTimingOverrides value and the EDID key is not in Common, is it because I have no custom resolutions created in AMD's control panel? (I don't have AMD control panels yet but I know it's not possible with Adrenalin in laptops)
Fourthly, there is no need to create a custom resolution in AMD's control panel to create the registry value, however it would be very hard.
(01-05-2024 03:07 PM)ToastyX Wrote: [ -> ] (01-05-2024 09:48 AM)WJUI Wrote: [ -> ]Unfortunately my second monitor is no longer detected by my PC.
I used CRU to make a custom resolution for my 24" side monitor to go with my 27" main monitor for sim racing. I then set the 1080p monitor to go to 2343x1152 or so, so that I could use my 27" monitor at 1440p instead of 1080p. It worked, I played my game. Didn't know if the resolution was actually working correctly so was gonna go back and test it with other resolutions.
Then when I tried to get back on again it just showed a black screen on the side monitor. Soon after the monitor disappeared from my PC display settings, and detecting yields nothing.
To try to fix it, I used reset.all, restart.exe, restarted my computer. I pressed delete on the CRU UI because I heard that was a way to reset the settings for the monitor, now the monitor isn't on CRU anymore (before it was still on there with a * even though it wasn't detected by PC anymore).
I'm using an HDMI 2.1, Never had a problem before--I just plug it in and the monitor works right away. Didn't do anything except use CRU. (Mentioning because people were saying it's probably the HDMI cable, an issue with the monitor, etc.)
I searched for this and found a few discussions but no concrete solutions. Anybody know what to do?
I guess the GPU had an issue when making the 1080p monitor run at the weird and above-max resolution, but beyond that I don't know what it is or what to do to fix it. Isa clean install of graphics card drivers likely to fix it? Unfortunately I'm confused on how exactly to do that in my short time researching it so far
Edit: I have an Intel Arc a750 in the PC
Usually when a monitor isn't detected, it's an issue with the monitor or the connection to the monitor, but I don't know if Intel's driver has some bug that could also cause this.
Maybe the driver failed to enable after running restart.exe, which could cause the second screen to be ignored. Check Device Manager under "Display adapters" and make sure the Intel GPU is enabled.
If the GPU is enabled, try unplugging the monitor's power for a minute to "reboot" the monitor just in case it's a firmware glitch.
If that doesn't work, uninstall the graphics driver using DDU with Windows in safe mode: https://www.wagnardsoft.com/display-driv...aller-ddu-
Then reinstall the Intel graphics driver. If that doesn't help, check if the monitor works by itself without the other monitor. If it still won't work, then something might be wrong with the monitor itself. Custom resolutions normally wouldn't damage a monitor like this, so I'm not sure what could have happened.
Awesome. I unplugged it for a day. Then tried it out without the other monitor and it works. Thanks Toasty
Hello,
I've got a 55" TCL 5 Series/S555 4K TV that I'm using with a Nvidia RTX 3070 FE Windows 11 PC and getting random bursts of 3-5 what I would call "flickers" (screen blanking out very quickly) every 40-60 min or so. I have tried various length/specs of HDMI cable, turning off HDR and switching to 4:2:2/4:2:0 color profiles in Nvidia Control Panel in an attempt to reduce bandwidth with no luck, and wondering if CRU can help but I don't know where to start. I did a search on the forum before posting and couldn't find anything specific enough for what I feel I'm encountering, so hoping to find help here. I don't have a lot of experience with CRU and I'm still learning about recent display technologies. FWIW, I also have a PS3 and PS4 Pro connected to this TV which do not appear to have this issue. A couple (very uneducated) thoughts:
- Some newer 4K/60Hz TVs like mine have advertised having HDMI 2.1 ports, but do not actually support HDMI 2.1 bandwidth. Could this be a conflict between the port's actual capability and what the Nvidia driver sees? As a shot in the dark, I tried using CRU to edit the "HDMI 2.0 support" data block to specify both "FRL rate" settings to 18 Gbps but that didn't appear to work. (The data block's name also changed to "HDMI 2.1 support" after so that may have defeated my theory anyway.) I have since reset CRU and completely reinstalled video drivers with DDU just in case.
- If not bandwidth-related, could setting a custom resolution perhaps solve this issue? My TestUFO "Exact" Refresh Rate Test results in 60.002 Hz, I'm not sure if that means anything.
I'm not attempting to enable FreeSync/Gsync or anything (VRR is set to "off" in the TV's input settings), just trying to play games at 4K/60Hz with HDR, which I know is at the limits of what the TV is capable of, but as I've said this is happening even when displaying with HDR off, 4:2:2 or 4:2:0 color. I read something in another post suggesting to disconnect any other displays, so I also disconnected my DVI monitor at my desk with no success.
I may be completely off base, so any suggestions from the CRU community would be greatly appreciated, as I'm about to go back to my old 1080p Samsung TV where I've never had an issue! Thanks all
