Don't Call It 'Godavari;' AMD Updates Kaveri APUs With DX12, FreeSync And VSR Support

It's not that often that you see a product in the computer hardware market last as long as Kaveri has. First shown to the world at CES 2014, AMD's desktop APUs have maintained relevance for the last 18 months, and show no signs of stopping now.

A new driver released today brings cutting edge technology to the aging platform. With it comes support for both DirectX 12 and FreeSync. These new cutting edge technologies have just breathed new life into all existing Kaveri-based APUs, ensuring even more performance is yet to be seen from these all-in-one processors. 

Latest Videos FromTom's Hardware
Contributor

Kevin Carbotte is a contributing writer for Tom's Hardware who primarily covers VR and AR hardware. He has been writing for us for more than four years.

  • wtfxxxgp
    Wow. It looks potent, especially for the price.
    Reply
  • photonboy
    Please stop saying "The power of the integrated GPU can then be harnessed and used as an advantage when paired with another GPU.."

    That's a feature DX12 supports however it must be implemented by the game developer at extra time (thus money).

    We have no idea how common this will be nor what expectations we should have for support but suggesting it will just naturally occur once we upgrade to Windows 10 is very, very misleading.
    Reply
  • Puiucs
    Please stop saying "The power of the integrated GPU can then be harnessed and used as an advantage when paired with another GPU.."

    That's a feature DX12 supports however it must be implemented by the game developer at extra time (thus money).

    We have no idea how common this will be nor what expectations we should have for support but suggesting it will just naturally occur once we upgrade to Windows 10 is very, very misleading.
    i don't think game devs will have the time to implement this, but it's almost certain that game engines will implement it sometime soon (Unreal Engine, Unity, CryEngine, etc). I expect it to be a default feature in a year or 2 for the big name engines.
    Having DX12 features already implemented in the engine used for the game brings dev costs down.
    Reply
  • Bernie Fresh
    interesting. 3rd party benchmarks pending, this could make a decent steambox.
    Reply
  • photonboy
    15950012 said:
    Please stop saying "The power of the integrated GPU can then be harnessed and used as an advantage when paired with another GPU.."

    That's a feature DX12 supports however it must be implemented by the game developer at extra time (thus money).

    We have no idea how common this will be nor what expectations we should have for support but suggesting it will just naturally occur once we upgrade to Windows 10 is very, very misleading.
    i don't think game devs will have the time to implement this, but it's almost certain that game engines will implement it sometime soon (Unreal Engine, Unity, CryEngine, etc). I expect it to be a default feature in a year or 2 for the big name engines.
    Having DX12 features already implemented in the engine used for the game brings dev costs down.

    My beef is we really have NO IDEA how easy or how common this will actually be, yet I'm constantly seeing comments that imply it will simply happen like it's a given. Also similar comments about mixing AMD and NVidia GPU's or stacking VRAM.

    Even if it looks like a "simple" feature to implement it still adds not only to development time (to troubleshoot GPU combos) and technical support after release.

    Sure, I'd like to see it used but again that's not my complaint.
    Reply
  • JonnyDough
    "esports"? Really? Exercise by sitting...

    I think it's time to get a new dub name.
    Reply
  • silverblue
    "It’s not that often that you see a product in the computer hardware market last as long as Kaveri has."

    Piledriver certainly has that beat, though you did say "not that often".
    Reply
  • Creme
    It's nice that they're bringing in features like VSR to their lower end models. The igpu can run some games in 1080p or 900p, and if you own a 768p monitor, then downsampling with these chips is viable.

    They advertise DX12, I wonder if the feature level is different from other Radeons.
    Reply
  • burnneck
    15950012 said:
    Please stop saying "The power of the integrated GPU can then be harnessed and used as an advantage when paired with another GPU.."

    That's a feature DX12 supports however it must be implemented by the game developer at extra time (thus money).

    We have no idea how common this will be nor what expectations we should have for support but suggesting it will just naturally occur once we upgrade to Windows 10 is very, very misleading.
    i don't think game devs will have the time to implement this, but it's almost certain that game engines will implement it sometime soon (Unreal Engine, Unity, CryEngine, etc). I expect it to be a default feature in a year or 2 for the big name engines.
    Having DX12 features already implemented in the engine used for the game brings dev costs down.

    My beef is we really have NO IDEA how easy or how common this will actually be, yet I'm constantly seeing comments that imply it will simply happen like it's a given. Also similar comments about mixing AMD and NVidia GPU's or stacking VRAM.

    Even if it looks like a "simple" feature to implement it still adds not only to development time (to troubleshoot GPU combos) and technical support after release.

    Sure, I'd like to see it used but again that's not my complaint.

    If only AMD can invest with their own game publishing company that would support their innovative solution. It will be easier for developer to invest time programing for those solution, as there would be a test case for them to follow suite.
    Reply
  • red77star
    All marketing mimmick especially talk about DX12. At the end of the day you still need decent video card to push frames, your games won't magically work better because of DX12 which seems only selling point for Microsoft in regard to Windows 10.
    Reply