It was just under two months ago that AMD announced the major restructuring of their graphics division, which would see the graphics division made whole once again, more than 5 years after AMD first split it up to better align with their CPU division. Placed under the control of AMD veteran Raja Koduri, it would be the responsibility of Raja and the rest of the Radeon Technologies Group to take AMD’s GPU division in a new direction and to rebuild it after the struggles of the past half-decade.

Today AMD is unveiling the first real initiative to take place under the Radeon Technologies Group banner, and that is a major rebranding of AMD’s GPU drivers and a ground-up replacement of the included control panel. At the same time, as this is the first RTG initiative, AMD and the RTG are using this occasion as their first opportunity to address the public as the Radeon Technologies Group. Typically I prefer to avoid ascribing large efforts to any one person, but in this case I think it’s safe to say that there’s a clear element of Raja making his mark on the RTG, and a desire to show how he is going to run things differently than AMD has in previous years. So for as much as today is about drivers and control panels, for the RTG today is also about the group laying out their plans for the future.

But first, let’s start with the drivers. After 13 years as the Catalyst Control Center – a name that pre-dates the AMD purchase altogether – AMD is finally doing away with the Catalyst branding. In fact, in some ways AMD is doing away with permanent driver branding altogether. 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.

Finally, AMD will be retaining their existing year-dot-month version numbering scheme for these drivers, which will now indicate what AMD considers minor versions of the software. The end result will be that the full name of a driver release will be along the lines of “Radeon Software Crimson Edition 15.11,” which will be the name of the forthcoming November driver release.

Meanwhile, along with announcing the new name for their drivers, AMD has also clarified their driver release plans over the next year, which will be fairly similar to how things have been for the past year. AMD is aiming to find a balance on WHQL driver releases – not too many and not too few – and have told us to expect multiple WHQL releases per year, likely averaging a release every couple of months. Meanwhile in between those releases AMD will publish beta driver updates as they do now on an as-needed basis. Both AMD and NVIDIA have been wrangling with the desire to balance driver update release schedules with the need to avoid making their non-gaming customers update their drivers every two weeks, and for AMD the solution will continue to be to space out beta releases between major WHQL releases. And no, they tell us, you won’t need to register with them to download the new drivers.

Moving on, launching as part of the first Radeon Software release will be the company’s new control panel, which they are calling Radeon Settings. Radeon Settings will be a ground-up redesign for AMD, with the company ditching the entire Catalyst .NET codebase. In its place AMD has built a new control panel from scratch based on the QT framework (ed: this will only be for Windows, at least for now), with the goal of giving their control panel a rather significant visual overhaul while also addressing load time complaints that go back to the earliest days of the .NET control panel.

In terms of a visual style, AMD tells us that they are aiming for a much more intuitive design for Radeon Settings, and have brought in a new UI designer as part of the process. From the screenshots AMD has shared with us so far (the press was not given a preview copy ahead of today’s announcement), besides the ever-present use of brushed metal, perhaps the biggest change is that Radeon Settings is wider than it is all, and the overall style is vaguely similar to Windows Metro/Modern with a focus on large buttons as opposed to lists and drop-down menus. It is, if nothing else, much more graphical than Catalyst Control Center is.

As for functionality changes, while feature updates are chiefly the domain of the drivers rather than the control panel, Radeon Settings will bring with it a couple of notable additions for gamers. Along with their existing functionality, per-game settings profiles can now contain individual settings for Crossfire, Overdrive, Framerate Target Control, and the Shader Cache, the first three features previously only being available globally and the latter being a new option entirely. Meanwhile under the Display settings, AMD is adding an Eyefinity “Quick Setup” option that will attempt a best-guess effort to arrange and enable an Eyefinity setup with a single click, allowing users to avoid the longer full setup routine when it’s not needed. Finally, after removing it a couple of years prior due to a security issue, AMD will be bringing back the driver update functionality of their control panel, allowing Radeon Settings to check for updates and to notify the user when an update is found.

At this point AMD tells us that the first release of the Radeon Software drivers and Radeon Settings control panel will be in Q4. However I expect that we may see it a bit sooner than that, and that AMD is shooting for November while offering a conservative ETA.

Going forward, AMD has also told us that this will be the first of multiple updates on the Radeon Software, AMD’s developer relations efforts, and the overall Radeon ecosystem. At this point AMD is setting up to execute on a multi-year plan, beginning with what the company feels is a need to be seen as being serious about software. As part of that effort the company is preparing new driver features for users, and though only briefly mentioned in passing, the new Radeon Software will ultimately bring new features for developers as well. In both cases AMD is being tight-lipped at the moment, but the messaging from the company is that they will have more to discuss on the matter later this year.

Comments Locked

88 Comments

View All Comments

  • Ryan Smith - Tuesday, November 3, 2015 - link

    Freesync/G-Sync are typically described as variable refresh. Adaptive v-sync would be the ability to dynamically turn v-sync on and off depending on the framerate, typically locking v-sync on at 60fps and turning it off if the framerate drops below that.
  • Zeus Hai - Tuesday, November 3, 2015 - link

    That's Free Sync, not adaptive Vsync. Pls read Ryan's comment for more info on them. The developer of RadeonPro left for Raptr, so it is no more. So you dont even know what you're talking about right?

    You don't see my point of having old cards? Ok, firstly I've been using them for about 6 six yrs now, been thru a lot (of frustration) with them. Secondly, when it's about time to upgrade, I'm not going with AMD again, not with those crappy drivers.

    Oh yeah, needless to say even their own Frame Rate Control doesnt work in Win 10, hahaha. They're neither talented nor listening, that's why they're going down, hard.
  • mapesdhs - Tuesday, November 3, 2015 - link

    They can add all the window dressing and flashy GUI stuff they want, what I want to know is, have they fixed DX9 CF and CF stability in general? Because atm it's terrible, so damn glitchy when I tried it with two 7970s.
  • mr_tawan - Tuesday, November 3, 2015 - link

    Personally I think going from .Net to Qt is going to benefit Linux platform. Also it would help with start up time (Qt is much faster in this regard, as it does not have to load bunch of .Net runtime to the memory). For code maintenance-vice I believe that Qt would be a nightmare, unless the people use Managed C++ code in the old CCC codebase (which is equally bad IMHO).

    They can of cause just update its UI code to be native ones so it does not look distinctively ugly on Windows, which would be their focus. I don't really know why they make a switch though.

    If it were me to choose, I would go with other toolkit that more friendly than Qt (it require a lot of custom tool likq QMake, and use pretty ugly code under the hood). Probably ... CopperSpice ? I don't know (have heard this name in CPPCON2015, it's basically a Qt fork that focus on modernize its code. No major user currenly AFAIK).
  • BrokenCrayons - Tuesday, November 3, 2015 - link

    The last AMD video card I used was a Radeon HD 6570 and that was a while ago so my personal experiences are a tad dated. Under Windows Vista and 7, I had no problems with the GPU and drivers. Things pretty much worked without me being worried about getting the latest Catalyst driver to fix some outstanding problem. When I moved that computer to Ubuntu I didn't really do much to push the card. It spent most of its time displaying web pages. There were no problems there either. I've since moved on to use NV graphics in my current big laptop (Linux Mint) and my desktop (Win7 Pro). Both are equally well-behaved so as far as driver quality is concerned, my experiences limited personal experiences make them a non-issue in my mind. I understand that not everyone will have the same results and some people are going to have pretty strong brand loyalty emotions tied to a particular product too. In the end, I really would just like to see AMD remain competitive because I certainly don't like the idea of an Intel or Nvidia that doesn't have to worry at least a little bit about what that other company is doing. :)
  • Zeus Hai - Tuesday, November 3, 2015 - link

    I dont want to see AMD gone either. But their driver team sucks, really really sucks. They only care about average fps in benchmark, and not smoothness in gameplay.

    100fps sounds super cool? No, think again. How about for the first half second, the card stutters and puts out 0 Frames, and then for the second half it pushes out 100 Frames? Still 100 frames in total for that single second, right? But if your char dies during the stutter, you might want to throw the mouse across the room rather than continue playing.
  • BrokenCrayons - Wednesday, November 4, 2015 - link

    Now that you mention it, I do remember having some inconsistent performance problems in Fallout 3 on the HD 6750 which really ought to have been quick enough to handle a game like that at 1280x1024 pretty easily. A much older GeForce 8800 GTS had no similar problems and neither does a GeForce GT 730 which are respectively a bit slower and a bit faster than the Radeon card. I didn't notice that problem in any other game, even later Bethesda stuff like Fallout New Vegas or Skyrim on the Radeon card and I wrote it off to FO3 being kinda quirky due to its age. Maybe it was an AMD-induced problem. If it was though, it was a pretty mild problem and I still played quite a bit without it being too frustrating. Then again, it's not a reflex intensive FPS with other human players where hesitation would make a big difference in the gaming experience.
  • seier - Friday, November 6, 2015 - link

    Major UI Redesigns are always a source of bugs. Drivers are inherently supposed to be stable. They should have just worked on features, stability, and performance. Oh well. I was already leaning to getting my son a GTX 970 any how. I currently have an R9 290 that I have mixed feelings about. The BIOS and as a second resort drivers should be able to keep a GPU from overheating when I don't even overclock. The nvidia GPUS use about 100 watts less power, but have a coil squeal. I guess you can't win. I do like that the R9 390 has 8GB RAM though.

Log in

Don't have an account? Sign up now