AW2523HF 360Hz cursor skipping

[Calypto]

Hello, I decided to try the AW2523HF. However, I've had many issues with it since I have a radeon GPU.

The first issue I've had and somewhat managed to resolve was the refresh rate was stuck at 30Hz, unless I created a dword:

Code: Select all

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000
DalSupportExternalPanelDrr=0

While this fixed the 30Hz refresh rate limit issue, FreeSync was unavailable under radeon settings. Finally, I found that enabling "Smart HDR" in the OSD fixed the 30Hz issue and allowed FreeSync to be toggled. However, Smart HDR is disabled by default, so I imagine the potentially 5 other people with radeon GPUs that will also end up buying this monitor will run into this issue.

The next issue which I haven't been able to resolve is cursor skipping at higher refresh rates (~300+), and is the worst at 360Hz. I haven't noticed any frame skipping, yet the cursor doesn't get drawn every X amount of refreshes. This behavior did not exist on the Acer X25 360Hz, and this behavior does not exist when using the monitor with my iGPU. It happens on every OS I've tried (Win7, 10, and Troonix).

[Discorz]

The next issue which I haven't been able to resolve is cursor skipping at higher refresh rates (~300+), and is the worst at 360Hz. I haven't noticed any frame skipping, yet the cursor doesn't get drawn every X amount of refreshes. This behavior did not exist on the Acer X25 360Hz, and this behavior does not exist when using the monitor with my iGPU. It happens on every OS I've tried (Win7, 10, and Troonix).

This sounds like the issue I had with M32Q and AMD. Even tho it passed frame skipping test, mouse was very obviously skipping (not the insufficient polling rate). Took me a while to figure it out. Turned out clock speeds of OC refresh rate were ever so slightly too high. In case of M32Q anything above 660 Mhz was mouse skipping even though it could technically go up to 690 Mhz. Reducing vertical totals in CRU by couple lines reduced the clock speeds and fixed it.

[Calypto]

I appreciate the response but unfortunately that isn't a viable solution since it's already a 100MHz difference from 360Hz to 300Hz and it still happens at 300Hz unless I restart the display, only for it to come back after the the GPU driver restarts.

The monitor seems ok apart from the amd-related issues, but it's definitely a budget monitor: the OSD is laggy, the joystick is the only OSD button, no option to disable deep sleep in OSD, pressing the OSD button doesn't immediately enter you into the main menu, and no way to immediately check the monitor's refresh rate. But garbage firmware isn't exclusive to Dell so it's always a pick and choose type of deal with the various vendors.

[Discorz]

Try searching for resolution timings from someone with same panel. And have you compared with iGPU timings?

[Calypto]

Is there a program that shows the current timings? CRU only shows EDID timings, but it doesn't even show the extension blocks when on the iGPU.

[Discorz]

Try with radeon software > display specs. Although I'm not sure how it works with igpus.

[Calypto]

I don't see a reason for the iGPU to use anything other than the EDID resolution, it's on AMD to fix it (they won't).