• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

Well so far the 17.1.1 has been fine.. Beside freesync still not working in The Division or rainbow six siege everything has been fine. Installed it, enabled freesync and uninstalled radeon settings along with the hdmi drivers and kept the display drivers and games been running good so fare.. hoping it holds :)
 
If you had whql driver you need to uninstall and then install the beta.

This has happened in the past for me also using AMDs auto updater.
Seems only beta will update over beta no idea if this is intended to be or a bug.
Ok, I *think* I tried that but I'll give it another shot. Thanks :)

That's interesting*, I've had something similar to this, I never considered it being due to me having wqhl drivers installed while trying to install beta's, but I have had a driver refuse to install over a different driver forcing me to manually removing the one installed to do it, That's happened a couple of times, I'll have a look at what drivers they are next time it happens.



*It's a slow news day, Sue me, :)
 
Good to know, Thanks.

Unfortunately that applies to MMH 7 also, not only The Division -_-
Any driver after 16.11.x and freesync isn't working with those 2 Ubisoft games. Might try Anno 2250 to see if that one has issues also.....

******************(swearing at AMD and Ubisoft)***********


But there are issues with Gsync also and The Division :D a visit at Nvidia forums, is very entertaining...
 
Last edited:
I agree on that. Considering how many are here having Nvidia as religion and Jen-Hsun Huang as it's Messiah and Prophet, declaring holy war to the rest of the heretics :D

You had to do it didn't you... you had to pick a side.. alright then. Better go get armored up and cover yourself in flame retardant :)
 
Unfortunately that applies to MMH 7 also, not only The Division -_-
Any driver after 16.11.x and freesync isn't working with those 2 Ubisoft games. Might try Anno 2250 to see if that one has issues also.....

******************(swearing at AMD and Ubisoft)***********


But there are issues with Gsync also and The Division :D a visit at Nvidia forums, is very entertaining...

Luckily I haven't got The Division, I had a play during the open beta and decided to save my money and buy it once the price drops a bit, I almost bought it when it was on sale on Steam recently, I'm happy waiting and hopefully the worst of the farmers will have moved on to the next big game by then.
 
Unfortunately that applies to MMH 7 also, not only The Division -_-
Any driver after 16.11.x and freesync isn't working with those 2 Ubisoft games. Might try Anno 2250 to see if that one has issues also.....

******************(swearing at AMD and Ubisoft)***********


But there are issues with Gsync also and The Division :D a visit at Nvidia forums, is very entertaining...

the weirdest thing is for me personally Freesync is working in The division only if i use fullscreen window mode and driver 16.9.2 which doesnt support window mode freesync.. Makes no sense
 
the weirdest thing is for me personally Freesync is working in The division only if i use fullscreen window mode and driver 16.9.2 which doesnt support window mode freesync.. Makes no sense

:confused:
Some times nothing makes sense.

Like AMDs response times to Freesync and Division. At least from my experience AMD is good at this, and when they break something, they have new drivers in few working days fixing it. Right now we are 2 months with this issue.

But, I bet they might have more issues with relive to fix first. We shall see the next set of drivers. But again, there are gsync issues with the Division, which more likely looks like the engine has some underlying issues in DX12.

However the most annoying issue for me, is that the 16.11 were crap overclocking drivers for the Nano. I cannot keep it stable abovel 1050. While 16.12 & 17.1, had no issue to operate 1140 & 1150 core, while clock for clock they give 1% perf boost between them.
 
So i have been getting microstutter with ReLive recordings, someone had the same issue and posted a video.

Well i have a 75hz Freesync monitor now and have figured out that running this at 75hz with my other 2 Samsung displays at 60hz is causing the issue. Switched the Freesync monitor to 60hz and the microstutter has gone away, but playing games at 60hz vs 75hz is less smooth while actually playing.

I hope there is a fix for this, i dont wana game at 60hz anymore, this is why i bought the 48hz-75hz range Freesync monitor :(

Its the AOC G2778VQ btw.

So anybody know how i can stop the microstutter explained above?

Maybe in ReLive an 'Auto' option for the fps might fix it, i can only set to 30 and 60 fps while recording on a 75hz monitor.. like i said if i set the FreeSync monitor to 60hz i dont get any microstutter on my recordings.

Be nice if they put in an option to type in whatever fps we choose (like in OBS Studio).. until they fix this, i cant do any recordings :(
 
By working are you basing this on the fact you see no screen tear?
Because Windows and windowed mode has forced vsync applied.

I know you mean well Shankly and you possibly cannot know what everyones tech level is but i had to take a deep breath there for a second :P. The answer is: ofcourse not. My monitor will tell me through its fps meter and so will the OSD. Its also on top of this very easy to feel and see.
 
Back
Top Bottom