Radeon 17.1.1 drivers bring support for Resident Evil 7

The latest batch of AMD's Radeon drivers, version 17.1.1, is now out in the wild. The new version packs support for the upcoming release of Resident Evil 7: Biohazard, along with fixes for a raft of minor issues.

Resident Evil 7: Biohazard

AMD says that crashes in Dishonored 2 and flickering in Epic's Paragon should both be fixed. That's about it for game-related fixes. Systems using AMD XConnect would previously experience a blue screen when audio drivers were loaded. XConnect should no longer cause Solidworks CAD software to misbehave, too.

Some users were seeing black screens after installing the 16.12.1 drivers, while others were experiencing display corruption after applications woke from a display timeout. AMD says both of those issues should be fixed in this driver version. Finally, the company says that crashing issues with its ReLive software in multi-GPU configurations have been resolved.

Meanwhile, some problems still exist with flickering in Counter-Strike: Global Offensive and World of Warcraft. CrossFire systems may hang in Shadow Warrior 2 and Deus Ex: Mankind Divided. AMD notes that games running in Borderless Fullscreen mode with FreeSync enabled may experience problems in certain scenarios.

The company is still addressing a number of issues with its ReLive software. Unplugging a secondary display can cause ReLive to hang. Users with graphics cards with 4GB of RAM may see UI flicker in Battlefield 1 when recording with, while games using the Vulkan API may hang. On systems using AMD APUs, the ReLive software may not install correctly, can cause a system hang, or fail to record.

The Radeon 17.1.1 drivers and the full release notes can be found right here.

Comments closed
    • DPete27
    • 3 years ago

    Sucks that AMD/Nvidia has to release new drivers for every friggin game that launches. Talk about a sunk cost.

      • jts888
      • 3 years ago

      That’s pretty much been the deal with legacy graphics APIs and drivers: high level abstractions get presented to devs, who despite vendor support very frequently use them unoptimally or incorrectly, and the vendors have to essentially rewrite engine pipelines and bundle them into drivers to make their own products look faster and less buggy.

      The new regime of Vulkan/DX12 presents such a bare metal view of resources that drivers don’t really have an opportune place to intercede, so patches need to take place in the game engines, where you’d be inclined to believe they belong anyway.

      Conspiratorial minds might even suspect that AMD pushed this initiative in part to negate Nvidia’s substantial driver team advantage.

      • DoomGuy64
      • 3 years ago

      It didn’t use to be like this. However ever since console ports, gameworks, and dx11 came on the scene, it’s become a necessity. Especially with devs lazily porting console games. AMD has the benefit of having hardware in the consoles, and nvidia has their huge driver team, so it evens out pretty well.

      Driver updates are more of a necessity for older hardware that aren’t as efficient. Both AMD and Nvidia’s new hardware are pretty good at handling dx11, but the older hardware still needs game specific optimizations. Just goes to show how inefficient dx11 really is by itself, since you have to optimize the driver for new releases.

      It wouldn’t be a problem if devs optimized for PC as much as they did consoles, but consoles are the primary market, and it’s cheaper to just slap together a cheap port than to optimize a proper dx11 mode. The only redeeming factor of lazy dx11 ports is how easy it is for the driver teams to optimize for, which is both a problem and the solution. There isn’t a better method available, outside of forcing game devs to spend more time optimizing for the PC. That, or upgrade your hardware, which is another problem and solution, especially when the best hardware is prohibitively expensive or hasn’t even been released. The game Crysis summed up all of these problems in a single game, which is why it’s been such a long running meme.

    • vaultboy101
    • 3 years ago

    Ditched my Team Reds RX 480 (sorry Scott) for a GTX 1080 plus gsync.

    Zero regrets going back to Team Green.

    AMD Radeon GPUs really are not cutting it and it shows in their low market share!

    I highly doubt Vega will be able to equal Pascal in performance per ALU efficiency…

      • Firestarter
      • 3 years ago

      and this comment is relevant to the article how?

        • DoomGuy64
        • 3 years ago

        Probably related to how nvidia pays people to sponsor products in forums.

      • Goty
      • 3 years ago

      [quote<]I highly doubt Vega will be able to equal Pascal in performance per ALU efficiency...[/quote<] Because THAT'S a metric anyone actually cares about, right?

        • Magic Hate Ball
        • 3 years ago

        Seriously…

        That’s like saying “the GTX 1080 will never be able to compete per Mhz with a Fury-X”. That’s not a metric anyone should care about.

      • Jigar
      • 3 years ago

      I believe every word you said. /s

      • Krogoth
      • 3 years ago

      Please remove the green-tinted shades. They are making you goofy.

      • tipoo
      • 3 years ago

      “It shows in their marketshare”

      They’ve been on a recovery course since Polaris:
      [url<]http://images.anandtech.com/doci/10613/jpr_q2_2016_amd_vs_nvda_SHARE.png[/url<] Marketshare is low in spite of Polaris, but it's being assisted by it.

    • DoomGuy64
    • 3 years ago

    Bug fix driver. Installed fine, seems more stable than previous ones.

      • Concupiscence
      • 3 years ago

      Good to know. Somehow I’m part of the subset of people that never has serious issues with driver installs… Maybe I’m blessed.

        • odizzido
        • 3 years ago

        You are. I’ve had a number of problems on both sides. I don’t update my drivers unless I am having issues now.

        • RAGEPRO
        • 3 years ago

        I have literally not had one single problem with a graphics driver update since the days of Windows 98 and 3dfx. Heh.

    • derFunkenstein
    • 3 years ago

    Black screens after/during install affected a friend’s system but I got around it. Guess we’ll have to try this to see if it’s more smooth.

    • JosiahBradley
    • 3 years ago

    I really hope these finally fix crossfire in Overwatch flickering when in fullscreen. Been playing borderless since launch and keep reporting the error to AMD, maybe I need to bother Blizzard.

    • Topinio
    • 3 years ago

    16.12.2 ?

    Edit: also, WTF on driver size, 17.1.1 is 140 MB (28%) smaller than 16.12.2

    • tay
    • 3 years ago

    I get the “default wattman settings were restored” thanks to some error it thinks that I had. Of course nothing crashed as far as I could tell, it was just a wake from sleep or pre meditated power cycle.

Pin It on Pinterest

Share This