Radeon 17.4.1 drivers engage spacewarp

AMD has updated its long-named Radeon Software Crimson ReLive Edition software to version 17.4.1. Judging from the release notes, the main focus for this release is delivering smoother virtual reality experiences through API magic. The headlining features are support for Oculus' Asynchronous Spacewarp on Radeon R9 290 series, R9 390 series, and R9 Fury series graphics cards, along with support for SteamVR Anynchronous Reprojection on Radeon RX 470 and RX 480 graphics cards under Windows 10. The new release is not as comprehensive as the major feature improvements introduced last December, but then again, driver updates seldom add anywhere near that much new stuff.

The update also enables DisplayPort High Bit Rate 3 (HBR3) connectivity over DP1.4, support for 8K resolution at 60 Hz (with dual cables), and support for 8K at 30 Hz with a single cable. The only 8K display we can think of right now is Dell's $5000 monster, but more 8K panels are surely on the way.

Every graphics driver release has bug fixes, and AMD says that this update squashes problems with display flickering when running games and applications in borderless fullscreen mode, poor multi-GPU scaling in Ghost Recon: Wildlands, and system hangs when unplugging XConnect external graphics devices. The company also says that the Radeon Settings application should be more responsive during driver upgrades.

The release notes page includes download links for the drivers for contemporary Windows operating systems, with the exception of Windows 8.1 32-bit. The notes specifically that mention these drivers are not intended for use with machines running Apple Boot Camp.

Comments closed
    • Forge
    • 3 years ago

    Yeah, the latest and greatest Boot Camp AMD drivers are from late 2015. SCREW CURRENT!

      • tipoo
      • 3 years ago

      That’s completely under Apples control. Beyond “well, it’s a working Windows machine”, they don’t give that many craps about Boot Camp. Take their trackpad driver for it vs Trackpad++ for instance.

      The Intel ones I could sometimes update directly, but not the AMD or Nvidia I take it. And updating directly always felt like building a house of cards with new bugs always popping up, while the old Apple driver would sap performance.

    • christos_thski
    • 3 years ago

    Any idea why SteamVR Anynchronous Reprojection isn’t supported on R9 Fury and the other cards? Isn’t it based on similar principles to Oculus’ Asynchronous Spacewarp which is supported?

      • Billstevens
      • 3 years ago

      Totally and completely different. Spacewarp as far as I know if the fanciest form of frame doubling right now, it legitametly predicts where the next frame will look in a 3d space and changes your visuals to approximate a fully rendered frame.

      Re-projection at least in its early formats is just plain old frame doubling and you really want to avoid it at all costs because it doesn’t feel as good to play. The Async Repro may be more complicate but I am pretty sure it isn’t doing as much as spacewarp.

        • christos_thski
        • 3 years ago

        thanks for the clarification, it appears I had the wrong notion

        • Entroper
        • 3 years ago

        To extend this, Oculus distinguishes between “timewarp” and “spacewarp”. Timewarp is able to account for the rotation of the HMD, while spacewarp accounts for both rotation and translation. My understanding is that Valve’s asynchronous reprojection is their version of timewarp, and they don’t have spacewarp.

    • allanmac
    • 3 years ago

    Should that be HBR3+DP1.3 and not DP1.4?

    • JosiahBradley
    • 3 years ago

    If only they would fix wattman and r9 200 cards or let us use the old style OC engine. It keeps conflicting with Afterburner. Going from 120fps+ to 10fps is angering when I have to do a complete Driver wipe using DDU and reinstall drivers from last year before wattman existed just to play games.

    Also I do love the pace of updates and I’ll update again once Vega comes out.

      • madmanmarz
      • 3 years ago

      I found the easiest fix for this problem for me was to run a bios with a modded voltage table. get your voltage out of the bios and then use wattman for overclocking. has worked perfectly for me but requires a little homework.

Pin It on Pinterest

Share This