Caporegime
-
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
- Thread starter LtMatt
- Start date
Soldato
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. 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.
I did expect this answer tbh it's one feature I wish my BenQ XL2730Z had.
Same thing here, on old drivers with FS working in fullscreen windowed.
what GPU are you using?
Suspended
- Joined
- 18 Oct 2002
- Posts
- 31,179
Shanks, tested Division earlier in Windowed (Full Screen) and Vsync is def off (Win 10)
Soldato
I thought all windows application that are not true fullscreen get vsync added to them from Windows DWM?
Windows 10, like Windows 8 before it, forces the use of the Desktop Window Manager. (desktop compositor)
This means that any application running in a window will have triple buffering applied to it.
If you disable V-Sync in a game that is running in a window, the framerate will be uncapped and is no longer synchronized to the refresh rate - as expected. However you won't get any screen tearing because triple-buffering is applied via the DWM.
If you want to disable V-Sync and still get screen tearing, run the game in fullscreen exclusive mode. That way the game should bypass the DWM."
Suspended
- Joined
- 18 Oct 2002
- Posts
- 31,179
I think their are issues with the Div and DX12 currently, esp regarding windowed and fs modes. It's probably affecting it somewhat.
R9 Fury
DirectX 11 has the exact some issue with freesync for me in that game.
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.
I'm looking into this one.
Permabanned
Hello, While you're here please can you add my 2560x1080 score to the scoreboard in the Dirt 3 bench thread and the 3440x1440 score to the Dirt Rally bench thread, Thanks.
Last edited:
Good news. Thanks
Soldato
Thanks Matt.
Maybe placebo, however it looks like freesync on the Nano works on windowed mode, but not on fullscreen with 17.1.1 (the other guy who reported something similar with 16.9 made me try it).
Also maybe put in the AMD employee suggestion box to add a property (on/off) with the drivers to display a tiny logo or light to display if Freesync is working, somewhere on the screen?
No need for something elegant
And a big thanks to whom ever is responsible for allowing my Nano to clock 1150 now
(using the AMD UEFI firmware nothing else).
Last edited:
Soldato
Just installed 17.1.1 in anticipation of RE7 being released but have just tried to play Dead Space and am getting flickering on Issac (main character) and the mouse is really unresponsive trying to turn in any direction. Guess I'm going to have to roll back to 16.12.2. This is the first time I've ever encountered any issues with a driver so pretty disappointed - I hope RE7 runs ok on this driver or they fix 17. whatever...
Edit: Ok so rolled back to 16.12.2 and I've got the same issue?? Wasn't happening before and I'm about half way through the game. Perhaps something to do with installing a new driver mid game or something however unlikely that sounds - going to reinstall 17.1.1 and set the graphics options again to see if that makes a difference...
Nah... still not working. I'm playing Dead Space through Origin but just tried Crysis 3 which is also through Origin and it's fine. Bizzare. I was really enjoying the game too... Think I'll just stick with 17.1.1. for now.
Edit: Ok so rolled back to 16.12.2 and I've got the same issue?? Wasn't happening before and I'm about half way through the game. Perhaps something to do with installing a new driver mid game or something however unlikely that sounds - going to reinstall 17.1.1 and set the graphics options again to see if that makes a difference...
Nah... still not working. I'm playing Dead Space through Origin but just tried Crysis 3 which is also through Origin and it's fine. Bizzare. I was really enjoying the game too... Think I'll just stick with 17.1.1. for now.
Last edited:
Have you tried disabling 'Shader Cache / AMD Optimised' in the graphics setting? Think there is an option to clear them as well and/or a folder in c:\amd you can clear out.
Sounds like it got worse for you but I think DS always had a reputation of being a bit bad on mouse. IIrc, I played through it with a pad but that was years back.
Sounds like it got worse for you but I think DS always had a reputation of being a bit bad on mouse. IIrc, I played through it with a pad but that was years back.
Hope you can help us get a fix for this one.
No matter what I try (DX12, DX11, fullscreen, windowed,...) it's been months since I could get Freesync working on the game with my Fury
Got an old driver issue, hoping someone can help with.
My other system that is just used for light gaming still has a 5850 in it. Recently the clocks keep getting stuck. The clocks are suppose to be 157/300 at idle and 760/1050 under load. For some reason though, the clocks keep getting stuck at 400/900. They don't clock up or down and just sit at that causing fps issues.
A reboot cures it, but it's annoying. The 5850 is a legacy card so is on the 15.7.1 driver which is the last pre-crimson driver. There is one driver after which is a crimson beta, but is bad and constantly crashes.
It never used to do it, the only thing that has changed between it starting this nonsense are being fine was a Windows update.
Any ideas? No other driver to go to. Is there a way to restart the driver without rebooting?.
My other system that is just used for light gaming still has a 5850 in it. Recently the clocks keep getting stuck. The clocks are suppose to be 157/300 at idle and 760/1050 under load. For some reason though, the clocks keep getting stuck at 400/900. They don't clock up or down and just sit at that causing fps issues.
A reboot cures it, but it's annoying. The 5850 is a legacy card so is on the 15.7.1 driver which is the last pre-crimson driver. There is one driver after which is a crimson beta, but is bad and constantly crashes.
It never used to do it, the only thing that has changed between it starting this nonsense are being fine was a Windows update.
Any ideas? No other driver to go to. Is there a way to restart the driver without rebooting?.
Could be the hardware acceleration option in either a browser or a chat program like curse voice that keeps the clocks locked. i had that problem once with chrome i believe and listening to youtube in the background while playing a game. It would mess with the clock and lock it lower than full speed.
Something weird happened today..
I was using driver 16.11.4 and I got a notification that it was available a new updated driver, even that I disabled this before.
I declined the update, a couple of seconds after my screens started to flicker and I got that windows warning sound that a new device was found, I restarted my pc and it got stuck when loading windows, so I restarted again and when it got back to windows it was showing only 2 GPUS, I have 3 and the driver version was 16.6, instead of 16.11.4 that I was using before.
I removed the AMD driver, installed back the 16.11.4 and now it is working as usual.
I have a friend that had a problem after this update alert, he has one GPU only and after this update message his pc got frozen and he had to restart, he was using the 16.6 driver already.
I was using driver 16.11.4 and I got a notification that it was available a new updated driver, even that I disabled this before.
I declined the update, a couple of seconds after my screens started to flicker and I got that windows warning sound that a new device was found, I restarted my pc and it got stuck when loading windows, so I restarted again and when it got back to windows it was showing only 2 GPUS, I have 3 and the driver version was 16.6, instead of 16.11.4 that I was using before.
I removed the AMD driver, installed back the 16.11.4 and now it is working as usual.
I have a friend that had a problem after this update alert, he has one GPU only and after this update message his pc got frozen and he had to restart, he was using the 16.6 driver already.
Last edited: