Threaded Mode | Linear Mode

bones · 10-22-2017, 12:16 PM

Asus RX480 8GB, HDMI to DVI cable.

***ToastyX*** · 10-22-2017, 11:27 PM

(10-22-2017 12:16 PM)bones Wrote: Asus RX480 8GB, HDMI to DVI cable.

Using an HDMI-DVI cable makes it work like single-link DVI, which limits you to 165 MHz pixel clock. The patch is supposed to get around that, but it looks like they added another check in the driver at some point. I will look into that. For now, you should be able to get under 165 MHz pixel clock by reducing the horizontal/vertical totals. Then you won't need the patch at all. Try reducing the vertical total to 1100. If that doesn't work for your monitor, try reducing the horizontal total to 2048 and set the vertical total to 1111. That'll also get you closer to 71.928 Hz.

bones · 10-23-2017, 12:00 PM

It seems my monitor is a shitty overclocker. Reducing the vertical total fixes my VRAM speed to maximum, and reducing the horizontal total gives artifacts Sad

But I appreciate the help Smile

***ToastyX*** · 10-23-2017, 07:42 PM

(10-23-2017 12:00 PM)bones Wrote: It seems my monitor is a shitty overclocker. Reducing the vertical total fixes my VRAM speed to maximum, and reducing the horizontal total gives artifacts
But I appreciate the help

What driver were you using when it worked? It looks like the check was added in 17.7.2. I will have to update the patcher for this.

bones · 10-23-2017, 07:52 PM

Last it worked on 17.9.3. Could've it been a placebo? :/

***ToastyX*** · 10-24-2017, 12:10 AM

(10-23-2017 07:52 PM)bones Wrote: Last it worked on 17.9.3. Could've it been a placebo? :/

No, the refresh rate wouldn't have been available if the check was working.

Try this: https://www.monitortests.com/atikmdag-patcher-1.4.6.zip

timescroll · (Last edited: 10-24-2017, 01:51 AM by timescroll)

(10-24-2017 12:10 AM)ToastyX Wrote:
(10-23-2017 07:52 PM)bones Wrote: Last it worked on 17.9.3. Could've it been a placebo? :/
No, the refresh rate wouldn't have been available if the check was working.

Try this: https://www.monitortests.com/atikmdag-patcher-1.4.6.zip

Tried the new patcher . Did not solve my Freesync block problem ( FS range 30-74 with 75Hz used to make Freesync work ) . Now Upper Freesync rate should match monitor refresh rate for Freesync to work Sad

Having this problem since BETA driver . Used to work ok in 17.10.1

***ToastyX*** · 10-24-2017, 02:08 AM

(10-24-2017 01:45 AM)timescroll Wrote: Tried the new patcher . Did not solve my Freesync block problem ( FS range 30-74 with 75Hz used to make Freesync work ) . Now Upper Freesync rate should match monitor refresh rate for Freesync to work Having this problem since BETA driver . Used to work ok in 17.10.1

Then make it match. The FreeSync range is supposed to include the current refresh rate. I don't understand why you expect the patcher to solve this problem.

timescroll · (Last edited: 10-24-2017, 02:43 AM by timescroll)

(10-24-2017 02:08 AM)ToastyX Wrote:
(10-24-2017 01:45 AM)timescroll Wrote: Tried the new patcher . Did not solve my Freesync block problem ( FS range 30-74 with 75Hz used to make Freesync work ) . Now Upper Freesync rate should match monitor refresh rate for Freesync to work Having this problem since BETA driver . Used to work ok in 17.10.1
Then make it match. The FreeSync range is supposed to include the current refresh rate. I don't understand why you expect the patcher to solve this problem.

Thing is it used to work fine when it did not match . Now it just says not supported.Trying to figure out what is going on .

(10-24-2017 02:11 AM)timescroll Wrote:
(10-24-2017 02:08 AM)ToastyX Wrote:
(10-24-2017 01:45 AM)timescroll Wrote: Tried the new patcher . Did not solve my Freesync block problem ( FS range 30-74 with 75Hz used to make Freesync work ) . Now Upper Freesync rate should match monitor refresh rate for Freesync to work Having this problem since BETA driver . Used to work ok in 17.10.1
Then make it match. The FreeSync range is supposed to include the current refresh rate. I don't understand why you expect the patcher to solve this problem.

Thing is it used to work fine when it did not match . Now it just says not supported.Trying to figure out what is going on .

When it matches it results in blanking in gaming Sad

It is a common workaround to make it work . When set to 30-74 @ 75 Hz radeon drivers used to see Freesync range of 30-75 if oyu get what I mean .

***ToastyX*** · 10-24-2017, 03:22 AM

(10-24-2017 02:11 AM)timescroll Wrote: Thing is it used to work fine when it did not match . Now it just says not supported.Trying to figure out what is going on .

It couldn't have worked fine because the range needs to include the current refresh rate for FreeSync to activate.

(10-24-2017 02:11 AM)timescroll Wrote: When it matches it results in blanking in gaming It is a common workaround to make it work . When set to 30-74 @ 75 Hz radeon drivers used to see Freesync range of 30-75 if oyu get what I mean .

It's not supposed to show 30-75 if it's set to 30-74. You shouldn't need a workaround to make it work. What monitor is this?