![]() Whereas programs like Afterburner load the card's default values and allow the user to tweak on a granular basis, Wattman loads its own values, and "resetting" it sends it back to Wattman default, not card default. ![]() I freely admit my ignorance is a large part of the problem here, but AMD could do a better job of communicating this. I've submitted a ticket to AMD but I think you'd have more pull with them. We need the ability to fully disable Wattman after playing with it. Had I not used Wattman, I'd likely not have had a complaint about the noise nor discovered the defective switch. Ultimately I sent the card back to the retailer because 1) the fan was too loud, and 2) the broken vbios switch didn't let me rectify this. The overclocking itself may not always be the reason why default Radeon WattMan settings crash. WattMan puts settings back to their defaults between games to avoid carrying overclocking parameters indicated for one game into another where they don't apply. The whole time I thought my card was defective (it was for other reasons, vbios switch didn't work), because the fan was louder than Sapphire intended. What caused WattMan crash This is a byproduct of a feature meant for their convenience. I had no idea that it was still adjusting the fan curve despite being "reset" to "default" settings. I "stopped" using Wattman with my Sapphire Nitro+ OC because I just wanted to use the card as it was out of box.
0 Comments
Leave a Reply. |