Toggle search
Toggle menu
5.5K
6.1K
232
53.7K
VR & AR Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

VRWorks

vrarwiki.com · VR & AR Wiki
More actions
(Redirected from GameWorks VR)
VRWorks
Information
Type Software development kit
Industry Virtual reality
Developer NVIDIA
Operating System Windows
Supported Devices NVIDIA GeForce and Quadro GPUs (feature support depends on GPU architecture)
Release Date August 13, 2015 (GameWorks VR beta); November 19, 2015 (GameWorks VR 1.0)
Website https://developer.nvidia.com/vrworks


VRWorks, formerly known as GameWorks VR, is a suite of virtual reality technologies developed by Nvidia for high-performance VR rendering on its graphics processors. It contains a set of APIs, libraries and driver features for two groups of developers: engine and application developers, who integrate rendering features such as VR SLI and multi-resolution shading, and HMD makers, who use driver-level features such as Direct Mode and Context Priority.[1][2]

The technologies began as "VR Direct" in September 2014, were grouped under the GameWorks VR name at Computex in May 2015, and had been renamed VRWorks by March 2016, when NVIDIA's developer site also grouped under it the professional features previously released as DesignWorks VR.[3][4] Later releases added hardware features of new GPU generations: Lens Matched Shading and Single Pass Stereo with Pascal in 2016, Variable rate shading and Multi-View Rendering with Turing in 2018, and the driver-level Variable Rate Supersampling in 2020.[5][6][7] The VRWorks Audio SDK and a public beta of the VRWorks 360 Video SDK were released in May 2017.[8]

As of October 2026, NVIDIA's VRWorks page lists Variable Rate Shading, Variable Rate Supersampling, VR SLI, Vulkan XR Multi-GPU and Multi-View Rendering for application developers, and Direct Mode and Display Stream Compression for headset makers.[2] VRWorks Audio is not among the listed components, and NVIDIA states that VRWorks 360 Video is no longer available or supported.[9]

Reviewed 21 October 2026. Checked every dated history, feature, GPU/API requirement, performance claim, quote and current-status statement against the cited NVIDIA pages, whitepaper, slides, press coverage and the ISCA 2019 paper. About review dates.

History

VR Direct and GameWorks VR (2014-2015)

NVIDIA first presented its VR features as "VR Direct" alongside the GeForce GTX 980 in September 2014. On May 31, 2015, in conjunction with Computex, it moved them under its GameWorks developer program and renamed the collection GameWorks VR. The same announcement introduced multi-resolution shading, which uses the multi-projection hardware of second-generation Maxwell GPUs; NVIDIA claimed a 1.3x to 2x increase in pixel shader performance without a noticeable loss in image quality.[3]

The first beta of the GameWorks VR SDK for game and application developers, containing VR SLI and multi-res shading, was released on August 13, 2015, together with GeForce driver 355.60, which enabled VR SLI. A second SDK for hardware and headset developers, with Context Priority, Direct Mode and Front Buffer Rendering, was under a non-disclosure agreement at the time.[10] NVIDIA developer technology engineer Nathan Reed described the SDK's features at SIGGRAPH 2015 on August 17, 2015.[1][11]

On November 19, 2015, NVIDIA released version 1.0 of GameWorks VR and of DesignWorks VR, a companion SDK for professional VR in fields such as manufacturing, media and entertainment, oil and gas, and medical imaging. The 1.0 releases added Windows 10 support and worked with both GeForce and Quadro GPUs. DesignWorks VR added Warp and Blend, synchronization (Frame Lock, Stereo Lock, Swap Groups and Swap Barriers), GPU Affinity and Direct for Video. In the same announcement NVIDIA said Epic Games would support multi-res shading and VR SLI in a coming version of Unreal Engine 4, and claimed a 50 percent performance gain from multi-res shading in Epic's "Reflections Subway" demo shown at VRX 2015.[12]

VRWorks and Pascal (2016)

By early March 2016 NVIDIA's developer site had a VRWorks page, which described VRWorks as a suite of "APIs, sample code and libraries for VR developers" and divided it into features for game and application developers (multi-res shading and VR SLI, the latter supported for DirectX and OpenGL), for headset developers (Context Priority and Direct Mode), and for professional developers using Quadro GPUs (Warp and Blend, synchronization, GPU Affinity and GPU Direct for Video, aimed at CAVE systems, immersive displays and clusters).[4]

At the Game Developers Conference on March 16, 2016, NVIDIA named VRWorks partners: the engine makers Epic, MaxPlay and Unity, the headset makers HTC and Oculus, and applications including Sólfar Studios' Everest VR, Valve's The Lab, ILMxLAB's Star Wars Trials on Tatooine and InnerVision Games' Thunderbird: The Legend Begins. In the release NVIDIA stated that VR needs about seven times the GPU performance of a typical PC game and latency below 20 milliseconds. Valve senior graphics programmer Alex Vlachos said the company was "seeing solid performance improvements using NVIDIA VRWorks and VR SLI technology in The Lab".[13]

When NVIDIA announced the Pascal-based GeForce GTX 1080 on May 6, 2016, it described an "enhanced" VRWorks SDK with three parts: VRWorks Graphics with the new simultaneous multi-projection capability, which renders to the shape of VR displays and draws both eyes in one pass; VRWorks Audio, which uses the NVIDIA OptiX ray-tracing engine to trace sound through an environment; and PhysX for VR, which detects when a hand controller touches a virtual object. NVIDIA demonstrated these in its own application VR Funhouse, and CCP Games said it planned to bring the new features to EVE: Valkyrie.[14] NVIDIA's GTX 1080 whitepaper claimed that Single Pass Stereo and Lens Matched Shading together deliver "up to 2x" VR performance compared with a GPU without simultaneous multi-projection.[5]

Audio, 360 video and engine support (2016-2017)

NVIDIA made the Pascal rendering features available to Unreal Engine developers through a "VRWorks 4.12 Graphics branch" of Unreal Engine 4, which added Lens Matched Shading, Single Pass Stereo, VR SLI and multi-res shading and was accessible to anyone with access to the engine's source on GitHub.[15] For Unity, NVIDIA released a VRWorks plugin on the Unity Asset Store that required Unity 2017.1.0 Beta 2 or later.[16] Road to VR reported in July 2017 that Unity 2017.1 was the first main-branch Unity release to support VRWorks, with multi-res shading and VR SLI on Maxwell or Pascal GPUs and Lens Matched Shading and Single Pass Stereo on Pascal GPUs.[17]

On May 8, 2017, at its GPU Technology Conference in San Jose, NVIDIA released the VRWorks Audio SDK, as C APIs for any engine plus an Unreal Engine 4 integration on GitHub, and the first public beta of the VRWorks 360 Video SDK for real-time 4K 360-degree video capture, stitching and streaming. The beta handled monoscopic stitching; NVIDIA demonstrated a coming stereo version stitching eight 4K cameras of Z CAM's V1 PRO camera system on two Quadro P6000 GPUs.[8][18] Z CAM later released a beta of its WonderLive Pro software for live 360-degree stereo streaming from the V1 Pro, shown at NVIDIA's booth at SIGGRAPH 2017 in Los Angeles (July 30 to August 3); live stitching required a PC with two Quadro P6000 or GeForce GTX 1080 Ti GPUs. In Z CAM's announcement, NVIDIA's Jason Paul said the V1 Pro was the first to integrate VRWorks 360 Video.[19]

Turing features and VRSS (2018-2021)

With the Turing architecture, NVIDIA published VRWorks Graphics SDK 3.0 in September 2018, which required R410 or later drivers and added Variable Rate Shading and Multi-View Rendering.[6][20] Version 2.0 of the 360 Video SDK, announced at Adobe MAX in October 2018, added Turing and CUDA 10 support.[9][21] VRWorks Audio SDK 2.0 followed in March 2019 with support for Turing RT Cores and OptiX 6.0.[22]

GeForce Game Ready driver 441.87, announced at CES 2020 on January 6, 2020, added Variable Rate Supersampling (VRSS), which the driver applies without game integration.[7] VRSS 2, with eye-tracked foveation, arrived with the R465 driver branch on March 30, 2021.[23]

Status

On September 17, 2020, NVIDIA said it would stop adding new SLI driver profiles for RTX 20 series and earlier GPUs from January 1, 2021, while games with native DirectX 12 or Vulkan multi-GPU support would keep working.[24] VR SLI is integrated by the application rather than enabled through driver profiles,[10] and NVIDIA still lists it, now with Vulkan support, on its VRWorks page.[2] The page links a VRWorks 3.6.2 download for the Vulkan and DirectX versions of Variable Rate Shading and Multi-View Rendering, and OpenGL and Vulkan samples on GitHub.[2] Linked samples in NVIDIA's nvpro-samples organization on GitHub, including the Vulkan XR multi-GPU and OpenGL Variable Rate Shading samples, are published under the Apache 2.0 license.[25][26]

Timeline

Date Event
September 2014 VR features introduced as "VR Direct" with the GeForce GTX 980[3]
May 31, 2015 Renamed GameWorks VR at Computex; multi-res shading announced[3]
August 13, 2015 GameWorks VR beta SDK; driver 355.60 enables VR SLI[10]
November 19, 2015 GameWorks VR 1.0 and DesignWorks VR 1.0 released[12]
March 2016 VRWorks name in use; GDC partner announcement on March 16[4][13]
May 6, 2016 Pascal VR features (simultaneous multi-projection), VRWorks Audio and PhysX for VR announced with the GTX 1080[14]
May 8, 2017 VRWorks Audio SDK and VRWorks 360 Video SDK beta released at GTC[8]
July 2017 Unity 2017.1 supports VRWorks on its main branch[17]
September 24, 2018 VRWorks Graphics SDK 3.0 with Turing Variable Rate Shading and Multi-View Rendering[6][20]
October 2018 VRWorks 360 Video SDK 2.0[9]
March 22, 2019 VRWorks Audio SDK 2.0 with RT Core acceleration[22]
January 6, 2020 Variable Rate Supersampling in driver 441.87[7]
March 30, 2021 VRSS 2 with eye-tracked foveation in R465 drivers[23]

Features

Load video
YouTube
Feature First available GPU requirement (per NVIDIA) APIs listed by NVIDIA
VR SLI 2015 (GameWorks VR beta SDK) Maxwell or later (GeForce GTX 900 series, Quadro M5000 and higher) DirectX 11, OpenGL (multicast), Vulkan[27]
Multi-res shading 2015 (GameWorks VR beta SDK) Maxwell and Pascal (GeForce GTX 900 series, Quadro M5000 and higher) DirectX 11, DirectX 12, OpenGL[28]
Lens Matched Shading 2016 Pascal (GeForce GTX 1060 series, Quadro P4000 and higher) DirectX 11, OpenGL; DirectX 12 listed as "coming soon"[29]
Single Pass Stereo 2016 Pascal (GeForce GTX 1060 series, Quadro P4000 and higher) DirectX 11, OpenGL; DirectX 12 listed as "coming soon"[30]
Variable Rate Shading 2018 Turing Direct3D 11, OpenGL, Vulkan at launch; Direct3D 12 "coming soon"[6]
Multi-View Rendering 2018 Turing OpenGL sample; DirectX 11, DirectX 12 and Vulkan in the VRWorks package[20][2]
Variable Rate Supersampling 2020 (driver 441.87) GeForce RTX Driver feature for DirectX 11 VR games with forward rendering and MSAA[7][23]
VRWorks Audio 2017 (SDK; announced 2016) Maxwell and Pascal at release; Turing RT Cores used from SDK 2.0 C APIs; Unreal Engine 4 plugin[31][22]

VR SLI

VR SLI increases the performance of VR Apps by assigning one or more GPUs to each eye during stereo rendering (creating a different image for each eye). Because VR uses two independent views, developers can split the rendering across two different GPUs and then combine the images into a single frame for the HMD. This lets the app run at a higher frame rate or with higher graphical settings. Additionally, the VR SLI API, through GPU affinity, allows developers to scale the system to more than two GPUs.[1] NVIDIA's technical material for the SDK states that how the GPUs are used is up to the application, that VR SLI needs engine integration, that scaling depends on the app, and that work duplicated on each GPU, such as shadow maps, GPU particles and physics simulations, reduces the gain.[32] The application selects GPUs with an affinity mask, so that, for example, the left eye's draw calls go to one GPU and the right eye's to another, while work needed by both is sent to both.[32]

Current NVIDIA material lists VR SLI for DirectX 11, OpenGL (through the multicast extension) and Vulkan.[27] A related feature, Vulkan XR Multi-GPU, distributes independent XR views across several physical GPUs and transfers them to the main GPU for presentation to an XR runtime such as OpenXR.[2] NVIDIA's open-source sample for it supports a two-GPU mode, with each GPU rendering one eye, and a four-GPU mode, with each GPU rendering half of one eye, and can present to an OpenXR runtime or to a window.[25]

Multi-resolution shading

Multi-resolution shading renders different parts of the image at different resolutions to better match the pixel density of the warped image. When a flat image is viewed through the lenses of an HMD, it is distorted, so the GPU has to perform an additional pass that warps the image to cancel the lens distortion. The warp pass compresses the edges of the image, so pixels rendered there are wasted. Multi-res shading splits the image into a grid of viewports: the center viewport keeps full resolution, while the viewports at the edges are scaled down, so fewer pixels are shaded before the warp.[1][28] It relies on the multi-projection hardware of Maxwell GPUs, which sends the scene geometry to several viewports in a single pass.[3] NVIDIA's technical slides gave a "conservative" setting that saves 25 percent of pixels (a 1.3x pixel shading speedup) and an "aggressive" setting that saves 50 percent (2x).[32]

NVIDIA described Shadow Warrior 2 (2016) as the first non-VR game to use multi-res shading, there lowering resolution at the edges of a monitor image; it claimed performance gains of up to 30 percent.[33]

Context Priority

Context Priority gives HMD developers control over GPU scheduling to support important VR features such as asynchronous timewarp, which reduces latency by adjusting a rendered image to the latest head position without rendering a new frame.[1] NVIDIA's slides describe it as implemented through GPU preemption.[32]

Direct Mode

In Direct Mode, the display driver treats the HMD as a device separate from the operating system's desktop and accessible only to VR apps. This improves plug-and-play support and avoids problems that occur when the OS treats the HMD as just another monitor.[1] It also allows HMD developers to reduce latency: Reed's 2015 talk describes low-level access to video modes, vsync timing and control over the flip chain, so that VR software can manage the path from rendering to scan-out itself.[34] NVIDIA's current description says Direct Mode uses Context Priority for GPU scheduling along with late latching and asynchronous time warp; access is through NVIDIA's HMD developer program.[2]

Front Render Buffering

Front Render Buffering allows the GPU to render directly to the front buffer to reduce latency.[1] Reed described front-buffer rendering as a capability exposed through Direct Mode that takes advanced low-level knowledge to use, and said it can reduce latency further with techniques such as rendering during vblank or racing the beam.[34] It was part of the headset developer SDK in 2015 and was listed among the GameWorks VR 1.0 features.[10][12]

Lens Matched Shading

Lens Matched Shading uses the simultaneous multi-projection (SMP) engine of Pascal GPUs to approximate the lens-corrected image more closely than multi-res shading. The SMP engine divides the display region into four quadrants, each with its own projection plane, adjusted to the shape of the lens distortion. In NVIDIA's example based on Oculus Rift parameters, the final image is 1.1 megapixels per eye; conventional rendering produces a 2.1-megapixel first-pass image (86 percent more pixels than needed), while Lens Matched Shading produces 1.4 megapixels, which NVIDIA says gives a 50 percent increase in throughput available for pixel shading. The default "conservative" setting keeps the sampling rate at or above that of the final image everywhere.[5] NVIDIA's page lists engine integration in Unreal Engine and Unity and support in the Oculus SDK.[29]

Single Pass Stereo

Single Pass Stereo uses the two projection centers of Pascal's SMP engine to render both eye views in one pass. The application runs vertex processing once but outputs two positions per vertex, one for each eye, and the hardware routes each version to the correct eye, so scene submission, driver work and geometry processing are done only once.[5] NVIDIA says this lets developers roughly double the geometric complexity of VR applications, and its Unreal Engine page claims a 50 percent reduction in geometry bandwidth.[30][15]

Variable Rate Shading

Variable Rate Shading (VRS), a Turing GPU feature exposed in VRWorks Graphics SDK 3.0, changes the number of pixels covered by one pixel shader operation. Rasterization stays at native resolution while the shader runs once for a block of pixels (coarse shading, from 1x2 up to 4x4) or several times per pixel (2x, 4x or 8x supersampling). The shading rate surface has one entry per 16 by 16 pixel tile. NVIDIA proposed gaze-tracked foveated rendering, lens-optimized shading and content-adaptive shading as uses, and noted that, unlike multi-res shading and Lens Matched Shading, VRS needs no separate upscaling pass.[6]

Multi-View Rendering

Multi-View Rendering (MVR), introduced with Turing, extends Single Pass Stereo from two views that differ only horizontally to up to four views whose positions are independent. NVIDIA designed it for canted (non-coplanar) headset displays and for very wide fields of view; its blog said planar displays become hard to manage at or above 110 degrees and mentioned headsets with fields of view beyond 180 degrees.[20]

Variable Rate Supersampling

Variable Rate Supersampling (VRSS) uses Variable Rate Shading to supersample the center of the headset image, where the eye is usually focused, only when the GPU has spare capacity, so the headset's frame rate is maintained. It is applied by the driver to DirectX 11 VR games with forward renderers and MSAA that NVIDIA has tested, and is switched on in the NVIDIA Control Panel ("Adaptive"); an "Always On" option applies up to 8x supersampling regardless of performance.[7] UploadVR listed 24 tested games at launch, including Boneworks, Job Simulator, Lone Echo, Raw Data and Rec Room.[35]

VRSS 2 moves the supersampled region to wherever the user is looking, using a headset's eye tracking. It requires an RTX GPU and the same DirectX 11, forward rendering and MSAA conditions; the first supported headset was the HP Reverb G2 Omnicept Edition, and NVIDIA's list had 32 supported games in April 2021.[23] NVIDIA's current page says headset makers can integrate their eye-tracking runtime with VRSS, with access by request.[2]

Display Stream Compression

For high-resolution headsets, NVIDIA lists Display Stream Compression (DSC) among its VRWorks features for HMD manufacturers, with compression ratios of up to 3:1; it is available through the HMD developer program.[2]

Professional VR features

The professional features that began as DesignWorks VR were offered for Quadro GPUs. Warp and Blend provides application-independent geometry corrections and intensity adjustments across whole desktops for seamless CAVE environments; Frame Lock, Stereo Lock, Swap Groups and Swap Barriers prevent tearing and misalignment when one large desktop is driven by several GPUs or clusters; GPU Affinity pins OpenGL contexts to specific GPUs; and GPU Direct for Video provides low-latency video transfers to and from the GPU for overlaying video in VR.[4][12]

VRWorks Audio

VRWorks Audio simulates how sound travels through a virtual scene by ray tracing. Rays trace direct and indirect paths from a source to the listener and are absorbed, reflected and scattered by surfaces according to their angle and material properties, which gives the listener cues about the size and structure of the space as well as the direct-sound binaural effects of conventional 3D audio.[5] It uses NVIDIA's OptiX ray-tracing engine.[14] The 2017 SDK page listed real-time modeling of direct and indirect sound propagation, occlusion, directionality through a head-related transfer function, attenuation, approximate direct-path diffraction, and material reflection, absorption and transmission. The acoustic model is built and updated as the application loads the scene, without precomputed filters, and the generated filters are applied to the "dry" source audio.[31]

Setup used effect presets (low, medium and high), compute presets (a low single-GPU preset and a high preset for simple scenes or multi-GPU systems) and predefined materials such as wood, metal, concrete, plastic, cloth, carpet and glass. The SDK required 64-bit Windows and Maxwell or Pascal GPUs (GeForce GTX 900 series and higher, Quadro M5000 and higher), and was also offered as a plugin for Unreal Engine 4.15.[31] In its report on the release, Road to VR described a demonstration in which the sound changed as the listener moved around a corner from the source.[18]

VRWorks Audio SDK 2.0 added support for Turing GPUs and OptiX 6.0, offloading tree traversal and triangle intersection tests to RT Cores when present, and a "Professional Compute" preset for professional acoustic simulation; NVIDIA gave virtual architectural walkthroughs and virtual in-car experiences as examples of such uses. NVIDIA stated that the SDK 2.0 on a Turing GPU ran 10 times faster than SDK 1.0 on an equivalent Pascal GPU in a test scene of over 200,000 triangles.[22] VRWorks Audio is not among the components on NVIDIA's current VRWorks page.[2]

VRWorks 360 Video

The VRWorks 360 Video SDK provided GPU-accelerated capture, stitching and streaming of 360 video from multi-camera rigs.[8] Version 2.0 added a depth-based mono stitching mode for scenes with objects close to the rig, movable seams between camera pairs, stitching of a chosen region of interest instead of a full panorama (NVIDIA's example was a 180 by 90 degree viewport), first-order B-format ambisonic audio, and Turing support. NVIDIA claimed up to 90 percent faster stereo stitching and twice the real-time mono performance on RTX GPUs.[9] An article by NVIDIA's Stanley Tack in Computer Graphics World also described a Warp 360 component that converts between perspective, fisheye and equirectangular projections and from equirectangular to cubemap output.[21] NVIDIA now states that VRWorks 360 is no longer available or supported.[9]

Engine integration and use

VRWorks features are added by developers rather than switched on globally, apart from driver features such as Direct Mode and VRSS; Road to VR noted at the 2015 beta that performance gains would only appear once developers updated their software.[10][7] NVIDIA maintained an Unreal Engine 4 branch with the graphics features and an Unreal Engine plugin for VRWorks Audio, and a Unity plugin for the graphics features.[15][31][16] Ted Carefoot, a producer at Cloudhead Games, said in November 2016, when NVIDIA gave select developers early access to a Unity version with VRWorks support, that the studio was "very excited to be working with NVIDIA on VRWorks".[17]

Applications that adopted VRWorks features include Valve's The Lab (VR SLI)[13] and Sólfar Studios' Everest VR, which first added multi-res shading and later Lens Matched Shading; NVIDIA claimed a 15 percent gain for Lens Matched Shading over multi-res shading in that game.[36] CCP Games' EVE: Valkyrie used Lens Matched Shading in an "Ultra" graphics mode for GeForce users.[37]

Research

VRWorks has been used as a reference point in computer architecture research. In a paper presented at the 46th International Symposium on Computer Architecture (ISCA 2019), Chenhao Xie, Xin Fu, Mingsong Chen and Shuaiwen Leon Song proposed OO-VR, an object-oriented VR rendering framework for multi-GPU systems with non-uniform memory access. They validated the simultaneous multi-projection engine they added to the ATTILA GPU simulator by comparing it with VRWorks VR benchmark scenes such as Sponza run on a GeForce GTX 1080 Ti, and reported a 27 percent speedup for the simulated SMP rendering over rendering the two views one after the other.[38]

See also

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 "GameWorks VR". NVIDIA Developer (archived 5 September 2015). NVIDIA. http://web.archive.org/web/20150905173324/https://developer.nvidia.com/virtual-reality-development. Retrieved 2026-10-21.
  2. ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 "NVIDIA VRWorks". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/vrworks. Retrieved 2026-10-21.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 Ryan Smith (2015-05-31). "NVIDIA Announces GameWorks VR Branding, Adds Multi-Res Shading". AnandTech. http://web.archive.org/web/20150601233646/http://www.anandtech.com:80/show/9305/nvidia-announces-gameworks-vr-branding-adds-multires-shading. Retrieved 2026-10-21.
  4. ↑ 4.0 4.1 4.2 4.3 "NVIDIA VRWorks". NVIDIA Developer (archived 4 March 2016). NVIDIA. http://web.archive.org/web/20160304085823/https://developer.nvidia.com/vrworks. Retrieved 2026-10-21.
  5. ↑ 5.0 5.1 5.2 5.3 5.4 "NVIDIA GeForce GTX 1080 Whitepaper". NVIDIA. NVIDIA. 2016. https://international.download.nvidia.com/geforce-com/international/pdfs/GeForce_GTX_1080_Whitepaper_FINAL.pdf. Retrieved 2026-10-21.
  6. ↑ 6.0 6.1 6.2 6.3 6.4 Swaroop Bhonde (2018-09-24). "Turing Variable Rate Shading in VRWorks". NVIDIA Technical Blog. NVIDIA. https://developer.nvidia.com/blog/turing-variable-rate-shading-vrworks. Retrieved 2026-10-21.
  7. ↑ 7.0 7.1 7.2 7.3 7.4 7.5 "NVIDIA GeForce CES 2020 Game Ready Driver". NVIDIA GeForce News. NVIDIA. 2020-01-06. https://www.nvidia.com/en-us/geforce/news/nvidia-geforce-ces-2020-game-ready-driver/. Retrieved 2026-10-21.
  8. ↑ 8.0 8.1 8.2 8.3 "Nvidia Releases VRWorks Audio & 360 Video SDKs at GTC". Computer Graphics World. 2017-05-08. https://www.cgw.com/Press-Center/News/2017/Nvidia-Releases-VRWorks-Audio-360-Video-SDKs-at-.aspx. Retrieved 2026-10-21.
  9. ↑ 9.0 9.1 9.2 9.3 9.4 Vukasin Milovanovic, Rochelle Pereira (2018-10-16). "VRWorks 360 Video SDK 2.0 Adds Features, Turing Support". NVIDIA Technical Blog. NVIDIA. https://developer.nvidia.com/blog/vrworks-360-video-sdk-2-0-adds-features-turing-support. Retrieved 2026-10-21.
  10. ↑ 10.0 10.1 10.2 10.3 10.4 Paul James (2015-08-13). "NVIDIA 'Gameworks VR' Beta and New 'VR SLI' Enabled Drivers Now Available". Road to VR. https://roadtovr.com/nvidia-gameworks-vr-beta-and-new-vr-sli-enabled-drivers-now-available/. Retrieved 2026-10-21.
  11. ↑ Nathan Reed (2015-08-17). "SIGGRAPH 2015: NVIDIA GameWorks VR". Nathan Reed's coding blog. https://www.reedbeta.com/talks/gameworks-vr/. Retrieved 2026-10-21.
  12. ↑ 12.0 12.1 12.2 12.3 "NVIDIA VR Platforms Deliver Massive Performance Boost for Virtual Reality". NVIDIA Newsroom. NVIDIA. 2015-11-19. https://nvidianews.nvidia.com/news/nvidia-vr-platforms-deliver-massive-performance-boost-for-virtual-reality. Retrieved 2026-10-21.
  13. ↑ 13.0 13.1 13.2 "Virtual Reality Ecosystem Embraces NVIDIA VRWorks, Making It the Gold Standard for Developers". NVIDIA Newsroom. NVIDIA. 2016-03-16. https://nvidianews.nvidia.com/news/virtual-reality-ecosystem-embraces-nvidia-vrworks-making-it-the-gold-standard-for-developers. Retrieved 2026-10-21.
  14. ↑ 14.0 14.1 14.2 "A Quantum Leap in Gaming: NVIDIA Introduces GeForce GTX 1080". NVIDIA Newsroom. NVIDIA. 2016-05-06. https://nvidianews.nvidia.com/news/a-quantum-leap-in-gaming-nvidia-introduces-geforce-gtx-1080. Retrieved 2026-10-21.
  15. ↑ 15.0 15.1 15.2 "VRWorks Unreal Engine Branch adds support for VR SLI, Lens Matched Shading and Single Pass Stereo". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/vrworks-unreal-engine-branch-adds-support-vr-sli-lens-matched-shading-and-single-pass-stereo. Retrieved 2026-10-21.
  16. ↑ 16.0 16.1 "NVIDIA VRWorks Support for Unity Engine Now Available". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/nvidia-vrworks-support-unity-engine-now-available. Retrieved 2026-10-21.
  17. ↑ 17.0 17.1 17.2 Dominic Brennan (2017-07-13). "Unity's Main Branch Now Supports NVIDIA VRWorks for Enhanced Rendering Features". Road to VR. https://roadtovr.com/nvidia-vrworks-coming-unity/. Retrieved 2026-10-21.
  18. ↑ 18.0 18.1 Ben Lang (2017-05-08). "NVIDIA Shows How Physically-based Audio Can Greatly Enhance VR Immersion". Road to VR. https://roadtovr.com/nvidia-shows-how-physically-based-audio-can-greatly-enhance-vr-immersion-vrworks-audio-release/. Retrieved 2026-10-21.
  19. ↑ "Z CAM Unveils Live 360º Stereo Streaming Powered by NVIDIA". Z CAM. Z CAM. https://www.z-cam.com/z-cam-unveils-live-360o-stereo-streaming-powered-by-nvidia/. Retrieved 2026-10-21.
  20. ↑ 20.0 20.1 20.2 20.3 Swaroop Bhonde, Mahalakshmi Shanmugam (2018-09-24). "Turing Multi-View Rendering in VRWorks". NVIDIA Technical Blog. NVIDIA. https://developer.nvidia.com/blog/turing-multi-view-rendering-vrworks/. Retrieved 2026-10-21.
  21. ↑ 21.0 21.1 Stanley Tack (2018-10-18). "NVIDIA RTX-Powered VRWorks 360 Video SDK Offers New Features". Computer Graphics World. https://www.cgw.com/Press-Center/News/2018/NVIDIA-RTX-Powered-VRWorks-360-Video-SDK-Offers-.aspx. Retrieved 2026-10-21.
  22. ↑ 22.0 22.1 22.2 22.3 Nefi Alarcon (2019-03-22). "VRWorks Audio Dials up the Immersion with RTX Acceleration". NVIDIA Technical Blog. NVIDIA. https://developer.nvidia.com/blog/vrworks-audio-dials-up-the-immersion-with-rtx-acceleration/. Retrieved 2026-10-21.
  23. ↑ 23.0 23.1 23.2 23.3 Ben Lang (2021-04-12). "NVIDIA Adds Eye-tracking Support to VRSS Foveated Rendering Tech". Road to VR. https://roadtovr.com/nvidia-vrss-2-eye-tracking-foveated-rendering-supersampling/. Retrieved 2026-10-21.
  24. ↑ Brad Chacos (2020-09-18). "RIP: Nvidia slams the final nail in SLI's coffin, no new profiles after 2020". PCWorld. https://www.pcworld.com/article/393426/rip-nvidia-slams-the-final-nail-in-slis-coffin-no-new-profiles-after-2020.html. Retrieved 2026-10-21.
  25. ↑ 25.0 25.1 "nvpro-samples/xr_multi_gpu: Vulkan multi-GPU sample for XR workloads". GitHub. NVIDIA. https://github.com/nvpro-samples/xr_multi_gpu. Retrieved 2026-10-21.
  26. ↑ "nvpro-samples/gl_vrs: Variable Rate Shading in OpenGL". GitHub. NVIDIA. https://github.com/nvpro-samples/gl_vrs. Retrieved 2026-10-21.
  27. ↑ 27.0 27.1 "VRWorks - VR SLI". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/vrworks/graphics/vrsli. Retrieved 2026-10-21.
  28. ↑ 28.0 28.1 "VRWorks - Multi-Res Shading". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/vrworks/graphics/multiresshading. Retrieved 2026-10-21.
  29. ↑ 29.0 29.1 "VRWorks - Lens Matched Shading". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/vrworks/graphics/lensmatchedshading. Retrieved 2026-10-21.
  30. ↑ 30.0 30.1 "VRWorks - Single Pass Stereo". NVIDIA Developer. NVIDIA. https://developer.nvidia.com/vrworks/graphics/singlepassstereo. Retrieved 2026-10-21.
  31. ↑ 31.0 31.1 31.2 31.3 "VRWorks - Audio". NVIDIA Developer (archived 10 July 2017). NVIDIA. http://web.archive.org/web/20170710224742/https://developer.nvidia.com/vrworks/vrworks-audio. Retrieved 2026-10-21.
  32. ↑ 32.0 32.1 32.2 32.3 "NVIDIA VRWorks SDK (technical overview slides)". NVIDIA Developer. NVIDIA. https://d29g4g2dyqv443.cloudfront.net/sites/default/files/akamai/VRWorks/VRWORKS_Technical.pdf. Retrieved 2026-10-21.
  33. ↑ Andrew Burnes (2016-10-13). "Shadow Warrior 2 Gets Faster With NVIDIA Multi-Res Shading". NVIDIA GeForce News. NVIDIA. https://www.nvidia.com/en-us/geforce/news/shadow-warrior-2-nvidia-multi-res-shading. Retrieved 2026-10-21.
  34. ↑ 34.0 34.1 Nathan Reed (2015-08-17). "NVIDIA GameWorks VR (SIGGRAPH 2015 slides and notes)". Nathan Reed's coding blog. https://www.reedbeta.com/talks/gameworks-vr/GameWorks_VR_SIGGRAPH_2015.pdf. Retrieved 2026-10-21.
  35. ↑ David Heaney (2020-01-06). "CES 2020: NVIDIA Increases VR Sharpness For RTX Cards With Variable Rate Supersampling". UploadVR. https://www.uploadvr.com/nvidia-rtx-vrss-ces-2020/. Retrieved 2026-10-21.
  36. ↑ "Everest VR adds NVIDIA VRWorks Lens Matched Shading". NVIDIA GeForce News (Poland). NVIDIA. https://www.nvidia.com/pl-pl/geforce/news/gfecnt/everest-vr-adds-nvidia-vrworks-lens-matched-shading/. Retrieved 2026-10-21.
  37. ↑ "NVIDIA VRWorks Enables New Levels of Visual Quality in EVE: Valkyrie". HEXUS. https://hexus.net/tech/items/graphics/107908-nvidia-vrworks-enables-new-levels-visual-quality-eve-valkyrie/. Retrieved 2026-10-21.
  38. ↑ Chenhao Xie, Xin Fu, Mingsong Chen, Shuaiwen Leon Song (2019). "OO-VR: NUMA Friendly Object-Oriented VR Rendering Framework For Future NUMA-Based Multi-GPU Systems". Proceedings of the 46th International Symposium on Computer Architecture (ISCA '19), ACM. https://doi.org/10.1145/3307650.3322247. Retrieved 2026-10-21.
Retrieved from "https://vrarwiki.com/index.php?title=VRWorks&oldid=52932"