Radeon Software Crimson Edition 16.3.2 is Rift-ready

AMD isn't leaving Radeon owners with Oculus Rifts high and dry today. The company has released Radeon Software Crimson Edition 16.3.2, a hotfix that adds support for Oculus SDK version 1.3 and the Radeon Pro Duo. The 16.3.2 release also adds support for a new feature called the Quick Response Queue. This scheduling feature lets developers submit time-sensitive work to the graphics card with more assurance it'll get done in the required time window.

Image: AMD

Before today, AMD says a high-priority task on a Radeon graphics card would have to request GPU resources using preemption. In that case, the GPU would temporarily suspend its other work, process the interruption, and return to its regular workload. AMD says preemption is a sub-optimal approach for time-sensitive tasks, since it doesn't provide any guarantee that a task will start and end within a given time frame. The company says that task-switching overhead and other delays associated with this method could also manifest as stuttering or lag in an application.

The Quick Response Queue, on the other hand, gives developers a special asynchronous queue where tasks can get preferential treatment from the GPU while the chip continues to perform other work. AMD says that since GCN asynchronous compute engines are both programmable and manage scheduling in hardware, it can enable the Quick Response Queue with nothing more than a software update on second-generation GCN GPUs and newer.

As an example of what this queue can do, AMD notes that Oculus implemented the asynchronous timewarp (or ATW) feature in version 1.3 of its SDK using the Quick Response Queue for AMD hardware. The company claims that using this feature makes it more likely that the ATW shader will be able to complete before the next vsync interval, even if it's submitted late in the rendering process. That's important since ATW is meant to reduce immersion-breaking judder in one's VR experience, and a warped frame is better than a dropped one. The company also touts the fact that running the ATW shader asynchronously means that the graphics card can continue to perform other tasks at the same time, like starting work on a new frame.

Radeon owners can download the appropriate version of this driver for their operating system and graphics card on this page.

Comments closed
    • DrCR
    • 4 years ago

    Present thoughts on [s<]ATI[/s<] AMD's Linux driver? It would be awesome to see AMD make a comeback.

      • synthtel2
      • 4 years ago

      I don’t have personal experience with AMD cards on Linux, but [url=http://www.x.org/wiki/RadeonFeature/<]this[/url<] makes it look like the open source drivers are doing pretty well on feature-completeness these days (excepting compute and some power management). Word of mouth is they're solid enough if you don't need 100% performance, FWIW. Catalyst still sounds pretty sketchy. Performance looks very weak (~50%) and inconsistent on both, probably a bit better on Catalyst. GPU-PRO is a new thing that might help, I guess, but I don't know much about it.

      • crystall
      • 4 years ago

      I don’t use AMD’s closed source drivers but the open source ones have been working flawlessly for me for a long time. It’s practically the only reason why I keep preferring AMD offerings to nVidia’s; since I spend most of my time using Linux and it’s the only way to get good performance and out-of-the-box support without the need for a proprietary drivers.

      (Intel offerings work too but I also want to do some serious gaming on Windows hence my use of a discrete GPU)

      • chuckula
      • 4 years ago

      From what I’ve seen the good news is that the Fury & Fury X are finally faster than the R9-290X in most benchmarks. It’s a positive sign for Polaris.

        • nanoflower
        • 4 years ago

        Also AMD has already been making commits to Linux for Polaris support so while it may require a beta build there will be Polaris support available on day 1 of the release of Polaris hardware for Linux.

    • kuttan
    • 4 years ago

    According to bitsandchips:
    [i<] "[RUMOR] Pascal in trouble with Asynchronous Compute code: According to our sources, next micro architecture Pascal GPU from NVIDIA will be in trouble if it will have to heavly use Asynchronous Compute code in video games. Broadly speaking, Pascal will be an improved version of Maxwell, especially about FP64 performance, but not about Asynchronous Compute performances. NVIDIA will bet on raw power, instead of Asynchronous Compute abilities. This means That Pascal cards will be highly dependent on driver optimizations and games developers kindness. So, GamesWorks optimizations will play a fundamental role in company strategy. That is it for this reason NVIDIA has made ​​publicly available some GamesWorks codes ?" [/i<] [url<]http://www.bitsandchips.it/52-english-news/6785-rumor-pascal-in-trouble-with-asyncronous-compute-code[/url<]

      • synthtel2
      • 4 years ago

      That’s probably the best news yet for Polaris’ competitive standing, if true.

    • DoomGuy64
    • 4 years ago

    Naw man, Async is just a gimmick, unlike our awesome gameworks program. – Nvidia

      • tipoo
      • 4 years ago

      1 year later
      “Introducing NSync, the proprietary GPU compute technology and boy band! Only $1000 added to your BoM”.

        • Firestarter
        • 4 years ago

        Backsync’s back, alright!

          • moriz
          • 4 years ago

          nsync and backstreet boys wombo combo comeback?!

            • Firestarter
            • 4 years ago

            oh my god we’re synced aga-aain!

    • tipoo
    • 4 years ago

    Is quick response queue entirely software based, as in any GCN card even of oldness can use it?

      • Beahmont
      • 4 years ago

      Umm… if you’d read the article, you’d know that QRQ is hardware based, but is available in any Second Gen GCN based hardware.

        • DancinJack
        • 4 years ago

        Reading is SO HARD though. Tipoo ain’t got time for that.

          • tipoo
          • 4 years ago

          You both got me, please collect your Tipoo point redeemable at any Tipoo location.

            • ColeLT1
            • 4 years ago

            I don’t want any Tip Poo.

    • Srsly_Bro
    • 4 years ago

    Sup?

      • Neutronbeam
      • 4 years ago

      Nuttin.

        • tipoo
        • 4 years ago

        Ew, we don’t need to know that.

      • LostCat
      • 4 years ago

      New drivers, apparently.

Pin It on Pinterest

Share This