AMD Radeon Software Crimson Edition 16.2.1 Hotfix
Click here to post a comment for AMD Radeon Software Crimson Edition 16.2.1 Hotfix on our message forum
Octopuss
They really messed up the driver naming convention even further, and I didn't think that would be possible. Instead of removing the beta part from drivers (which only made people assume they were bad and kept crying for WHQL), and only slap WHQL onto some of them (when appropriate obviously), they decided to rename beta to hotfix, making it look even less stable. WTF...?
billydydcoen
vsr disabled at each reboot with 16.2 and this hotfix. Clean install after DDU in safe mode, Windows 10 Pro 64 bit
SimBy
Did previous version work fine for you? I have no problems with VSR it stays enabled. Same OS.
billydydcoen
Yes, no problem with the 16.1.1 release. My guess is, that it's DDU fault, because i did not used it to install 16.1.1 but i used it before install 16.2
janos666
Please explain it to me like I am a child who does not believe that dragons and wizards or sentient space aliens and underwater gas-gods exist in the same realm where AMD releases these drivers and won't accept the "purity of essence" or "memory of the water" as the only logic answer for every possible questions.
You can't possibly have a (legit) hotfix update for a version which was never even released (and as much as I can tell, there was no 16.2 stable [non-hotfix] ever).
Noisiv
This... thing of ours is called: AMD Radeon Software Crimson Edition 16.2.1
Crimson panel shows: Radeon Software Version 16.2
AMD webpage says
The AMD Radeon Software Crimson Edition 16.2.1 Driver contains the following:
AMD Radeon Software Crimson Edition 16.2.1 Driver Version 15.301.1901
There is no "15.301.1901" value in Crimson, and there is no such thing as "Driver Version" being listed in Crimson panel. Closest thing in Crimson panel is:
Driver Packaging Version
15.301.1901-160223a-299681E
And finally, there is no way in hell to find the number for particular component version (2D driver, Mantle...) on AMD webpage
grrrr....:cussing:
SimBy
What exactly are you having such a hard time understanding? There is no such thing as 'stable' GPU drivers so I'm not even gonna go into that. GPU drivers are a very fluid thing. You could say they are in a permanent beta state. Like I already said, this is not your LAN adapter.
Hotfix simply means a quick driver update that resolves an issue. Weather it's a simple CF profile (like the latest couple of hotfixes) or a quick bug fix that was widespread and very annoying to many.
janos666
Ah, forget about that. They have a history of "forgetting" to increment the visible version numbers of those modules after changing the code, so that information is not too relevant anyway.
Noisiv
It's like 2 completely different groups of ppl are working on Crimson. Developers and naming scheme guys. And they hate each others guts đuke2:
Crimson is 16.x.x, but Driver version is 15.xxx.xxx, unless its a Vulkan dev. driver.
In which case both Crimson software and Driver Version is 16.15.
Give me a break!
janos666
My problem is that AMD uses it's own arbitrary versioning scheme which is:
- seemingly incompatible with the usual templates adapted by the rest of the world (and it's undocumented, so it's hard to understand without "revers-engineering")
- it's inconsistent on it's own (which makes the empiric reverse-engineering harder, if not impossible in a sense - thus it will always remain hard to understand)
- it's in a constant flux (whenever there is a high enough number of historic record for you to think you figured it all out, it can suddenly change without notice)
Of course, due to the nature of it (relatively small number of releases and small number of coexisting branches) allows for some good "educated guesses". But that doesn't mean the system is sound. (It won't make a mad man sane if you can make some good sense out of his gibbering.)
spectatorx
In crimson panel i can see 16.2.1:
http://s7.postimg.org/vxjx73e4b/crimson1621.png
To me the most important is main versioning which is based on year.month scheme with eventual addition of number of a driver released particular month or whatever.
JohnnyK
So if I could enable crossfire with my two 7950s there'd be a profile for this game? Man, what a relief... :bugeye:
Tree Dude
That is a pretty fast release of a CF profile for them (if it is actually any good). Usually they are way behind.
Noisiv
My fault. I did not install 16.2.1 hotfix :P
(Which *** would I know if you didn't remind me!!)
Or maybe I did -> see? Im already đ
Hell if I can keep the track of such small 4th decimal point increments, combined with Hotfix suffix for a total confusion of poor me.
billydydcoen
Solved installing the latest Vulkan driver package over the 16.2.1, so imho the problem is really DDU
db87
My Crossfire profiles broke... again.
vancook
This driver 16.2.1 have the vulkan driver inside or need install other driver for vulkan ?
Agonist
Choppy gameplay may be experienced when both AMD Freesync***153; and AMD Crossfire***153; are both enabled
This is the fix I have been waiting for.
Been having to use afterburner to limit FPS because of choppy gameplay with freesync on.
the9quad
Beginning with the next driver release, the Radeon drivers will be known as âRadeon Software.â At the same time, similar to projects such as Ubuntu Linux and Android, AMD will be introducing a codename-like middle name to denote the âmajor version.â These names, which only fitting for the RTG will all be variations of red, will start with âCrimson Editionâ and will change roughly every year as AMD introduces what they consider a new major version of the software.
The way I understand it is
15.12 is "the" crimson edition, all non-whql drivers are called hotfixes delineated by the year/month plus which beta for that month. The next WHQL should just be called 16.3 crimson edition. After that until the next quarter all the betas will revert to the hotfix label and numbering scheme.
Didnt think it was that important or difficult.
primetime^
This driver appears to be the very same drivers from the vulcan release...but its has newer radean settings than 16.2....i know the older vulcan never even had the settings.
all i did was upgrade....since all it did was update the radeon settings
Radeon Settings Version - 2016.0226.1531.27895 (only thing newer for me)
Driver Packaging Version - 16.15.1009-160213a-299302E
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1546
Direct3DÂŽ Version - 9.14.10.1180
OpenGLÂŽ Version - 6.14.10.13430
OpenCL⢠Version - 2.0.6.0
AMD Mantle Version - 9.1.10.108
AMD Mantle API Version - 98309
AMD Audio Driver Version - 10.0.0.2
vulcan sdk works for me....so yes on your question
