VR & AR Wiki - User contributions [en]

https://vrarwiki.com/api.php?action=feedcontributions&feedformat=atom&user=Copsaur7 VR & AR Wiki - User contributions [en] 2026-04-21T02:04:38Z User contributions MediaWiki 1.43.0 https://vrarwiki.com/index.php?title=Daydream&diff=10215 Daydream 2016-05-19T22:14:05Z

<p>Copsaur7: /* Developer */</p> <hr /> <div>{{stub}}<br /> [[Daydream]] is [[Google]]'s mobile [[Virtual Reality Platform]]. Built on top of [[Android N]], Daydream encompasses both software along with hardware such as Daydream-ready smartphones, [[#Devices|HMDs]] and [[#Accessories|controllers]]. Daydream was the successor to [[Google Cardboard]] and was unveiled in Google I/O 2016.<br /> <br /> ==Devices==<br /> The [[Daydream HMD]] consists of a [[Slide-on HMD]] that requires a Daydream-ready phone. Daydream-ready phones are new Android N smartphones with special components such as special sensors and displays. These phones act the the processors and displays for the HMD. Daydream HMD differs from [[Cardboard]] as it only works with specific phones, not all phones. <br /> <br /> ==Accessories==<br /> [[Daydream Controller]] - a small remote with a touchpad, 2 buttons and [[rotational tracking]].<br /> <br /> ==Daydream-ready Phones==<br /> Smartphones act as the displays and processors for the Daydream HMDs. Unlike Google Cardboard, only Daydream-ready Android phones , not all phones can used for Daydream HMD. These phones have special sensors and screens needed for a quality VR experience. Google has partnered with [[Samsung]], [[LG]], [[HTC]], [[Huawei]], [[Xiaomi]], [[ZTE]], [[Asus]], and [[Alcatel]] to bring these phones to market.<br /> <br /> ==Platform==<br /> [[Daydream Home]]<br /> <br /> ==Apps==<br /> <br /> ==Developer==<br /> [[Daydream Development Kit Guide]]<ref>https://developers.google.com/vr/concepts/dev-kit-setup#prerequisites</ref><br /> <br /> ==Technology==<br /> <br /> ==History==<br /> <br /> ==References==<br /> <br /> [[Category:Virtual Reality Platforms]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10214 Developer Resource 2016-05-19T05:11:36Z

<p>Copsaur7: </p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR apps]]. An [[app]] can either implement [[OVR]] or [[OpenVR]] or both. This means that the app has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> If you launch a game on Steam that supports [[Rift]] natively (meaning, it has been compiled against the [[Oculus SDK]]), you will get [[asynchronous timewarp]] and it will run exactly like the game from Oculus Home. It won't use the the [[SteamVR Runtime]], it will use the [[Oculus Runtime]]. Only downside is that launching the game is more difficult. <br /> <br /> If you buy a game that is compiled against the [[OpenVR SDK]], then it can run on [[Vive]] and Rift. However, running on Rift uses both runtimes:<br /> <br /> Rendered Image using the OpenVR SDK -> SteamVR Runtime -> Oculus Runtime -> Rift<br /> <br /> The Oculus Runtime effectively thinks you are playing a game called "SteamVR", but the content of the "game" is actually the image that the SteamVR runtime got from the OpenVR compiled game. This seems to work rather well and personally I have not noticed any additional latency. In theory you would even get Asynchronous Timewarp, but that would only happen if SteamVR itself isn't responding in time. If an OpenVR game stalls completely, the SteamVR runtime will throw you back into the loading construct and continues to render at 90fps. Since the SteamVR runtime has this fail safe mechanism and all the Oculus Runtime sees is "SteamVR", it will most likely never trigger Asynchronous Timewarp.<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> ===Example===<br /> [[Project Cars]] on Steam supports both [[OpenVR]] and [[OVR]]. The Oculus Home version supports only OVR as of today.<br /> <br /> #Project Cars on Home + Rift -> will run natively<br /> #Project Cars on Steam + Vive -> will run natively<br /> #Project Cars on Steam + Rift + launched as Rift app -> will run natively<br /> #Project Cars on Home + Vive -> won't run<br /> #Project Cars on Steam + Rift + launched as SteamVR app -> will run via SteamVR<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[apps]], or better said apps compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Timewarp&diff=10213 Timewarp 2016-05-19T05:10:32Z

<p>Copsaur7: </p> <hr /> <div>__TOC__<br /> ==General Information==<br /> '''Timewarp''' / '''Time warping''' also known as '''Reprojection''' is a technique in [[VR]] that warps the rendered image before sending it to the display to correct for the head movement occurred after the rendering.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> Timewarp can reduce [[latency]] and increase or maintain [[frame rate]]. Additionally, it can reduce [[judder]] caused missed frames (when frames take too long to render).<ref name="YT1">https://www.youtube.com/watch?v=WvtEXMlQQtI</ref> This process takes the already rendered image, modify it with freshly collected positional information from your [[HMD]]'s sensors, then display it to your screen. Utilizing [[depth maps]] ([[Z Buffers]]) already present in the engine, Timewarp requires very little computation.<br /> <br /> Timewarp is a feature of [[Oculus SDK]]. It was initially released in the version 0.3.1 of the SDK. [[#Positional Timewarp|Positional Timewarp]] was introduced in [[Oculus PC SDK]] 0.6.0<ref>https://twitter.com/volgaksoy/status/599251845156995072</ref>.<br /> <br /> [[Runtime]]s for various platforms such as the [[Oculus Runtime]] and [[SteamVR Runtime]] are responsible for Timewarp. Different runtimes [[#Oculus Rift vs. SteamVR vs. PSVR|perform timewarp differently]].<br /> <br /> ==Asynchronous Timewarp (ATW)==<br /> '''Asynchronous Timewarp''' or '''ATW''' is when timewarp occurs on another thread in parallel (asynchronously) with rendering. Before every [[vsync]], the ATW thread generates a new timewarped frame from the latest frame completed by the rendering thread.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> ATW fills in the missed frames and reduces [[judder]].<ref>https://developer.oculus.com/blog/asynchronous-timewarp-on-oculus-rift/</ref><br /> <br /> ==How Timewarp Reduces Latency==<br /> Without Timewarp, your HMD would capture the data about the position of your head, render the image based on this data (correct angel etc.), then display the image when the next scene is due to be on screen. In a 60 fps game, a new scene is displayed once every 16.7 milliseconds. With this process, each image you see is based on the head-tracking data from almost 17 milliseconds ago. <br /> <br /> With Timewarp, the first 2 parts of the process is the same. your HMD would capture the data about the position of your head and render the image based on the data. Before this image is displayed, your HMD captures the position of your head again. Using this information, the rendered image is modified with a mathematical calculation to fit the latest data. Finally the modified image is displayed on screen. The resulting image is more recent and more accurately depict the position of your head at the time of display than the image initially rendered. Timewarp only works in very short distances and time intervals or the resulting image will look unrealistic or out of place.<br /> <br /> ==How Timewarp Increases Frame Rate==<br /> Timewarp allows engines to increase or maintain frame rate when they are otherwise unable to do. It does this by artificially filling in dropped frames.<br /> <br /> In a game engine limited to 50 frames per second, a new frame is displayed once every 20 milliseconds. To increase the game's frame rate to 60, you need to display a new frame once every 16.7 milliseconds. To increase the fps through timewarp, the last completely rendered frame, not the one that is currently rendering, is updated with the latest data about the position of your head. The modified frame is displayed before your eyes.<ref name="YT1">https://www.youtube.com/watch?v=WvtEXMlQQtI</ref> Theoretically, this method could increase frame rate from 1 to 60. Realistically, timewarp only works in very short distances and time intervals. Long distances or time intervals will make the image appear unrealistic or out of place.<br /> <br /> ==Limitations of Timewarp==<br /> Timewarp works well in a rotational only tracking system. When positional / translational tracking is introduced, it does not work as well and presents a few problems.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> When timewarp is used with positional tracking, only the rotational change is reflected in the resulting image. The positional change is ignore, causing [[judder]]. This is solved through the introduction of [[#Positional Timewarp|Positional Timewarp]].<br /> <br /> Moving objects such as an animated character can also cause judder. The notice-bility of the judder depends on the size, number and speed of the moving object.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> Large and fast moving objects can cause very noticeable judder.<br /> <br /> ==Positional Timewarp==<br /> {{see also|Positional Timewarp}}<br /> Positional Timewarp solves positional judder caused by translational movements. <br /> <br /> It is accomplished by ???<br /> <br /> ==Oculus Rift vs. SteamVR vs. PSVR==<br /> The [[Oculus Runtime]] uses asynchronous timewarp to interpolate frames from any frame rate to 90. I.e. the game has a massive explosion, fps drop to 70, async timewarp interpolates to 90.<br /> <br /> The [[SteamVR Runtime]] uses reprojection when the target frame rate is not met. But instead of interpolating from an arbitrary frame rate to 90, it forces the game to render at 45fps and then doubles the frame rate via interpolation.<br /> <br /> Both approaches have advantages and disadvantages. Asynchronous timewarp is great for very short dips below 90, but it's variability means frame times aren't that smooth. SteamVR's reprojection has very smooth and predictable frame times, however the fps hit is much higher, which could look weird if animations and physics are meant to run with 90Hz.<br /> <br /> Sony's [[PSVR]] is using SteamVR style reprojection as one of their default modes. Games can render at 60fps and will be reprojected to 120.<br /> <br /> ==References==<br /> <references /><br /> <br /> <br /> <br /> [[Category:Terms]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Timewarp&diff=10212 Timewarp 2016-05-19T04:57:46Z

<p>Copsaur7: </p> <hr /> <div>__TOC__<br /> ==General Information==<br /> '''Timewarp''' / '''Time warping''' also known as '''Reprojection''' is a technique in [[VR]] that warps the rendered image before sending it to the display to correct for the head movement occurred after the rendering.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> Timewarp can reduce [[latency]] and increase or maintain [[frame rate]]. Additionally, it can reduce [[judder]] caused missed frames (when frames take too long to render).<ref name="YT1">https://www.youtube.com/watch?v=WvtEXMlQQtI</ref> This process takes the already rendered image, modify it with freshly collected positional information from your [[HMD]]'s sensors, then display it to your screen. Utilizing [[depth maps]] ([[Z Buffers]]) already present in the engine, Timewarp requires very little computation.<br /> <br /> Timewarp is a feature of [[Oculus SDK]]. It was initially released in the version 0.3.1 of the SDK. [[#Positional Timewarp|Positional Timewarp]] was introduced in [[Oculus PC SDK]] 0.6.0<ref>https://twitter.com/volgaksoy/status/599251845156995072</ref>.<br /> <br /> ==Asynchronous Timewarp (ATW)==<br /> '''Asynchronous Timewarp''' or '''ATW''' is when timewarp occurs on another thread in parallel (asynchronously) with rendering. Before every [[vsync]], the ATW thread generates a new timewarped frame from the latest frame completed by the rendering thread.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> ATW fills in the missed frames and reduces [[judder]].<ref>https://developer.oculus.com/blog/asynchronous-timewarp-on-oculus-rift/</ref><br /> <br /> ==How Timewarp Reduces Latency==<br /> Without Timewarp, your HMD would capture the data about the position of your head, render the image based on this data (correct angel etc.), then display the image when the next scene is due to be on screen. In a 60 fps game, a new scene is displayed once every 16.7 milliseconds. With this process, each image you see is based on the head-tracking data from almost 17 milliseconds ago. <br /> <br /> With Timewarp, the first 2 parts of the process is the same. your HMD would capture the data about the position of your head and render the image based on the data. Before this image is displayed, your HMD captures the position of your head again. Using this information, the rendered image is modified with a mathematical calculation to fit the latest data. Finally the modified image is displayed on screen. The resulting image is more recent and more accurately depict the position of your head at the time of display than the image initially rendered. Timewarp only works in very short distances and time intervals or the resulting image will look unrealistic or out of place.<br /> <br /> ==How Timewarp Increases Frame Rate==<br /> Timewarp allows engines to increase or maintain frame rate when they are otherwise unable to do. It does this by artificially filling in dropped frames.<br /> <br /> In a game engine limited to 50 frames per second, a new frame is displayed once every 20 milliseconds. To increase the game's frame rate to 60, you need to display a new frame once every 16.7 milliseconds. To increase the fps through timewarp, the last completely rendered frame, not the one that is currently rendering, is updated with the latest data about the position of your head. The modified frame is displayed before your eyes.<ref name="YT1">https://www.youtube.com/watch?v=WvtEXMlQQtI</ref> Theoretically, this method could increase frame rate from 1 to 60. Realistically, timewarp only works in very short distances and time intervals. Long distances or time intervals will make the image appear unrealistic or out of place.<br /> <br /> ==Limitations of Timewarp==<br /> Timewarp works well in a rotational only tracking system. When positional / translational tracking is introduced, it does not work as well and presents a few problems.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> When timewarp is used with positional tracking, only the rotational change is reflected in the resulting image. The positional change is ignore, causing [[judder]]. This is solved through the introduction of [[#Positional Timewarp|Positional Timewarp]].<br /> <br /> Moving objects such as an animated character can also cause judder. The notice-bility of the judder depends on the size, number and speed of the moving object.<ref name=ATW blog1">https://www.oculus.com/blog/asynchronous-timewarp/</ref> Large and fast moving objects can cause very noticeable judder.<br /> <br /> ==Positional Timewarp==<br /> {{see also|Positional Timewarp}}<br /> Positional Timewarp solves positional judder caused by translational movements. <br /> <br /> It is accomplished by ???<br /> <br /> ==Oculus Rift vs. SteamVR vs. PSVR==<br /> <br /> ==References==<br /> <references /><br /> <br /> <br /> <br /> [[Category:Terms]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10211 Developer Resource 2016-05-19T03:40:25Z

<p>Copsaur7: /* App Stores */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR apps]]. An [[app]] can either implement [[OVR]] or [[OpenVR]] or both. This means that the app has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> If you launch a game on Steam that supports [[Rift]] natively (meaning, it has been compiled against the [[OVR SDK]]), you will get [[asynchronous timewarp]] and it will run exactly like the game from Oculus Home. It won't use the the [[SteamVR Runtime]], it will use the [[Oculus Runtime]]. Only downside is that launching the game is more difficult. <br /> <br /> If you buy a game that is compiled against the [[OpenVR SDK]], then it can run on [[Vive]] and Rift. However, running on Rift uses both runtimes:<br /> <br /> Rendered Image using the OpenVR SDK -> SteamVR Runtime -> Oculus Runtime -> Rift<br /> <br /> The Oculus Runtime effectively thinks you are playing a game called "SteamVR", but the content of the "game" is actually the image that the SteamVR runtime got from the OpenVR compiled game. This seems to work rather well and personally I have not noticed any additional latency. In theory you would even get Asynchronous Timewarp, but that would only happen if SteamVR itself isn't responding in time. If an OpenVR game stalls completely, the SteamVR runtime will throw you back into the loading construct and continues to render at 90fps. Since the SteamVR runtime has this fail safe mechanism and all the Oculus Runtime sees is "SteamVR", it will most likely never trigger Asynchronous Timewarp.<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> ===Example===<br /> [[Project Cars]] on Steam supports both [[OpenVR]] and [[OVR]]. The Oculus Home version supports only OVR as of today.<br /> <br /> #Project Cars on Home + Rift -> will run natively<br /> #Project Cars on Steam + Vive -> will run natively<br /> #Project Cars on Steam + Rift + launched as Rift app -> will run natively<br /> #Project Cars on Home + Vive -> won't run<br /> #Project Cars on Steam + Rift + launched as SteamVR app -> will run via SteamVR<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[apps]], or better said apps compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Steam&diff=10210 Steam 2016-05-19T03:25:56Z

<p>Copsaur7: </p> <hr /> <div>{{App Store Infobox<br /> |image=<br /> |Platforms=[[SteamVR]]<br /> |Devices=[[HTC Vive]], [[Oculus Rift (Platform)]]<br /> |Operating Systems=[[Android]], [[Windows]]<br /> |Accessible=[[Mobile]], [[PC]], [[VR]]<br /> |Developer=[[Valve]]<br /> |Notable Personnel=[[Gabe Newell]]<br /> |Apps=<br /> |Downloads=<br /> |Website=http://store.steampowered.com/<br /> }}<br /> {{stub}}<br /> {{see also|SteamVR}}<br /> [[Steam]] is the official [[Virtual Reality]] [[App Store]] for the [[SteamVR]] and [[HTC Vive]]. Created by [[Valve]] and released in 2003, Steam curates and distributes [[games]], [[apps]] and [[software]] not only for [[VR Devices]] but also for [[PC]], [[Mac]], [[Linux]] and [[SteamOS]]. It is the largest and most popular digital distribution platform for PC games. The app store is accessible on [[VR Devices]] such as [[HTC Vive]] and [[Oculus Rift]] and non-VR devices such as PC and Mobile.<br /> <br /> In 2013, Steam added a category called [[#VR Support|VR Support]]. Since then Valve has slowly added for subcategories and other features.<br /> <br /> *Note that unlike the [[Oculus Store]], Steam carries titles not only for the [[Vive]] but also for other [[VR HMDs]] such as the [[Rift]].<br /> ==VR Support==<br /> Players can sort and filter VR-enabled games through the following subcategories<br /> ===Headsets===<br /> *[[HTC Vive]]<br /> <br /> *[[Oculus Rift (Platform)]]<br /> ===Input===<br /> *[[Input Devices|Tracked motion controllers]]<br /> <br /> *[[Gamepad]]<br /> <br /> *[[Keyboard / Mouse]]<br /> <br /> ===Play Area===<br /> *[[Seated]]<br /> <br /> *[[Standing]]<br /> <br /> *[[Room-scale]]<br /> <br /> ==How to Run Oculus Rift App Natively on Steam==<br /> If you are in SteamVR mode, it will do it automatically (depending on what device you are using). Otherwise you usually right click the item in the desktop client and select the option: ''Launch Oculus Rift in VR Mode''. It might also give you a popup if you try to launch it straight away.<br /> <br /> *Only apps compiled against the [[OVR SDK]] can run on Rift natively. Native Rift apps use [[Oculus Runtime]] directly and allow [[asynchronous timewarp]].<br /> <br /> <br /> <br /> [[Category:App Stores]] [[Category:SteamVR]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Steam&diff=10209 Steam 2016-05-19T03:23:54Z

<p>Copsaur7: </p> <hr /> <div>{{App Store Infobox<br /> |image=<br /> |Platforms=[[SteamVR]]<br /> |Devices=[[HTC Vive]], [[Oculus Rift (Platform)]]<br /> |Operating Systems=[[Android]], [[Windows]]<br /> |Accessible=[[Mobile]], [[PC]], [[VR]]<br /> |Developer=[[Valve]]<br /> |Notable Personnel=[[Gabe Newell]]<br /> |Apps=<br /> |Downloads=<br /> |Website=http://store.steampowered.com/<br /> }}<br /> {{stub}}<br /> {{see also|SteamVR}}<br /> [[Steam]] is the official [[Virtual Reality]] [[App Store]] for the [[SteamVR]] and [[HTC Vive]]. Created by [[Valve]] and released in 2003, Steam curates and distributes [[games]], [[apps]] and [[software]] not only for [[VR Devices]] but also for [[PC]], [[Mac]], [[Linux]] and [[SteamOS]]. It is the largest and most popular digital distribution platform for PC games. The app store is accessible on [[VR Devices]] such as [[HTC Vive]] and [[Oculus Rift]] and non-VR devices such as PC and Mobile.<br /> <br /> In 2013, Steam added a category called [[#VR Support|VR Support]]. Since then Valve has slowly added for subcategories and other features.<br /> <br /> *Note that unlike the [[Oculus Store]], Steam carries titles not only for the [[Vive]] but also for other [[VR HMDs]] such as the [[Rift]].<br /> ==VR Support==<br /> Players can sort and filter VR-enabled games through the following subcategories<br /> ===Headsets===<br /> *[[HTC Vive]]<br /> <br /> *[[Oculus Rift (Platform)]]<br /> ===Input===<br /> *[[Input Devices|Tracked motion controllers]]<br /> <br /> *[[Gamepad]]<br /> <br /> *[[Keyboard / Mouse]]<br /> <br /> ===Play Area===<br /> *[[Seated]]<br /> <br /> *[[Standing]]<br /> <br /> *[[Room-scale]]<br /> <br /> ==How to Run Oculus Rift App Natively on Steam==<br /> If you are in SteamVR mode, it will do it automatically (depending on what device you are using). Otherwise you usually right click the item in the desktop client and select the option: '''Launch Oculus Rift in VR Mode'''. It might also give you a popup if you try to launch it straight away.<br /> <br /> [[Category:App Stores]] [[Category:SteamVR]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10208 Developer Resource 2016-05-19T03:19:02Z

<p>Copsaur7: </p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR apps]]. An [[app]] can either implement [[OVR]] or [[OpenVR]] or both. This means that the app has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> If you launch a game on Steam that supports [[Rift]] natively (meaning, it has been compiled against the [[OVR SDK]]), you will get [[asynchronous timewarp]] and it will run exactly like the game from Oculus Home. It won't use the the [[SteamVR Runtime]], it will use the [[Oculus Runtime]]. Only downside is that launching the game is more difficult. <br /> <br /> If you buy a game that is compiled against the [[OpenVR SDK]], then it can run on [[Vive]] and Rift. However, running on Rift uses both runtimes:<br /> <br /> Rendered Image using the OpenVR SDK -> SteamVR Runtime -> Oculus Runtime -> Rift<br /> <br /> The Oculus Runtime effectively thinks you are playing a game called "SteamVR", but the content of the "game" is actually the image that the SteamVR runtime got from the OpenVR compiled game. This seems to work rather well and personally I have not noticed any additional latency. In theory you would even get Asynchronous Timewarp, but that would only happen if SteamVR itself isn't responding in time. If an OpenVR game stalls completely, the SteamVR runtime will throw you back into the loading construct and continues to render at 90fps. Since the SteamVR runtime has this fail safe mechanism and all the Oculus Runtime sees is "SteamVR", it will most likely never trigger Asynchronous Timewarp.<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[apps]], or better said apps compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10207 Developer Resource 2016-05-19T03:15:38Z

<p>Copsaur7: /* Runtimes */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> If you launch a game on Steam that supports [[Rift]] natively (meaning, it has been compiled against the [[OVR SDK]]), you will get [[asynchronous timewarp]] and it will run exactly like the game from Oculus Home. It won't use the the [[SteamVR Runtime]], it will use the [[Oculus Runtime]]. Only downside is that launching the game is more difficult. <br /> <br /> If you buy a game that is compiled against the [[OpenVR SDK]], then it can run on [[Vive]] and Rift. However, running on Rift uses both runtimes:<br /> <br /> Rendered Image using the OpenVR SDK -> SteamVR Runtime -> Oculus Runtime -> Rift<br /> <br /> The Oculus Runtime effectively thinks you are playing a game called "SteamVR", but the content of the "game" is actually the image that the SteamVR runtime got from the OpenVR compiled game. This seems to work rather well and personally I have not noticed any additional latency. In theory you would even get Asynchronous Timewarp, but that would only happen if SteamVR itself isn't responding in time. If an OpenVR game stalls completely, the SteamVR runtime will throw you back into the loading construct and continues to render at 90fps. Since the SteamVR runtime has this fail safe mechanism and all the Oculus Runtime sees is "SteamVR", it will most likely never trigger Asynchronous Timewarp.<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[games]]/[[experiences]], or better said games/experiences compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10206 Developer Resource 2016-05-19T03:15:28Z

<p>Copsaur7: /* App Stores */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[games]]/[[experiences]], or better said games/experiences compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10205 Developer Resource 2016-05-19T03:07:27Z

<p>Copsaur7: /* App Stores */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> If you buy a game on Steam that supports [[Rift]] natively (meaning, it has been compiled against the [[OVR SDK]]), you will get [[asynchronous timewarp]] and it will run exactly like the game from Oculus Home. It won't use the the [[SteamVR Runtime]], it will use the [[Oculus Runtime]]. Only downside is that launching the game is more difficult. <br /> <br /> If you buy a game that is compiled against the [[OpenVR SDK]], then it can run on [[Vive]] and Rift. However, running on Rift uses both runtimes:<br /> <br /> Rendered Image using the OpenVR SDK -> SteamVR Runtime -> Oculus Runtime -> Rift<br /> <br /> The Oculus Runtime effectively thinks you are playing a game called "SteamVR", but the content of the "game" is actually the image that the SteamVR runtime got from the OpenVR compiled game. This seems to work rather well and personally I have not noticed any additional latency. In theory you would even get Asynchronous Timewarp, but that would only happen if SteamVR itself isn't responding in time. If an OpenVR game stalls completely, the SteamVR runtime will throw you back into the loading construct and continues to render at 90fps. Since the SteamVR runtime has this fail safe mechanism and all the Oculus Runtime sees is "SteamVR", it will most likely never trigger Asynchronous Timewarp.<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[games]]/[[experiences]], or better said games/experiences compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Android_VR&diff=10187 Android VR 2016-05-18T23:03:52Z

<p>Copsaur7: Redirected page to Daydream</p> <hr /> <div>#REDIRECT [[Daydream]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=AndroidVR&diff=10186 AndroidVR 2016-05-18T23:02:02Z

<p>Copsaur7: Copsaur7 moved page AndroidVR to Daydream</p> <hr /> <div>#REDIRECT [[Daydream]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Daydream&diff=10185 Daydream 2016-05-18T23:02:02Z

<p>Copsaur7: Copsaur7 moved page AndroidVR to Daydream</p> <hr /> <div>{{stub}}<br /> [[AndroidVR]] is [[Google]]'s [[Virtual Reality Platform]]. Designed to expend [[Android]], the company's mobile platform, AndroidVR was unveiled in Google I/O 2016.<br /> <br /> AndroidVR was first discovered in the release notes for Preview 3 of Unreal Engine 4.12. As of May 11, 2016, not much is known about AndroidVR. Google could incorporate [[Cardboard]] into AndroidVR. There are also rumors about Google making a [[Slide-on HMD]] similar to [[Gear VR]].<br /> ==Devices==<br /> <br /> ==Accessories==<br /> <br /> ==Platform==<br /> <br /> ==Apps==<br /> <br /> ==Developer==<br /> <br /> ==Technology==<br /> <br /> ==History==<br /> <br /> ==References==<br /> <br /> [[Category:Virtual Reality Platforms]]</div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10184 Developer Resource 2016-05-18T22:52:38Z

<p>Copsaur7: /* App Stores */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads [[games]] and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu.<br /> <br /> If you buy a native [[Oculus Rift]] game on Steam, you will get [[asynchronous timewarp]] and it will run exactly like the game from Oculus Home. It won't use the the [[SteamVR Runtime]], it will use the [[Oculus Runtime]]. Only downside is that launching the game is more difficult. Upside is that your game could potentially be device agnostic, i.e. games can support multiple [[headsets]] natively.<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[games]]/[[experiences]], or better said games/experiences compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10183 Developer Resource 2016-05-18T18:48:27Z

<p>Copsaur7: /* Wrappers and Injectors */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[games]]/[[experiences]], or better said games/experiences compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the [[SteamVR Runtime]]. The game thinks it's connected to a [[Rift]], but it is not. The SteamVR runtime is rendering the game and supports [[reprojection]], but not [[asynchronous timewarp]] (remember, this is a feature of the [[Oculus Runtime]]).<br /> <br /> All Oculus games distributed through [[Oculus Home]] implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in [[Lucky's Tale]]: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> Sidenote: technically one could even write a wrapper that routes [[OpenVR]] calls to the Oculus runtime directly, bypassing [[SteamVR]] altogether. But since SteamVR can do it already, there is little need for that<br /> <br /> *[[LibOVRWrapper]] installs dlls into [[Windows]] that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> *LibOVRWrapper + ReVive allows you to run old Rift games on [[Vive]].<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10182 Developer Resource 2016-05-18T17:12:00Z

<p>Copsaur7: /* Wrappers and Injectors */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> [[Oculus Rift]] [[games]]/[[experiences]], or better said games/experiences compiled with the [[OVR]] [[dll]]s do not render to the [[HMD]] directly. They render their images and send them to the [[runtime]]. The interface for that are the dlls. [[Wrappers]] replace the content of the dlls with functions that are named identically, but redirect the games rendered image to a different runtime. Equally, they provide the game with the [[rotational tracking|rotation]] and [[positional tracking|position]] data of the headset.<br /> <br /> *[[ReVive]] replaces the content of the dlls with functions that communicate with the SteamVR runtime. The game thinks it's connected to a Rift, but it is not. The SteamVR runtime is rendering the game and supports reprojection, but not async timewarp (remember, this is a feature of the Oculus runtime).<br /> <br /> All Oculus games distributed through Oculus Home implement an entitlement check. This means the game is asking Oculus Home if the user is allowed to play it. ReVive does not hack this entitlement check and games need to be downloaded/purchased via Oculus Home. Games need to be started through Home once or the Oculus Service needs to be restarted. Example of the entitlement check failing in Lucky's Tale: Instead of the main menu, ReVive users see a worm on a log showing you it's tongue.<br /> <br /> (Sidenote: technically one could even write a wrapper that routes OpenVR calls to the Oculus runtime directly, bypassing SteamVR altogether. But since SteamVR can do it already, there is little need for that)<br /> <br /> *[[LibOVRWrapper]] installs dlls into Windows that old Rift games need in order to communicate with the new runtime. It effectively translates old games to the new runtime. [unsure: Do these old games now also use timewarp or do they need to specifically request it via an sdk call?]<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10181 Developer Resource 2016-05-18T17:08:37Z

<p>Copsaur7: /* App Stores */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the [[Rift]] to work. By default only supports [[apps]] from the [[Oculus Store]] (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the [[Universal Menu]] on the [[Xbox]] button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching [[OpenVR]] games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10180 Developer Resource 2016-05-18T17:02:35Z

<p>Copsaur7: /* Runtimes */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for [[asynchronous timewarp]] and handles device detection, display, etc. It (the runtime service) needs to be running for [[Oculus Home]] to launch.<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the Rift to work. By default only supports apps from the store (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the Universal Menu on the Xbox button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching OpenVR games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10179 Developer Resource 2016-05-18T17:00:49Z

<p>Copsaur7: /* SDKs */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. '''SDKs do not handle [[asynchronous timewarp]] or [[reprojection]], those are handled by the runtime!'''<br /> <br /> *'''[[OVR]]''' - Made by [[Oculus VR]] for the [[Oculus Rift]]. Current version (14th May 2016) is 1.3.1 and can access all features of the [[Oculus Runtime]].<br /> <br /> *'''[[OpenVR]]''' - Made by [[Valve]] and supports [[Vive]] and [[Rift]] via the [[SteamVR Runtime]].<br /> <br /> Sidenote to SDK's and [[Unity]] games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, [[Gear VR]] and [[PSVR]], but not [[SteamVR]]. A game compiled with Unity 5.3 can use those optimizations with the [[Oculus SDK]] but not the [[OpenVR SDK]]. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the Rift to work. By default only supports apps from the store (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the Universal Menu on the Xbox button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching OpenVR games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10178 Developer Resource 2016-05-18T16:55:27Z

<p>Copsaur7: </p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> <br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==App Stores==<br /> [[App Stores]] are distribution platforms for software.<br /> <br /> *'''[[Oculus Home]]''' needs to be running for the Rift to work. By default only supports apps from the store (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the Universal Menu on the Xbox button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching OpenVR games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10177 Developer Resource 2016-05-18T10:32:17Z

<p>Copsaur7: /* Software Distribution Platforms */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> <br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> {{see also|App Stores}}<br /> *'''[[Oculus Home]]''' needs to be running for the Rift to work. By default only supports apps from the store (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the Universal Menu on the Xbox button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching OpenVR games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10176 Developer Resource 2016-05-18T10:31:53Z

<p>Copsaur7: /* Software Distribution Platforms */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> <br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> {{see also|Stores}}<br /> *'''[[Oculus Home]]''' needs to be running for the Rift to work. By default only supports apps from the store (checkbox in the settings of the 2d desktop client to enable other sources). It downloads games and runs them. It also handles the Universal Menu on the Xbox button.<br /> <br /> *'''[[Steam]]/[[SteamVR]]''' technically does not need to run when launching OpenVR games, but highly recommended (room setup and config is pulled from there). Also handles overlay menu on the Xbox button, or when running on the Rift, it launches by pressing the select/start button in the Oculus Universal Menu<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10175 Developer Resource 2016-05-18T10:31:05Z

<p>Copsaur7: /* Runtimes */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> <br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> *'''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> *'''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10174 Developer Resource 2016-05-18T10:30:56Z

<p>Copsaur7: /* SDKs */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> <br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> '''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> '''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10173 Developer Resource 2016-05-18T10:30:39Z

<p>Copsaur7: /* SDKs */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> '''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> <br /> '''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> *Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> '''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> '''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10172 Developer Resource 2016-05-18T10:30:27Z

<p>Copsaur7: /* Runtimes */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> '''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> '''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> *Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> [[Runtimes]] are <br /> <br /> '''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> '''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10171 Developer Resource 2016-05-18T10:30:10Z

<p>Copsaur7: /* SDKs */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> '''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> '''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> *Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> '''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> '''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10170 Developer Resource 2016-05-18T10:28:59Z

<p>Copsaur7: /* Runtimes */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> '''[[Oculus Runtime]]''' is responsible for async timewarp and handles device detection, display, etc. It (the runtime service) needs to be running for Oculus Home to launch<br /> <br /> '''[[SteamVR Runtime]]''' is responsible for reprojection and supports Rift and Vive<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10169 Developer Resource 2016-05-18T10:27:54Z

<p>Copsaur7: /* SDKs */</p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> [[SDKs]] or [[Software Development Kits]] are used to build [[VR]] [[games]] and [[experiences]]. A game/experience can either implement [[OVR]] or [[OpenVR]] or both. This means that the game/experience has access to native functionality in it's corresponding runtime. SDKs do not handle async timewarp or reprojection, those are handled by the runtime!<br /> <br /> *'''[[OVR]]''' - Made by Oculus for the Oculus Rift. Current version (14th May 2016) is 1.3.1 and can access all features of the Oculus runtime.<br /> *'''[[OpenVR]]''' - Made by Valve and supports Vive and Rift via the SteamVR runtime.<br /> <br /> Sidenote to SDK's and Unity games: Unity 5.3 currently has optimizations for VR in their native mode. The native mode supports Rift, Gear and PSVR, but not SteamVR. A game compiled with Unity 5.3 can use those optimzations with the Oculus SDK but not the OpenVR SDK. The OpenVR SDK has it's own optimizations, which may or may not result in similar performance. However, the upcoming Unity 5.4 will support SteamVR natively and performance should be more or less identical. Please note: this is Unity specific and other engines might have similar or different optimizations for some or all headsets.<br /> <br /> ==Runtimes==<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7 https://vrarwiki.com/index.php?title=Developer_Resource&diff=10168 Developer Resource 2016-05-18T09:52:59Z

<p>Copsaur7: </p> <hr /> <div>{{stub}}<br /> <br /> ==SDKs==<br /> <br /> ==Runtimes==<br /> <br /> ==Software Distribution Platforms==<br /> <br /> ==Wrappers and Injectors==<br /> <br /> ==Resources==<br /> [[Oculus Sample Framework]] and [[Oculus Sample Framework for Unity 5]]<ref>https://developer.oculus.com/blog/introducing-the-oculus-sample-framework-for-unity-5/</ref> - Experimental sandbox for VR developers and designers.<br /> <br /> ==3D models==<br /> * [https://www.yobi3d.com Yobi3D - 3D model search engine]: offers a 3D viewer to see search results in 3D. Also works with Cardboard.<br /> <br /> ==References==<br /> <references /></div>

Copsaur7