(08-15-2024 03:01 PM)ToastyX Wrote: [ -> ] (08-15-2024 01:02 PM)Jen Wrote: [ -> ]Hello, so I got my new aw2725df, but when I try to use a custom resolution theres no hdmi signal despite the resolutions being within the hdmi 1.4 bandwith limit and intel gpu pixel clock limit (300.99 mhz)
I noticed that only the tv resolutions in the CTA-861 extension block work, but nothing else including detailed resolutions within the extension block. Also in case, the block also includes hdmi support (not 2.1 to be exact) with 340tmds limit.
That's up to the monitor. Just because the GPU can send it doesn't mean the monitor will handle it. What resolutions are you trying? The manual says it only supports 60/120 Hz at 1920x1080 and 60/120/144 Hz at 2560x1440 with HDMI. The monitor requires DisplayPort for higher refresh rates.
I was trying to add some wierd resolutions (all below 300.99mhz and 16:9)
1920x1080@138
1793x1008@158
1424x801@247
Since they don't seem to work at the moment, does that mean I'm stuck at 1920x1080@120, until I get a new pc?
(08-15-2024 03:53 PM)Jen Wrote: [ -> ]I was trying to add some wierd resolutions (all below 300.99mhz and 16:9)
1920x1080@138
1793x1008@158
1424x801@247
Since they don't seem to work at the moment, does that mean I'm stuck at 1920x1080@120, until I get a new pc?
Seems that way. It doesn't even support 1920x1080 @ 240 Hz with HDMI 2.0 even though it supports HDMI 2.0 for 2560x1440 @ 120/144 Hz, and they could have supported 1280x720 @ 240 Hz with HDMI 1.4. Have you tried 144 Hz at a lower resolution like 1600x900 with "Native PC" timing?
(08-13-2024 07:45 PM)ArtMov Wrote: [ -> ]Thanks for the answer, where can I check the boot resolution in cru?
The boot resolution isn't controlled by the EDID. If it's a BIOS machine, it usually boots in text mode, and then Windows switches to a graphics mode for the boot logo. If it's a UEFI machine, the resolution depends on the firmware. You would need to find out what resolution it's trying to send. Usually it's one of the 60 Hz established resolutions.
(08-15-2024 07:18 PM)ToastyX Wrote: [ -> ] (08-15-2024 03:53 PM)Jen Wrote: [ -> ]I was trying to add some wierd resolutions (all below 300.99mhz and 16:9)
1920x1080@138
1793x1008@158
1424x801@247
Since they don't seem to work at the moment, does that mean I'm stuck at 1920x1080@120, until I get a new pc?
Seems that way. It doesn't even support 1920x1080 @ 240 Hz with HDMI 2.0 even though it supports HDMI 2.0 for 2560x1440 @ 120/144 Hz, and they could have supported 1280x720 @ 240 Hz with HDMI 1.4. Have you tried 144 Hz at a lower resolution like 1600x900 with "Native PC" timing?
I managed to go 144hz on 1280x720, 1600x900, and one of my wierd resolutions 1792x1008. It seems to be capped at 144,but when I go to 1080p nothing over 120hz workshop. Doing 1280x720@240 native pc actually worked :o
Edit: Every custom resolution works so long as it's not a custom mode line (native pc, exact, etc all work except manual for some reason)
I managed to pull of 1280x720@295, but it would be really nice to get custom modelines working on this monitor. Do you happen to know why the custom timings don't work?
question: do the RX 56, RX 64 and Radeon VII support interlaced resolutions???
(08-15-2024 08:05 PM)Jen Wrote: [ -> ]I managed to go 144hz on 1280x720, 1600x900, and one of my wierd resolutions 1792x1008. It seems to be capped at 144,but when I go to 1080p nothing over 120hz workshop. Doing 1280x720@240 native pc actually worked :o
Edit: Every custom resolution works so long as it's not a custom mode line (native pc, exact, etc all work except manual for some reason)
I managed to pull of 1280x720@295, but it would be really nice to get custom modelines working on this monitor. Do you happen to know why the custom timings don't work?
Well, "Exact" is a custom timing. It's up to the monitor's firmware. Some monitors are generous and will accept most timings, while others are more strict or might not have any obvious logic. I once had a monitor that would accept 80-83 Hz with certain timing parameters but not 75-79 Hz no matter what I tried. It's basically trial and error.
It might only support certain combinations of resolutions and refresh rates. It might reject a resolution if the horizontal or vertical blanking is too low. It might only accept timing parameters that are similar to certain standards. Horizontal values that are multiples of 8 are more likely to work. Reducing the vertical back porch is most likely to work first, followed by the horizontal back porch.
"Native PC" for 1280x720, 1600x900, and 1920x1080 match the timing parameters it supports by default for 60 Hz, so those resolutions might behave differently.
(08-15-2024 08:55 PM)juanme555 Wrote: [ -> ]question: do the RX 56, RX 64 and Radeon VII support interlaced resolutions???
Those are GCN GPUs, which should support interlaced, but I don't know if the driver includes support for it. If it does, it would be with HDMI only.
(08-15-2024 10:30 PM)ToastyX Wrote: [ -> ] (08-15-2024 08:05 PM)Jen Wrote: [ -> ]I managed to go 144hz on 1280x720, 1600x900, and one of my wierd resolutions 1792x1008. It seems to be capped at 144,but when I go to 1080p nothing over 120hz workshop. Doing 1280x720@240 native pc actually worked :o
Edit: Every custom resolution works so long as it's not a custom mode line (native pc, exact, etc all work except manual for some reason)
I managed to pull of 1280x720@295, but it would be really nice to get custom modelines working on this monitor. Do you happen to know why the custom timings don't work?
Well, "Exact" is a custom timing. It's up to the monitor's firmware. Some monitors are generous and will accept most timings, while others are more strict or might not have any obvious logic. I once had a monitor that would accept 80-83 Hz with certain timing parameters but not 75-79 Hz no matter what I tried. It's basically trial and error.
It might only support certain combinations of resolutions and refresh rates. It might reject a resolution if the horizontal or vertical blanking is too low. It might only accept timing parameters that are similar to certain standards. Horizontal values that are multiples of 8 are more likely to work. Reducing the vertical back porch is most likely to work first, followed by the horizontal back porch.
"Native PC" for 1280x720, 1600x900, and 1920x1080 match the timing parameters it supports by default for 60 Hz, so those resolutions might behave differently.
Yep! It was most likely the vertical blanking being too low. All the resolutions work now albeit with a very very slight increase in pixel clock. Thank you so much though
Also do you know why there isn't a ycc422 and 10bpc setting in Intel graphics command center? It's only RGB or ycc444 for color format and 8bpc and 12bpc for color depth.
Hi all, I'm trying to set up real display scaling (so that the non-native resolution is displayed non-native in the monitor menu, for example 720p in game and 720p in monitor menu), qhd 1440p165hz (display port) and second monitor 1080p60hz (hdmi), when I try to change something in CRU, windows stops loading and I get a gray screen and disabled keyboard and mouse (second monitor completely turns off) or it only loads from the second time, I don't understand what could be the problem. I like the display scaling behavior better in non-native resolutions, and I want to use it always. I just need to put a couple resolutions into real display scaling mode.
The confusing part is that if I set everything up and restart the driver (restart64), everything works perfectly until I restart the computer like in the example above.
(08-16-2024 09:16 PM)topmeme Wrote: [ -> ]Hi all, I'm trying to set up real display scaling (so that the non-native resolution is displayed non-native in the monitor menu, for example 720p in game and 720p in monitor menu), qhd 1440p165hz (display port) and second monitor 1080p60hz (hdmi), when I try to change something in CRU, windows stops loading and I get a gray screen and disabled keyboard and mouse (second monitor completely turns off) or it only loads from the second time, I don't understand what could be the problem. I like the display scaling behavior better in non-native resolutions, and I want to use it always. I just need to put a couple resolutions into real display scaling mode.
The confusing part is that if I set everything up and restart the driver (restart64), everything works perfectly until I restart the computer like in the example above.
If this is an NVIDIA GPU, it's a driver bug that needs to be reported to NVIDIA. Does it still happen if you disconnect the second monitor?