Discussion in 'MSI AfterBurner Application Development Forum' started by msi-afterburner, May 28, 2015.
I love you Unwinder!
many thanks for this awesome app...very much helpful to monitor usage and temp of CPU/ GPU as OSD in game.
Dear forum visitors,
I'm happy to announce that 4.2.0 is entering closed beta testing stage tomorrow. Hope that closed testing will take around a week as usual, then we release publicly.
After releasing 4.2.0 I'll focus on major RTSS update. The main priorities will be Mantle and DX12 support.
And some more news for Fallout 4 fans. Chris aka Drerex (the person who designed MSI AB v4 skins and a lot of skins for legacy Precision X) is working on nice Fallout 4 themed skin for EVGA Precision X16:
But due to flexibility of MSI Afterburner's skinn cross-compatibility engine, the skin is usable with AB as well.
Looking forward to it as usual, Unwinder.
A lot of people are reporting that this reports the wrong drivers when running AMDs new Crimson drivers, i can't verify myself, as gone back to the 15.9.1s now, due to the cores not locking on my cards, constantly went up and down while on the Crimsons (which a few others are also reporting).
Reported driver version is what is stored in the registry by AMD driver INF. Address that to AMD. If you peek into Crimson driver INF, you'll see that is sets Catalyst_version in the registry to 15.8. At the same time additional separate version for new control panel radeon software has been added, and this one is set to 15.11.
I'm wondering, anyone from AMD software team ever heard about backward compatibility? How do they assume diagnostic tools should report the version? You cannot rely on Catalyst version because it now stores some bogus value with Crimson, you cannot safely rely on control panel software version as well because if you do then user decide to get rid of new shiny Crimson driver without uninstalling it completely - version will be displayed improperly on any older driver (because it doesn't overwrite "new" version entry). Classic AMD.
An AMD problem then
GPU-Z will have proper reporting in next version:
Simple change to new registry key will cause wrong detection issues when older driver is installed on top of Crimson without removing it.
Yeah. This is a joke, man...
sigh. would love to see fps in fable
wrong thread sry