LiquidVR

LiquidVR
Information
Type	SDK
Industry	Virtual reality
Developer	AMD
Written In	C++
Operating System	Windows 7 or newer
License	MIT License
Supported Devices	AMD Radeon GPUs based on the Graphics Core Next (GCN) architecture
Release Date	March 3, 2015 (alpha); January 2016 (public GitHub release)
Website	https://gpuopen.com/liquidvr/

LiquidVR is a Virtual Reality SDK developed by AMD. It was announced on March 3, 2015 during the Game Developers Conference. Because GPU processing is at the heart of delivering AAA graphical quality in a VR environment, LiquidVR aims to utilize AMD's Radeon video cards to deliver better content, comfort, and compatibility to VR applications of all types.

The SDK gives applications a Direct3D 11 interface to GPU features that reduce motion-to-photon latency and spread VR rendering across several GPUs, including asynchronous compute, multi-GPU affinity, late latching of tracking data and GPU-to-GPU resource copies. AMD released an alpha of LiquidVR SDK 1.0 to registered developers on the day of the announcement, and in January 2016 it published the SDK on GitHub under the MIT License as part of its GPUOpen initiative. The runtime ships with AMD's graphics drivers, so an application needs only the LiquidVR.h header to use it.

Reviewed 27 September 2026. Checked the AMD 2015 and 2016 press releases, the GitHub README, changelog, releases, commits and license, the GPUOpen page, and the PC Perspective, Tom's Hardware, PC Gamer, bit-tech, Road to VR and UploadVR articles against every dated or quoted claim. About review dates.

Features

AMD built LiquidVR around what it called the "three Cs": comfort, compatibility and compelling content. PC Perspective, which spoke with AMD graphics CTO Raja Koduri at GDC 2015, explained comfort as ultra-low latency between head motion and the photons reaching the eyes, and compatibility as AMD's aim to treat all VR headsets equally in a plug-and-play way. The four features announced in March 2015 were:

• Latest Data Latch - For efficient GPU head tracking.

• Asynchronous Shaders - Minimizes latency, stuttering and judder.

• Affinity Multi-GPU - Lower latency and improve frame rates in VR with multiple GPUs.

• Direct-to-Display - Plug-and-play connection between an AMD Radeon graphics card and a VR headset.

The table below summarizes how AMD and contemporary press described each feature.

Feature	How it works	Source
Latest Data Latch (Late-Latch)	A programming mechanism that "helps get head tracking data from the head-mounted display to the GPU as quickly as possible by binding data as close to real-time as possible." The GitHub documentation describes it as reading constant data updated by the CPU after the original Direct3D 11 calls were issued. PC Perspective reported that tracking head movement until the end of the frame render rather than only at its start could save "potentially 5-10ms" of delay.
Asynchronous Shaders (Async Compute)	Uses the asynchronous compute engines (ACEs) of AMD's GCN GPUs to run image processing in parallel with rendering. AMD used it for "Hardware-Accelerated Time Warp", which warps a finished frame to the latest head position just before it is sent to the headset. In Direct3D 11 it provides a subset of the async compute functionality of Direct3D 12.
Affinity Multi-GPU (Multi-GPU Affinity)	Sends Direct3D 11 API calls to one or more GPUs selected by an affinity mask, so that, for example, each eye can be rendered on its own GPU instead of using alternate frame rendering (AFR), which adds latency.
Direct-to-Display (D2D)	Bypasses the operating system and sends the rendered image straight to the headset, including direct rendering to the front buffer. In the public SDK this interface is not accessible to applications; it is used directly by head-mounted display vendors.
GPU-to-GPU resource copies	Copies resources between GPUs with explicit control over synchronization.
Motion estimation	Added in version 1.1; calculates motion between two surface frames on specific GPUs and "can be used for ASW" (Asynchronous Spacewarp).
Vulkan interoperability	Added in version 1.1; converts buffers, surfaces and semaphores for use with Vulkan.
TrueAudio Next	Listed by AMD's GPUOpen page as a LiquidVR benefit: GPU-compute based, real-time physics-based audio acoustics rendering.

Latency and time warp

The main goal of the feature set is lower latency. The AMD press release for the launch defined motion-to-photon latency as "the time between when a user moves their head and when his or her eye sees an updated image reflecting that new position." In its GDC 2015 report, Tom's Hardware quoted Layla Mah, AMD's head design engineer, as saying that typical motion-to-photon latency was about 11 milliseconds at 90 Hz, so saving one or two milliseconds mattered. Mah explained that a synchronous time warp has to finish before VSync or the user sees judder, while LiquidVR lets the warp run asynchronously and, with front buffer rendering, start during scan-up after VSync, which gives a frame a millisecond or more of extra time.

Writing for PC Gamer in 2016, Jarred Walton described the async shaders as the SDK's main differentiator. He wrote that Asynchronous Timewarp is a compute shader that can be scheduled alongside other graphics work on GCN hardware without preempting it, whereas GPUs without a comparable feature must perform a context switch. The same article reported AMD's claim that Affinity Multi-GPU "can cut latency nearly in half while doubling bandwidth and computational resources," and noted that it was unclear how well the approach scaled beyond two graphics cards.

LiquidVR Development Kit

LiquidVR Development Kit or LDK is a pre-packaged PC platform for VR developers that AMD discussed with Road to VR around E3 2015. In a July 2015 report, Road to VR said that AMD's vice president of alliances, Roy Taylor, told it the company planned to offer systems "built to known, controlled specifications to keep configuration variation to a minimum." According to Daryl Sartain of AMD's virtual reality division, the LDK hardware would use AMD GPUs, while the PCs themselves would come from OEMs that built systems to order with a matching operating system image.

Buyers were to receive their choice of VR headsets with the kit, together with the latest version of Crytek's CryEngine, which the report said had been updated with support for the Oculus Rift, Sony's Project Morpheus and the HTC Vive. The kit was scheduled to ship in fall 2015; AMD did not announce pricing at the time.

History

AMD unveiled LiquidVR at the Game Developers Conference in San Francisco on March 3, 2015, and released the alpha version of LiquidVR SDK 1.0 to registered developers the same day. PC Perspective reported that AMD called this an "early alpha" stage, with engine and game developers getting access during GDC, and that Koduri wanted LiquidVR in full production by the time consumer VR headsets reached the market. Oculus was a launch partner. In the press release, Oculus CEO Brendan Iribe said the company was "excited to have AMD working with us on their part of the latency equation, introducing support for new features like asynchronous timewarp and late latching." Tom's Hardware named Oculus and Crytek among AMD's partners for the announcement. It also reported that AMD said LiquidVR drew on engineering from its Mantle API and would be enabled through all relevant APIs, starting with DirectX 11, and that Koduri considered support for the OSVR initiative premature. PC Perspective compared the SDK with NVIDIA's VR Direct, which NVIDIA had presented with asynchronous warping and VR SLI; the site's initial impression was that LiquidVR was at an earlier stage than VR Direct.

In December 2015 AMD announced GPUOpen, an initiative to release its graphics tools, libraries and SDKs as open source under the MIT License, with LiquidVR among the technologies included. The LiquidVR repository appeared on GitHub in January 2016 with version 1.0.3.20, dated January 18, 2016 in the changelog and published as a release on January 19, 2016.

On March 14, 2016, during GDC 2016, AMD announced the dual-GPU Radeon Pro Duo, featuring LiquidVR, as a platform for VR content creation and consumption, with 16 teraflops of compute performance and an expected price of US$1,499. On the same day AMD said it had been named exclusive GPU technology provider for Crytek's VR First initiative, which provides VR labs for colleges and universities, and that it would equip the labs with Radeon Pro Duo cards featuring the LiquidVR SDK; the first VR First lab, at Bahcesehir University in Istanbul, had opened in January 2016. A further AMD release that day stated that LiquidVR was "being used across the VR software stack by headset manufacturers, including Oculus, HTC, game engine developers and content creators." The Sulon Q all-in-one headset, shown with AMD at GDC 2016, was also described as working with LiquidVR.

Later builds added an HDCP status API for Direct-to-Display (April 2016), Vulkan interoperability and a motion estimator (August 2016), and motion estimator support for Fiji GPUs in build 1.0.10.0 (November 29, 2016). In December 2016, Road to VR reported that the LiquidVR suite bundled with the Radeon Software Crimson ReLive Edition driver added MultiView, which it called AMD's equivalent of NVIDIA's Simultaneous Multi-projection, and MultiRes, AMD's equivalent of NVIDIA's multi-res shading; the same driver brought Oculus' Asynchronous Spacewarp to Radeon RX 400 series GPUs. The GitHub README documents a version 1.1, tied to drivers 17.4.1 and 17.10.1061, that added motion estimation and Vulkan interoperability.

Requirements and current status

The GitHub README lists an AMD Radeon GCN-based GPU (recommending the R9 290 series or higher for VR), Windows 7, 8.1 or 10, and Radeon Software Crimson Edition drivers or later; building the samples requires Visual Studio 2013. It notes that all GCN-based Radeon GPUs support the feature set, and that LiquidVR features work even when no VR device is installed. AMD's GPUOpen page lists an AMD Radeon GCN-based GPU with an R9 390 or better recommended, and Windows 7 or newer.

The public repository's last code update, to SDK build 1.0.10.0, was committed on March 29, 2017, and a README revision followed on April 6, 2017. As of September 2026, the GPUOpen page still offers version 1.0.3.20 for download, along with the documentation and GitHub source.

See also

• VRWorks
• GameWorks VR
• Asynchronous Timewarp
• Asynchronous Reprojection
• Motion-to-photon latency