The AMD Driver Thread

Mei · 9 Oct 2015 at 22:22

yeh just installed the new beta over the top
windows 10
no drama so far :x

kunoichia · 10 Oct 2015 at 16:29

I love how I have to use bandicam to limit my fps to 999 cause otherwise when i load up games like fifa and csgo on my new 390 it just reboots my pc cause fps shoots to like 3000.. Why is the limit on rivatuner 200..?

Dont even get me started on the 95 number in CCC..

shankly1985 · 10 Oct 2015 at 16:59

kunoichia said:
I love how I have to use bandicam to limit my fps to 999 cause otherwise when i load up games like fifa and csgo on my new 390 it just reboots my pc cause fps shoots to like 3000.. Why is the limit on rivatuner 200..?

Dont even get me started on the 95 number in CCC..

Why push frame rates that much? Csgo 300fps is fine and imo 300fps is more than enough for all games.

Finners · 10 Oct 2015 at 17:06

60FPS with v-sync is fine for a game like fifa or more if you have a higher Hz monitor. Its hardly a fast passed game.

kunoichia · 10 Oct 2015 at 17:57

shankly1985 said:
Why push frame rates that much? Csgo 300fps is fine and imo 300fps is more than enough for all games.

Well for csgo i dont want a capped fps really because of input, 300 is fine for rest tbh but why is the cap in msi 200? OR am i missing something?

shankly1985 · 10 Oct 2015 at 19:08

kunoichia said:
Well for csgo i dont want a capped fps really because of input, 300 is fine for rest tbh but why is the cap in msi 200? OR am i missing something?

Csgo at 300fps you shouldn't have any input lag. You can unlock frame rate but it's of no real use tbh
Even the pros run 300fps.

Am not sure why msi afterburner is locked at 200fps though.

LtMatt · 10 Oct 2015 at 19:13

kunoichia said:
I love how I have to use bandicam to limit my fps to 999 cause otherwise when i load up games like fifa and csgo on my new 390 it just reboots my pc cause fps shoots to like 3000.. Why is the limit on rivatuner 200..?

Dont even get me started on the 95 number in CCC..

kunoichia said:
Well for csgo i dont want a capped fps really because of input, 300 is fine for rest tbh but why is the cap in msi 200? OR am i missing something?

I sent you a mail Kun.

kunoichia · 10 Oct 2015 at 19:23

AMDMatt said:
I sent you a mail Kun.

the noob who talked me into a new amd card instead of going nvidia this time.

slick mother****er ;p

LtMatt · 10 Oct 2015 at 19:48

kunoichia said:
the noob who talked me into a new amd card instead of going nvidia this time.

slick mother****er ;p

Dial in your overclock, noob.

kunoichia · 10 Oct 2015 at 21:32

AMDMatt said:
Dial in your overclock, noob.

If i can primetest this 4500 clock all day for the last 2 years or more and crank this 390 up to 1200 / 1700 but it still happens on stocksetting and even when downclocked it aint my overclock you big knob

Anyway problem solved with a fpscap its ok really thought my psu was deaded yesterday

Went to read all the horrorstories on the interwebs with the 390 drivers and just dx11 blackscreening I already had my pitchfork out for ya and wanted to ask my supplier for a nvidia trade

LoadsaMoney · 10 Oct 2015 at 23:08

Whats the correct way to use FreeSync, as im still getting tearing (and its doing me nut in!) ?.

Im playing Metro Last Light at the minute, and im still getting it, even though im getting 143fps (capped in Afterburner) its like a ripple effect, had the same in 2033, and also get it now and again in GTA V (all while still in the FreeSync range).

What i do is, i have FreeSync on in the drivers, v-sync off in game, and i use Afterburner to cap my frame-rate to 143, so i stay within the 144.

I did a search looking for some answers, and found a thread over on the AMD forums about getting tearing still with FreeSync, and this was posted as the correct answer.

As I stated, FreeSync only works within a given range. If your frame rate goes above or below that range, you get tearing. Unless you enable vsync, which lets FreeSync do its thing within range, while letting vsync do its thing when out of range. No tearing at any frame rate.

The difference between vsync and FreeSync at precisely 144fps is non-existent. Both entail drawing a new frame every 6.944ms. At 150fps, say, vsync does exactly the same thing - draws a new frame every 6.944ms, but the GPU gets to rest for 0.278ms of that time, having completed the frame early. Without vsync, you still get a new image only every 6.944ms, but now it's partly one frame, and partly the next one - you get tearing. The fragment of the new frame will, it's true, be based on more recent information. But by necessity, that information can be no more than 6.944ms newer than the information that generated the previous frame, and on average less than half that value. You're just not going to notice that. If you see any lag at all, it's due to the monitor itself, or the game engine. At most, the tiny contribution of vsync would push it over the edge of the threshold at which you're capable of noticing a delay.

And if you're already trying to impose a frame rate limit, you're already giving yourself the same time penalty that vsync does when pegged to the maximum frame rate. So just enable both FreeSync and vsync.

Also, someone esle posted this.

What you should do is turn vsync on all the time. When both vsync and FreeSync are enabled, you automatically get FreeSync when the frame rate is within range, and vsync otherwise.

Now i thought FreeSync, took care of the input lag which v-sync causes, so there was no need to have v-sync enabled in game anymore, and also, providing your within the FreeSync range, you wouldn't get any tearing either. :confused:

shankly1985 · 10 Oct 2015 at 23:27

LoadsaMoney said:
Whats the correct way to use FreeSync, as im still getting tearing (and its doing me nut in!) ?.

Im playing Metro Last Light at the minute, and im still getting it, even though im getting 143fps (capped in Afterburner) its like a ripple effect, had the same in 2033, and also get it now and again in GTA V (all while still in the FreeSync range).

What i do is, i have FreeSync on in the drivers, v-sync off in game, and i use Afterburner to cap my frame-rate to 143, so i stay within the 144.

I did a search looking for some answers, and found a thread over on the AMD forums about getting tearing still with FreeSync, and this was posted as the correct answer.

Also, someone esle posted this.

Now i thought FreeSync, took care of the input lag which v-sync causes, so there was no need to have v-sync enabled in game anymore, and also, providing your within the FreeSync range, you wouldn't get any tearing either.

I use the same has you and they is a couple games I have noticed have issues. CSGO and TF2 and also Fifa 16 if you don't use FRTC in the drivers.

GTA5 I get zero screen tear. I even tested that by alt-tab out switch off freesync go back into game see loads screen tear, switch freesync back on and screen tear is gone.

You pointing out a very interesting debate though. Does Freesync really remove Vsync issues if you have both enabled??

LoadsaMoney · 10 Oct 2015 at 23:46

shankly1985 said:
I use the same has you and they is a couple games I have noticed have issues. CSGO and TF2 and also Fifa 16 if you don't use FRTC in the drivers.

GTA5 I get zero screen tear. I even tested that by alt-tab out switch off freesync go back into game see loads screen tear, switch freesync back on and screen tear is gone.

Yeah some games i don't see any tearing (Dying Light for example), i can't remember, but i think Metro LL is capped at 60fps, so maybe thats why im getting it.

You pointing out a very interesting debate though. Does Freesync really remove Vsync issues if you have both enabled??

Id like to know this too, as FreeSync stops the input lag v-sync causes, so why still have it enabled ?

shankly1985 · 10 Oct 2015 at 23:50

LoadsaMoney said:
Yeah some games i don't see any tearing (Dying Light for example), i can't remember, but i think Metro LL is capped at 60fps, so maybe thats why im getting it.

Id like to know this too, as FreeSync stops the input lag v-sync causes, so why still have it enabled ?

Metro LL not capped to 60fps for me mate. Let me just double check. not running new updated version though.

LoadsaMoney · 10 Oct 2015 at 23:54

Its capped at 60fps, just tried it with v-sync enabled in game, and im locked at 59.9.

Im playing the original, not the redux.

Will try v-sync off, but with AB capped to 59, instead of 143.

shankly1985 · 10 Oct 2015 at 23:56

LoadsaMoney said:
Its capped at 60fps, just tried it with v-sync enabled in game, and im locked at 59.9.

Im playing the original, not the redux.

With freesync on and vsync off I get no screen tear and avg 80fps where I was just then.

edit
I'll try with vsync on

edit
Yeah locks at 60fps even though my display is still refreshing @144hz BenQ software reports. Quick Google it seems this is a known issue with this game and Vsync.
What happens if you say lock frame rate with MSI at say 70fps do you still get screen tear with only Freesync?

LoadsaMoney · 11 Oct 2015 at 00:06

Turned v-sync back off in game, but locked the frame-rate to 59 instead via AB, and didn't get any tearing, so must be the issue.

I'll try locking to 70.

EDIT:

Didn't get any at 70 either, 143 must be too high.

shankly1985 · 11 Oct 2015 at 00:14

LoadsaMoney said:
Turned v-sync back off in game, but locked the frame-rate to 59 instead via AB, and didn't get any tearing, so must be the issue.

I'll try locking to 70.

EDIT:

Didn't get any at 70 either, 143 must be too high.

I use 135fps max if that helps

LoadsaMoney · 11 Oct 2015 at 00:15

shankly1985 said:
I use 135fps max if that helps

I'll give that a go

EDIT: hmm, not sure if its totally gone, but it looks better still, will have to have a good play.

LoadsaMoney · 11 Oct 2015 at 22:02

Just played for over an hr there, with my rate capped to 100, and didn't snotice any rippling or tearing.

Would be good to know about using v-sync with it though, as some people say.