The AMD Driver Thread

[nashathedog]

So does the hotfix make the performance better or what?

not really but for me it now runs silky smooth until the presumed memory leak hits and then it's like flipping a switch.

I can play around 30 to 40 minutes with no issues then it becomes a stuttery mess. A restart fixes it and then I get another 30 to 40 minutes before it happens again.

 

[nashathedog]

Suggestions please.

I was looking through my installed folder with the intent of making sure all programs like Trix and GPUTweak where removed. I had a brainfart moment and saw my AMD folder as ASUS so I deleted it.
That shouldn't be a big deal right? I simply reinstall the crimson driver.
WRONG.

Now I can't get Crimson. I have reinstalled the drivers, even by going back and trying to install the first one thats there and then installing the new 16.1.1 hotfix on top but nothing works. I've made umpteen attempts and every time I get the same result, Everything seems fine but there is no Crimson program for me to be able to do things like use the fps lock. I've spent over an hour now, Installing, testing, reinstalling testing, wiping clean, installing testing but no crimson.

This should have been a simple thing to correct but it's not.

Can someone explain how to fix this please.

 

[Diagro]

Suggestions please.

I was looking through my installed folder with the intent of making sure all programs like Trix and GPUTweak where removed. I had a brainfart moment and saw my AMD folder as ASUS so I deleted it.
That shouldn't be a big deal right? I simply reinstall the crimson driver.
WRONG.

Now I can't get Crimson. I have reinstalled the drivers, even by going back and trying to install the first one thats there and then installing the new 16.1.1 hotfix on top but nothing works. I've made umpteen attempts and every time I get the same result, Everything seems fine but there is no Crimson program for me to be able to do things like use the fps lock. I've spent over an hour now, Installing, testing, reinstalling testing, wiping clean, installing testing but no crimson.

This should have been a simple thing to correct but it's not.

Can someone explain how to fix this please.

You go to the recycle bin, and restore the AMD file... Most basic thing ever.

Unless you emptied the bin in which case you knew what you were doing and it wasnt a mistake

 

[nashathedog]

You go to the recycle bin, and restore the AMD file... Most basic thing ever.

Unless you emptied the bin in which case you knew what you were doing and it wasnt a mistake

Very helpful thanks but you do not get stuff in the recycle bin when you use the uninstaller. As I said I had a brainfart moment and was mistaking AMD for ASUS. I realized pretty quickly and tried to cancel mid process but it simple tells you to wait until it's finished what it's doing by which time it's too late.

 

[fs123]

Very helpful thanks but you do not get stuff in the recycle bin when you use the uninstaller. As I said I had a brainfart moment and was mistaking AMD for ASUS. I realized pretty quickly and tried to cancel mid process but it simple tells you to wait until it's finished what it's doing by which time it's too late.

Have you tried using DDU to totally remove all traces of AMD drivers and then re-installing Crimson?

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

[anthony566]

Have you tried using DDU to totally remove all traces of AMD drivers and then re-installing Crimson?

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

rs123

I did a very similar thing a while back and DDU did fix it ... just install it and it will boot you into safe mode and find and remove whats left so your system is clean then it reboots back into windows where you can do a fresh install.

 

[Nexus18]

I always use DDU before installing new drivers, takes a bit longer but worth it.

 

[LoadsaMoney]

Assuming 1.3 is still beta - I think it is, I haven't seen my copy update in a while - I would think you could just uncheck the beta participation box then validate the game files and in theory (imo at least) it should patch the game back to 1.2, as 1.2 would be what it's validating against in steams servers

I read it wasn't now, supposedly changed on Monday, and if you go to the beta properties page, you should see that you are no longer opted in.

 

[ED209]

I always use DDU before installing new drivers, takes a bit longer but worth it.

likewise, i use DDU as well to remove old before re installing new ones

 

[nashathedog]

Have you tried using DDU to totally remove all traces of AMD drivers and then re-installing Crimson?

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Although I've used ddu in the past I've never needed too before so yeah I'll have to try that later.
I can't be bothered right this minute as I've wasted ages on it already and it's working fine apart from the fact the Crimson program isn't there so I'm going to play some ROTTR which is behaving itself in the village valley and I'll try ddu this evening, Cheers.

 

[thebennyboy]

Changing texture quality from high to very high instantly doubles VRAM usage on ROTTR for me pretty much, seems a very steep increase in VRAM usage.

Spoiler

 

[BluD]

Changing texture quality from high to very high instantly doubles VRAM usage on ROTTR for me pretty much, seems a very steep increase in VRAM usage.

Thats strange, it doesnt make as much difference for me, on high i have 3gigs use and on vhigh i have 3.9 same as you.

 

[thebennyboy]

Thats strange, it doesnt make as much difference for me, on high i have 3gigs use and on vhigh i have 3.9 same as you.

I used the Very High preset to test it out. I only changed the Texture Quality setting to High after that, the only thing turned off was Motion Blur as i don't like it.

 

[LoadsaMoney]

Looks like us Fury owners are going to have to downgrade to the 300 series if we want to play ROTTR, as we don't have the VRAM for it.

 

[thebennyboy]

Looks like us Fury owners are going to have to downgrade to the 300 series if we want to play ROTTR, as we don't have the VRAM for it.

Or pretty much all AMD customers besides those with 300 series cards.

 

[ICDP]

Looks like us Fury owners are going to have to downgrade to the 300 series if we want to play ROTTR, as we don't have the VRAM for it.

I'm running at 4K on a single Fury Non-X and am only getting stutters at the start of a missionduring loading. FPS is sitting around 40 with Freesync and is very playable to me in the Soviet Installation level (subjective of course).

 

[TonyTurbo78]

Or pretty much all AMD customers besides those with 300 series cards.

yay ban removed, love you mods nothing better to do

shame we can't get crossfire working on said 390 cards lol

 

[Nexus18]

yay ban removed, love you mods nothing better to do

shame we can't get crossfire working on said 390 cards lol

And ban again in....

 

[nashathedog]

yay ban removed, love you mods nothing better to do

shame we can't get crossfire working on said 390 cards lol

I thought the new driver had a working profile for ROTTR.

I know GTAV's new profile came out the door broke thanks to some amazingly intuitively timed "we have finished our patch extra's" from Nvidia Not that I'm implying anything but you know, like space time is big

 

[TonyTurbo78]

I thought the new driver had a working profile for ROTTR.

I know GTAV's new profile came out the door broke thanks to some amazingly intuitively timed "we have finished our patch extra's" from Nvidia Not that I'm implying anything but you know, like space time is big

I've heard it's not the best, I can't tell I've not got the game.