Difference between revisions of "Direct mode"

From Virtual Reality, Augmented Reality Wiki
Jump to: navigation, search
(Created page with "In Direct Mode, the display driver treats the HMD as an entity separate from the operating system and accessible only to VR apps. It improves plug-and-play capabilities an...")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
In [[Direct Mode]], the display driver treats the HMD as an entity separate from the operating system and accessible only to VR apps. It improves plug-and-play capabilities and prevents numerous [[UX]] issues that occur when the OS treats the HMD as just another monitor. It also allows HMD developers to reduce latency by giving them the control over frame queuing and vsync behavior.<ref name="GameWorks_VR_Site">https://developer.nvidia.com/virtual-reality-development</ref>
+
In [[Direct Mode]], the display driver treats the [[HMD]] as an entity separate from the operating system and accessible only to [[VR apps]]. It improves plug-and-play capabilities and prevents numerous [[UX]] issues that occur when the OS treats the HMD as just another monitor. It also allows HMD developers to reduce latency by giving them the control over frame queuing and vsync behavior.<ref name="GameWorks_VR_Site">https://developer.nvidia.com/virtual-reality-development</ref>
 +
 
 +
Direct mode is supported by [[GameWorks VR]] by [[Nvidia]].
 +
==References==
 +
<references />
 +
 
 +
[[Category:Terms]]

Latest revision as of 06:37, 1 July 2015

In Direct Mode, the display driver treats the HMD as an entity separate from the operating system and accessible only to VR apps. It improves plug-and-play capabilities and prevents numerous UX issues that occur when the OS treats the HMD as just another monitor. It also allows HMD developers to reduce latency by giving them the control over frame queuing and vsync behavior.[1]

Direct mode is supported by GameWorks VR by Nvidia.

References

  1. https://developer.nvidia.com/virtual-reality-development