AMD/ATI Pixel Clock Patcher

[ToastyX]

(11-26-2022 01:19 AM)jorgeapp Wrote:  master! can you please update the fix to be compatible with latest anermine/nimez mod v22.10.3?

I'm not seeing any issues with Amernime Zone 22.10.3.

[pwner]

Do i need this if im using a DisplayPort?
Also a HDMI 2.1?

[ToastyX]

(12-21-2022 05:52 PM)pwner Wrote:  Do i need this if im using a DisplayPort?
Also a HDMI 2.1?

No.

[pwner]

ok thanks (im still run it)

[zamar19]

Hello, can you update or test it to current AMD 23.2.1 driver? Also I'm using PC with AMD RX 460 DP-to-HDMI connection from Win 11 PC to a 4K monitor & Smart TV, so not sure why you mentioned above its not needed for DP?

While this tool was the only solution for me over several years, a typical user forgets between driver upgrades, what your tool does and what problem it addresses. New users don't know it to begin with. I remember it was explained before, but now I don't see any explanation in your 1st post. Is there a reason for that, and would you be interested to add some explanation of problems it was designed to solve? And in what cases it may be useful & not useful?

[ToastyX]

(02-21-2023 02:22 AM)zamar19 Wrote:  Hello, can you update or test it to current AMD 23.2.1 driver? Also I'm using PCP with AMD RX 460 DP-to-HDMI connection from Win 11 PC to a 4K monitor & Smart TV, so not sure why you mentioned above its not needed for DP?

While this tool was the only solution for me over several years, a typical user forgets between driver upgrades, what your tool does and what problem it addresses. New users don't know it to begin with. I remember it was explained before, but now I don't see any explanation in your 1st post. Is there a reason for that, and would you be interested to add some explanation of problems it was designed to solve? And in what cases it may be useful & not useful?

23.2.1 should be compatible. Pixel clock limits are described in the CRU thread because that's where people usually run into such limits. New users shouldn't need the patcher. It was originally intended to get around DVI limits and HDMI limits on older video cards. Any card made in the past 10 years shouldn't need the patcher for HDMI, and newer cards don't even have DVI anymore. The patcher does nothing for DisplayPort. Passive DisplayPort to HDMI adapters are considered to be HDMI, not DisplayPort. You shouldn't need the patcher if you get a proper active adapter. The patcher also implements a BIOS signature workaround for RX 400/500-series cards, mainly useful for people that are mining crypto with a custom BIOS.

[zamar19]

(02-21-2023 05:24 AM)ToastyX Wrote:  You shouldn't need the patcher if you get a proper active adapter.

It looks my adapter is passive. However I didn't need the patcher for the resent driver, likely due to only one monitor hooked to the GPU via HDMI 2.1 direct. Before two monitors were hooked (1st via HDMI 1.4 to 1st TV, 2nd via DP-to-HDMI 1.4 to 2nd TV), I recall it was likely the reason to use the patcher. Updated GPU driver and thought I'd need it again.

[Zachadoodle]

Don't download the new Spring update. I've noticed some issues with the driver and the patcher. I've been getting severe drops in FPS and had to uninstall, clear the cache, and redo my overclocking settings on the AMD driver because of it. Most of all I had to revert back to 23.2.2 AMD driver getting much better performance compared to the Spring version which 23.3.1. If I were you all I'd hurry up and get 23.2.2 before the atikmdag patcher is not updated before AMD takes it off their website. ToastyX it may not seem like it is not working on the Spring version of the patch, but I would double check it. As a reminder to everyone here, don't update the driver until someone else updates you that the patcher works on it.