At the tail-end of 2014 AMD launched their Catalyst 14.12 driver set, better known as the Omega driver set. With Omega, AMD shifted their development process for the Catalyst driver set, focusing on delivering feature updates in fewer, larger updates while interim driver releases would focus on bug fixes, performance improvements, and adding new cards. The Omega release in turn was the first of these major releases, delivering a number of new features for Catalyst such as Virtual Super Resolution, preliminary support for FreeSync, and of course a number of performance improvements.

When briefing the press on Omega, one of AMD’s points was that if it was successful they were intending to make it a yearly release – in essence putting major feature updates on a yearly cadence – and after the reaction to Omega AMD has gone ahead and done just that. So launching today and serving as the cornerstone of AMD’s video driver plans for 2016 is this year’s major update, Radeon Software Crimson Edition. (Download)

Meet Radeon Software Crimson Edition 15.11

AMD and the Radeon Technologies Group first announced their plans for Radeon Software Crimson Edition back at the start of the month, in a preview/teaser of what they were working on. AMD’s initial preview focused on the UI aspects of Crimson, namely the new control panel application, Radeon Settings. And while AMD’s preview actually covered Radeon Settings in a fair bit of depth, like all good previews AMD kept everything going on under the hood for Crimson equally under wraps. As a result we have quite a bit to discuss today, with Crimson rolling out with a number of bug fixes and feature additions on top of the control panel overhaul AMD originally announced.

But before diving into matters, let’s talk about AMD’s announced release schedule for Crimson going forward. Like Omega before it, Crimson is an annual release and a cornerstone for AMD’s driver plans for the next year. Along with renaming their driver stack from Catalyst to simply Radeon Software, the Crimson branding will be sticking with this release cycle. Come late 2016, for their next major feature update the Crimson branding will be replaced with another red-themed name.

Meanwhile one point of criticism towards AMD in 2015 has been the limited number of WHQL certified driver releases for the year. AMD had plenty of beta releases over the year – averaging once a month despite the fact that the company stopped adhering to a fixed monthly release schedule in 2012 – however they only released 3 WHQL certified releases. WHQL certification is in and of itself a thorny issue – it is an additional layer of quality assurance, which is good, but it doesn’t cover game-specific bugs, which are the bulk of the bugs most gamers are going to run into – so while it’s useful it alone won’t make a driver good or bad. None the less AMD will be addressing the lack of WHQL certified releases for 2016.

AMD’s plans call for up to 6 driver releases to be WHQL certified next year, with additional beta releases as necessary as AMD already does today. Frankly the “up to” designation leaves AMD quite a bit of wiggle room in case they fall short, so it’s not a very solid promise. But on the other hand it’s legitimately difficult to plan for a specific number of WHQL releases a year in advance – one can’t predict bugs – so AMD does need some wiggle room in case they can’t meet that schedule. That said, if AMD wants to seriously address the complaints about the lack of WHQL releases in 2015 and retain their integrity, then they need to deliver on those 6 releases for 2016.

Speaking of quality assurance, AMD tells us that they have once again increased their QA testing, and stability is a top focus for 2016. With the Omega driver AMD ramped up both their automated and human testing to cover more test cases and system configurations, and for Crimson AMD has done this again.

As drivers approach (and in some cases exceed) the complexity of an operating system, comprehensive driver QA becomes increasingly invaluable, and Windows 10’s aggressive driver update mechanism will bring driver quality to the forefront. So although AMD has never not focused on driver quality and stability, there is always room for improvement. And particularly in AMD’s case, some of the Catalyst releases have shipped with some major issues despite AMD’s QA process improvements for Omega – the web browser memory leak comes to mind – so AMD definitely needs to improve their processes to prevent future issues.

As for Crimson in particular, AMD notes that they have knocked out a large number of bugs. AMD also notes that a number of these bugs came in and/or were prioritized via user feedback, so they’re asking that we remind everyone that AMD has a bug reporting form and that they’re encouraging anyone experiencing a driver bug to use it.

Under The Hood: DirectX 9, Shader Caching, Liquid VR, and Power Consumption
Comments Locked


View All Comments

  • tuxfool - Tuesday, November 24, 2015 - link

    If You never get that, then clearly it isn't happening to anybody else.
  • Glenn37216 - Tuesday, November 24, 2015 - link

    Me neither .. I have 970's , 980's , 980ti's ... hmm maybe he needs to quit going to pornhub so much !
  • Alexvrb - Tuesday, November 24, 2015 - link

    Nobody likes a quitter! Besides, it doesn't crash on an AMD GPU- I MEAN-- nevermind...
  • looncraz - Tuesday, November 24, 2015 - link

    I've had to fix issues like that on both sides when using multiple monitors.

    This new driver from AMD, though, is awesome! I can now set a simple low global clockspeed, then set speeds per game, without all of my previous profile work. And framerate control is fantastic, I set the default at 60fps, then set just a few games to go faster. My default clocks are -45%, -40% lower power, and 500MHz RAM (default is 1250). It goes back up to stock for BF4 and Hitman. Other than that, nothing I play requires the full power of an R9 290 (not even Crysis), and some games hit stupidly high framerates.
  • AS118 - Tuesday, November 24, 2015 - link

    Yeah, that's true. I've used Nvidia and AMD drivers, and while both are actually pretty good, I noticed that Nvidia's faster drivers can be buggier, even if they're WHQL, whereas AMD's instabilities are usually found more in the betas. They may take longer to put out WHQL drivers, but I find that they're more stable because of it.

    That said, near about 90% of the time, I've had no trouble with Nvidia or AMD drivers, even the beta ones. I don't use Crossfire / SLI or the latest tech though. That generally leads to more issues, especially if you combine them (using 2 of the just released cards in Crossfire, etc.)
  • dkizzy - Tuesday, November 24, 2015 - link

    Dude forget these haters. I still have that problem on my BenQ XL2420Z 144hz. I have to run it at 120hz to get the card to clcok down on the desktop.
  • looncraz - Tuesday, November 24, 2015 - link

    People don't seem to realize that even AMD's beta drivers would probably pass WHQL testing. Doesn't make much sense to have a main branch that isn't in an acceptable state. The beta drivers are just branches of the WHQL'd drivers with a few fixes applied.

    More WHQL drivers means absolutely nothing.
  • bolek - Thursday, December 17, 2015 - link

    This. No drivers, beta or not, are released without running WHQL tests internally. The official WHQL certification matters for OEMs like Dell or HP, but has zero impact on gamers.
  • Dalamar6 - Wednesday, November 25, 2015 - link

    Both companies have their ups and downs, but there is no excuse for AMD's crippling rolling release linux distributions because they never update drivers. For months/years on end.
  • Oxford Guy - Thursday, November 26, 2015 - link

    Don't forget the magical "mouse does nothing for a while" syndrome that was also a virtue of at least one, if not more, of their driver releases.

Log in

Don't have an account? Sign up now