The AMD Driver Thread

nashathedog · 15 Jan 2017 at 10:11

shankly1985 said:
Robert from AMD says we should be using vsync with freesync for best results mainly at the lower end and it will also keep frame rate in check.

Tbh I have tested Freesync with FRTC or msi afterburner frame limiter and Freesync still working so I not truly sure why he him self says not to use it.

That's the source I'm referring too, I think it was you that originally posted it too but can't be sure, It's the high end I'm worried about, my monitor has a working range of 30 to 75 but often goes up to 100 or more depending on the game, I'll try it with v-sync on and if it's no different I'll go back to limiting it with frtc, Cheers.

MyBrainz · 15 Jan 2017 at 12:24

Well i ended up getting the 27" AOC G2778VQ which arrived on friday. Been tinkering with it over the weekend and have to say that Arma 3 Battle Royale feels like a different game and i can even higher settings from Very High to Ultra and it still feels smoother than before, not sure if this is the Freesync effect or maybe Arma had an update with a perf increase recently and i just didnt know about it, feels much better either way

I am only using Full Screen Borderless Window Mode with Vsync ON locked at 75hz/75fps in Arma 3.. and its running great

Now to DayZ Standalone.. i know this game is still in development but i was expecting Freesync to fix my stutter issues while in Borderless Window Mode.. not to be

I see players on Twitch running Nvidia and they have smooth gameplay so im starting to think that maybe AMD are not on the ball with support for this game so if @AMDMatt can enlighten me on the situation with driver support on this title it would be greatly appreciated

Its not a stutter fest, just intermittent stuttering while looking around, seems to happen when i come into a new scene of the map, a new bunch of trees or when i first enter a town.. is this a Cache issue?

I've tried allsorts with RTSS frame limiter and the FRTC in Crimson, Vsync on and off etc and still get stutter while running Borderless.. Fullscreen seems much better but i need Borderless while running 3 monitors/streaming etc

HEADRAT · 15 Jan 2017 at 13:15

HEADRAT said:
and Radeon Setting crashes, nice!

Seems to have something to do with Vulcan as if I switch back to OPENGL rendered it works fine, if I select Vulcan I just get black screen/then crash.

kmetek · 15 Jan 2017 at 18:34

hey guys relive doesn't offer much info as catalyst used to, right?

nashathedog · 16 Jan 2017 at 10:35

shankly1985 said:
Robert from AMD says we should be using vsync with freesync for best results mainly at the lower end and it will also keep frame rate in check.

Tbh I have tested Freesync with FRTC or msi afterburner frame limiter and Freesync still working so I not truly sure why he him self says not to use it.

nashathedog said:
That's the source I'm referring too, I think it was you that originally posted it too but can't be sure, It's the high end I'm worried about, my monitor has a working range of 30 to 75 but often goes up to 100 or more depending on the game, I'll try it with v-sync on and if it's no different I'll go back to limiting it with frtc, Cheers.

With regards to V-sync on am I meant to do it on a game by game basis or is it done in the Crimson Wattman software?

If in the Crimson software is it via the 'Wait for vertical refresh' option in global graphics? and if so which option? It has the 4 following options: Always off, Always on, Off unless application specifies & On unless application specifies.
Cheers

old gamer · 16 Jan 2017 at 11:05

ive never used freesync and vsync together, just freesync and cap the fps in crimson

djbully · 16 Jan 2017 at 11:24

old gamer said:
ive never used freesync and vsync together, just freesync and cap the fps in crimson

Yes, that's what I do and Freesync is fine. I just set frame limiter to 1 or 2 FPS below what you top limit is, as sometimes it will go just over the limit and lose freesync.

So for example my monitor are 35-60Hz range so I set frame limit to 59 FPS in crimson and it works a treat.

V-sync is nasty especially when using steering wheels, or flight sticks!

Phil2008 · 16 Jan 2017 at 13:33

Are the bright/con sliders back yet?

shankly1985 · 16 Jan 2017 at 13:42

nashathedog said:
With regards to V-sync on am I meant to do it on a game by game basis or is it done in the Crimson Wattman software?

If in the Crimson software is it via the 'Wait for vertical refresh' option in global graphics? and if so which option? It has the 4 following options: Always off, Always on, Off unless application specifies & On unless application specifies.
Cheers

Game by game the Crimson setting isn't for direct x it's openGL

nashathedog · 16 Jan 2017 at 15:31

old gamer said:
ive never used freesync and vsync together, just freesync and cap the fps in crimson

djbully said:
Yes, that's what I do and Freesync is fine. I just set frame limiter to 1 or 2 FPS below what you top limit is, as sometimes it will go just over the limit and lose freesync.

So for example my monitor are 35-60Hz range so I set frame limit to 59 FPS in crimson and it works a treat.

V-sync is nasty especially when using steering wheels, or flight sticks!

shankly1985 said:
Game by game the Crimson setting isn't for direct x it's openGL

Okay, thanks, I've set frtc to 74 fps

HEADRAT · 16 Jan 2017 at 17:00

HEADRAT said:
Seems to have something to do with Vulcan as if I switch back to OPENGL rendered it works fine, if I select Vulcan I just get black screen/then crash.

Any ideas why Vulcan doesn't seem to be working in DOOM in 16.12.2?

shankly1985 · 16 Jan 2017 at 17:01

HEADRAT said:
Any ideas why Vulcan doesn't seem to be working in DOOM in 16.12.2?

I can test later for you.

HEADRAT · 16 Jan 2017 at 18:56

Thank you

<edit>

Something fishy going on here, this was a fresh install of Win10 and 16.12.2, I presume that these new drivers don't install the Vulkan runtime correctly.

If I run vulkaninfo.exe I get a bit of a worry entry:

===========
VULKAN INFO
===========

Vulkan API Version: 1.0.26

WARNING: [loader] Code 0 : Registry lookup failed can't get layer manifest files

Thanks

HEADRAT

shankly1985 · 17 Jan 2017 at 01:10

Working fine on my 290 mate, check software info within Crimson and see what version you running. see my image

jupiter_man · 17 Jan 2017 at 01:42

is anyone suffering from micro shuttering in FIFA17 online mode?
I have this very weird thing going, my game running perfectly fine in any offline mode, over 100fps, however it shutter every few seconds when I am playing online (FPS is still over 100fps at all time)
Had anyone have this problem before and how did you solve it?
Thanks!!!!!!!!!
(not sure it is EA's problem or driver's problem, I have updated my driver to the latest one)

shankly1985 · 17 Jan 2017 at 02:50

Nothing here play fifa online abit

HEADRAT · 17 Jan 2017 at 06:06

shankly1985 said:
Working fine on my 290 mate, check software info within Crimson and see what version you running. see my image

If you look in Programs and Features do you just have "Vulkan Run Time Libraries 1.0.26.0" with Publisher LunarG, Inc. or is there another package by LunarG?

What do you see at the top of the output of the command vulkaninfo.exe?

My concern here is that some 16.12.2 isn't loading something it should that you might have had installed by a previous driver?

Used DDU to clean out 16.12.2 and went back to 16.11.5, still the same error in DOOM with Vulkan, I'm at a loss

(OPENGL is fine)

nashathedog · 17 Jan 2017 at 06:27

Every time I change something in my AMD radeon settings program and then attempt to shut it down using the 'X' in the top right corner it crashes & I get a Host application has stopped working message. Is anyone else getting issues like this?

I'll do a fresh install and see if that solves it.

Phixsator · 17 Jan 2017 at 07:54

I have found something weird. I've had issues with The division for a long time when it comes to freesync. Mostly because ubi made a mess of exclussive fullscreen causing it to only be borderless window mode and therefor freesync wouldnt work. Yesterday i accidently switched to fullscreen window mode instead of exclusive fullscreen (which does not work) and freesync was working...on driver 16.9.2 which is long before the suppose windowed support that came with the relive drivers.. there is some voodoo going on here.

EDIT: Quick dirty edit here.. Freesync goes broke again if i use relive drivers no matter the settings used. Window or fullscreen.. does not matter.

djbully · 17 Jan 2017 at 08:44

nashathedog said:
Every time I change something in my AMD radeon settings program and then attempt to shut it down using the 'X' in the top right corner it crashes & I get a Host application has stopped working message. Is anyone else getting issues like this?

I'll do a fresh install and see if that solves it.

I'm sure you must know DDU, that may help you.