AMD Discontinues Monthly Driver Updates, Releases Catalyst 12.6 Betaby Ryan Smith on June 1, 2012 9:00 AM EST
The last month or so has been one of transition for AMD’s Catalyst driver crew. Alongside the launch of AMD’s Trinity APU – complete with what’s only AMD’s 2nd VLIW4 GPU – AMD has also been hard at work on preparing their next Windows 8 drivers, and on the development side of things AMD also put plans into motion to move their DX10 GPU families to legacy status. Capping this off, AMD’s driver team is embarking on one more change, and for long-time AMD followers it’s going to be a doozy.
For the better part of a decade now AMD (née ATI) has released new WQHL-certified video drivers on a monthly basis. In principle this enables AMD to offer driver updates on a predictable schedule, and to spread out major driver changes over a few versions of the driver. In practice this is exactly how things have worked up until the last couple of years, which is why we’ve been fans of AMD’s driver update schedule for the longest time.
ATI Catalyst 3.8
With that said, that time has come to a close. AMD has announced that starting with Catalyst 12.6 AMD will be ceasing their monthly driver update schedule in favor of releasing drivers on a dynamic/as-needed basis, effectively taking up NVIDIA’s driver release schedule. Instead of 12 monthly WHQL releases plus a smattering of beta and hotfix drivers, AMD will have what we’d estimate to be around half as many WHQL releases alongside an unknown number of beta driver releases. It’s a significant change for AMD’s Catalyst crew and one we’re glad to see they’re making.
Why? As we briefly mentioned before, the benefits of AMD’s monthly driver release schedule were realized in practice for quite some time, but only up until the last couple of years. Starting around the release of the HD 5000 series though those benefits became harder to realize and less meaningful. The issue is at its basic level one of complexity – AMD’s drivers continue to grow in size and complexity, with the latest release weighing in at 170MB. Video drivers have effectively eclipsed Windows 95 in complexity and size in the last couple of years, which reflects the fact that these devices really have become processors, complete with all the intricacies of code compilation and scheduling, and basically in need of a mini-OS just to run them.
The result has been that AMD (and NVIDIA too) have both seen their driver development schedules become more drawn out. For AMD this has meant fewer major driver branches are released in any given year as it takes them longer to research, develop, and assemble the various optimizations and features that are added to their drivers. Consequently the need to release drivers on a monthly basis has led to some driver releases that bring few if any changes, as AMD has no new additions to that driver branch as they work on the next branch. In other words, AMD’s monthly commitment meant AMD had to release drivers whether they had something new or not.
Really this branch problem came to a head in the later part of last year with AMD’s disastrous October driver releases where they ended up with several different drivers being released in the same month; a regular Catalyst release, a BF3 release, and a Rage release that didn’t contain the BF3 improvements. Even without a fixed driver release schedule AMD will still have driver branches and the need to manage the development of multiple branches at once – that’s just the reality of this kind of software development – but it will free up resources that previously needed to be committed to the monthly driver, and in all likelihood it will make project management easier for AMD by making it push major development along a single branch (avoiding a BF3/Rage situation).
As it stands AMD has already missed one monthly driver drop with Catalyst 12.2 (the first regular driver in the 7000 series branch), and AMD will have missed another monthly driver drop with 12.5, which missed its May deadline. It’s clear that thanks in large part to these jumps in complexity and development time that monthly driver releases have become unsustainable for AMD, and behind the scenes we’ve been prodding AMD to move to a dynamic schedule for that exact reason. This makes us all the more glad to see that rather than foolishly try to keep up with this schedule that they’re backing off from trying to release so many drivers.
Modern Catalyst Control Center
However it would be remiss of us to not point out a second, more practical reason for this change too: a reduced necessity. Prior to 2010, full Catalyst driver releases were the only way for AMD to release any kind of driver change. That changed with Catalyst 10.2, which saw the introduction of Catalyst Application Profiles (CAPs). CAPs were primarily created to ease the distribution of new game profiles for Crossfire, but in some cases more general single-GPU problems can be fixed in those profiles. By manipulating the various compatibility settings in their profiles AMD can fix some issues without requiring a driver update, such as CAP 12.4-2 which improved the performance of Max Payne 3 for both single video cards and Crossfire configurations. Larger issues still require a full driver release of course, but compared to years before the advent of CAPs there’s definitely a reduced need thanks to the separation of driver and profile.
As we stated earlier, AMD will be moving to a dynamic/as-needed schedule for driver releases. It’s their hope – as it is ours – that they’ll be able to further improve on the quality and meaningfulness of Catalyst driver releases. Certainly this will cut out the release of near-useless Catalyst drivers, whereas quality as always remains to be judged. Realistically AMD’s most immediate goal should be to do a better job of getting drivers out for major new games as necessary, as that’s something they’ve particularly struggled with and is the thing the new schedule should help the most with by freeing up resources.
To that end the Catalyst 12.6 driver, released in beta form today, will be the first such driver release. We haven’t had a chance to evaluate these drivers in depth yet, but they are from AMD’s latest driver branch and should contain the typical assortment of performance improvements and bug fixes that we’ve come to expect from a major Catalyst release.
Also, it should be noted that while AMD is changing their release schedule their naming schedule is not changing. Catalyst drivers will still be named by [Year].[Month], which unfortunately means there are going to be holes in AMD’s numbering scheme. A month without a driver will simply be empty, so they could go from 12.6 to 12.8, for example. Importantly for non-technical users however this means that they maintain the date in the driver number, making it easy to tell whether a driver is recent or not.
On that note, the one thing AMD hasn’t changed so far but bears mentioning as something we’d like to see changed is AMD’s website. It has always been difficult to find AMD’s beta drivers from inside their website, a problem that is only going to become worse with the change in the release schedule. AMD needs to use this opportunity to change their site so that beta drivers are as easy to find as WHQL drivers, something that quite frankly NVIDIA has done a solid job of.
Finally, alongside the change to their driver release schedule AMD is also instituting a new driver report form to replace the older Catalyst Crew Feedback Form, which is being called the AMD Issue Report Form. The goal is the same, but AMD is moving to this new form in an attempt to gather better feedback from users than what the old form collected. If nothing else, we hope that AMD does a better job of keeping the form visible, as there seems to have been a lot of AMD users that simply never knew about the Catalyst Crew form.
Addendum: We've been informed by AMD that with the release of the Catalyst 12.6 betas, Catalyst 12.5 has been canceled entirely. 12.6 is what 12.5 would have been, and this has special significance for AMD's DX10 generation GPUs. 12.5 was supposed to be the last monthly Catalyst release that supported those GPUs but Catalyst 12.6 beta doesn't support them. So it's not clear when DX10 GPU owners will see a new driver; if this is the start of AMD's "quarterly" update cycle, then it may be a few months, making 12.4 the final driver for the time being.
Post Your CommentPlease log in or sign up to comment.
View All Comments
g101 - Saturday, June 9, 2012 - linkOh boy, the troll returns. EVERY SINGLE article that has anything to do with AMD, and this kid/***** cogburn shows up.
Apart from writing unintelligible rubbish, you have never actually said anything worthwhile.
Really, what the ****?. Do you have absolutely nothing to do?
Anyways, although I've found certain anadtech articles to be suffering from highly questionable testing procedures and data analysis, Ryan Smith actually knows what he's talking about.
Granseth - Friday, June 1, 2012 - linkFor me the solution was to uninstall Trixx or Afterburner (don't remember wich), and everything was OK again.
And I can understand peoples frustration wit AMD sometimes, and there might be more problems there than with nVidia, but I am not satisfied with any of them. But hopefully in the future sometime it will all be excellent :)
setzer - Friday, June 1, 2012 - linkYes, that is an issue that has been a bane of dynamic voltage switching cards since the probably the 5xxx series, as up to that point the memory voltage was the same.
A solution for your problem, although not optimal is getting a bios (or altering your card bios) and disable memory voltage switching (use RBE if your card is supported), another solution is trying to return your card and switch for other brand.
And I should note that this is also a problem on NVIDIA cards.
My opinion is that there's poor quality control on the components being used by some manufacturers for some ranges of cards. Although it's also possible that your problem is originated on bad system ram or a bad psu (and yes I know it is a pain when people say that and you check and it's fine).
The cards themselves are great when you don't have any problems and a really sad problem is that for some reason (well I can think of a few reasons) publications or review sites are never plagued by these issues...
taken0prisoners - Friday, June 1, 2012 - linkYour loss dude
thunderising - Friday, June 1, 2012 - linkactually yours. AMD driver updates do not cause insane screen flickering, or overheating and possible melting of my GPUs, like nVidia's
Ooops, I said it!
silverblue - Friday, June 1, 2012 - linkIsn't he replying to the OP? If so, you're actually in agreement with him.
B3an - Saturday, June 2, 2012 - linkImmature fanboy prick.
Homeles - Sunday, June 3, 2012 - linkYou seem like you've got maturity issues as well.
Assimilator87 - Friday, June 1, 2012 - linkEh, nVidia's no saint either. It took them six months to fix an issue with their cards being stuck at 2D clocks after running F@H and the silent stream bug on GF100 cards is a problem that has persisted for over a year with no fix in sight. Threw in a 6970 to replace my 470 and 465 and it works flawlessly with my receiver.
Sufo - Friday, June 1, 2012 - linkhaha, yeah I'm with you. As a long time owner of multiple ati and nvidia cards, I'll say that my experience has led me to believe that AMD drivers are consistently more problematic. I currently run 5850s in xfire and they have been an absolute nightmare. Doesn't help that my 2 biggest games over the past 3 years have been BC2 and BF3 - but these aren't the only ones where I've been scuppered by shitty drivers.
Fanboys who want to justify their purchases always charge into these discussions to the cries of "BUT THEY'VE COME A LONG WAY" and yes, they have, but they still suck. Fixes are too slow to come out. xfire profiles will be released with bugs time after time.
I realise that the current slew of nvidia cards have had troubles with drivers, but as far as I can tell they vast majority of these issues have been with multi-monitor displays. I lived off a 7950 gtx for the longest time, a time when I was gaming muuuch more than I am now and I never _once_ encountered a game specific driver bug. I'm now moving back to nvidia, despite having supposedly experienced AMD at its new "peak" and despite the worrying reports of issues with the 6xx series. I guess that says it all.