Discussion in 'Videocards - AMD Radeon Drivers Section' started by Hilbert Hagedoorn, May 4, 2017.
Card stuck at max clock and 100% usage.
OC working with Wattman, unlike before
Can't believe you are still around.
Why don't you just buy a Nvidia gpu and GTFO already.
You'r post looks like its from google translator and already feels incoherent from its original form.
You bring zero relevance and banter on like a cry baby. Its pathetic.
What are you doing it's more pathetic. Defending a bad service or product it feels far more incoherent. I have bought everything since hd2600 up to r9. Drivers took the way down. This year, I like 16.7.2, 16.11.5 or 17.2.1. But why that gap exist? Aren't they professionals?
Wolfenstein NO doesn"t work still.Used ddu in safe mode but didn"t help. The only thing i quess is my win 10 has no creator update. On 17.4.4 works fine.
Drivers took the way UP for me since i bought the R9 380...i see only improvements for my card..
Now wattman doesnt save setings after reebot on my rx480 nice....anyone with this issue on RX4xx cards?
Agonist is right though. Everytime its same thing with you. You talk some crap and leave.
Buy an nvidia card and just go there already.
Is there anything specific I have to do before WattMan will allow me to increase core voltage? I can reduce core voltage, and I can increase memory voltage, but I can't increase core voltage.
Does overriding game settings work for anyone? I don't think it has been working for a few drivers now.
It was working for me on 17.4.4, but not with 17.5.1. May have to do with the profiles. Probably needs to be fresh installed.
Perfect on my side, seems working like a driver, so far for now.
Radeon WattMan may fail to apply settings on some Radeon R9 390 series graphics products
I'm happy.. I had reported the issue to AMD and even though they took a while I'm glad they took care of it. Solved for me, Cheers.
Promising start, for the first time in a while my pc booted to desktop first time and no Wattman error message by the clock.
Also, for those who like me, have a problem with monitor not coming back from sleep mode, and also having more than 1 monitor , here my hints ( this occurs since 17.x.x)
when you uninstall old drivers, using amd , or DDU, they do not clean up old unused monitors .
then if you have some trouble to get out your monitor(s) from sleep mode, just :
- open a cmd in administrator mode (runas)
- type set devmgr_show_nonpresent_devices=1
- then type devmgmt.msc
- in disply menu , select "display hidden devices"
- in monitor category, just delete old monitors entries (the grayed ones)
Good driver so far. OpenGL performance seems a little better too (though I haven't done any proper testing).
Hmm, so far it's OK.
It's still installed
Nice find. This helped with my color depth not changing to 8bit problem.
I dont ever DDU unless I have an issue. I run 3 monitors. All work upon waking up on every 17.X driver.
I just install new drivers ontop of old ones. Rarely have an issue. Like 1% of the time.
But thanks for what you posted. I saved it in a text doc on my backup drive.
EDID overrides working great with this.
FH3 works really good now. Performance is good. No artifacts now.
Still long load times even with a nice SSD.
Having freesync work with Nascar Racing 2003 is just AMAZING.
So damn smooth now.
Welp, still no fix for the atrocious CFX performance in Andromeda. TAA, FXAA, nothing fixes it.