Developer Resource - Revision history

Xinreality at 00:35, 28 October 2025

2025-10-28T00:35:27Z

← Older revision		Revision as of 00:35, 28 October 2025
Line 88:		Line 88:
	While OpenXR has successfully standardized the foundational layer of XR development, its "write once, run anywhere" promise is not absolute. For standalone Android-based headsets, developers often still need to create separate application packages (APKs) for different platforms like Meta Quest and Pico, as these platforms may use their own vendor-specific OpenXR loaders.<ref name="RedditOpenXRUniversal">https://www.reddit.com/r/virtualreality/comments/wi6w2x/vr_devs_just_how_universal_is_openxr_anyways/ - VR Devs, just how universal is OpenXR anyways?</ref>		While OpenXR has successfully standardized the foundational layer of XR development, its "write once, run anywhere" promise is not absolute. For standalone Android-based headsets, developers often still need to create separate application packages (APKs) for different platforms like Meta Quest and Pico, as these platforms may use their own vendor-specific OpenXR loaders.<ref name="RedditOpenXRUniversal">https://www.reddit.com/r/virtualreality/comments/wi6w2x/vr_devs_just_how_universal_is_openxr_anyways/ - VR Devs, just how universal is OpenXR anyways?</ref>

	Furthermore, innovative platform-specific ~~features—such~~ as Meta's advanced Passthrough capabilities, hand tracking enhancements, or [[spatial anchors]]~~—are~~ exposed to developers through vendor-specific extensions to the OpenXR standard.<ref name="MetaOpenXRAdvancements">https://developers.meta.com/horizon/blog/openxr-standard-quest-horizonos-unity-unreal-godot-developer-success/ - Meta and OpenXR</ref> To leverage these powerful features, a developer must write code that specifically targets that vendor's hardware.		Furthermore, innovative platform-specific features, such as Meta's advanced Passthrough capabilities, hand tracking enhancements, or [[spatial anchors]], are exposed to developers through vendor-specific extensions to the OpenXR standard.<ref name="MetaOpenXRAdvancements">https://developers.meta.com/horizon/blog/openxr-standard-quest-horizonos-unity-unreal-godot-developer-success/ - Meta and OpenXR</ref> To leverage these powerful features, a developer must write code that specifically targets that vendor's hardware.

	===Meta Quest SDK===		===Meta Quest SDK===
Line 550:		Line 550:

	===Alternative Distribution: SideQuest===		===Alternative Distribution: SideQuest===
	[[SideQuest]] is the leading third-party platform and community for the Meta Quest ecosystem. Its primary function is to facilitate the "sideloading" of ~~applications—the~~ process of installing an app directly onto the headset via a PC, bypassing the official store.<ref name="SideQuestSetup">https://sidequestvr.com/setup-howto - Get SideQuest</ref>		[[SideQuest]] is the leading third-party platform and community for the Meta Quest ecosystem. Its primary function is to facilitate the "sideloading" of applications, the process of installing an app directly onto the headset via a PC, bypassing the official store.<ref name="SideQuestSetup">https://sidequestvr.com/setup-howto - Get SideQuest</ref>

	SideQuest has become a vital hub for:<ref name="SideQuestHome">https://sidequestvr.com/ - SideQuest</ref>		SideQuest has become a vital hub for:<ref name="SideQuestHome">https://sidequestvr.com/ - SideQuest</ref>

Xinreality: Text replacement - "e.g.," to "for example"

2025-10-28T00:29:37Z

Text replacement - "e.g.," to "for example"

Xinreality at 22:51, 13 October 2025

2025-10-13T22:51:07Z

Show changes

RealEditor: destub

2025-07-02T20:15:42Z

destub

← Older revision		Revision as of 20:15, 2 July 2025
Line 1:		Line 1:
	~~{{stub}}~~
	{{TOCRIGHT}}		{{TOCRIGHT}}
	==How to Get Started==		==How to Get Started==

Neo222 at 11:42, 4 January 2017

2017-01-04T11:42:23Z

← Older revision		Revision as of 11:42, 4 January 2017
Line 1:		Line 1:
	{{stub}}		{{stub}}
			{{TOCRIGHT}}
	==How to Get Started==		==How to Get Started==
	{{see also\|How to Get Started in VR Development}}		{{see also\|How to Get Started in VR Development}}

Neo222 at 03:41, 3 January 2017

2017-01-03T03:41:21Z

← Older revision		Revision as of 03:41, 3 January 2017
Line 60:		Line 60:
	==Resources==		==Resources==
	[[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.		[[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.
			{{see also\|Resources Directory}}
			{{:Resources Directory}}

	==3D models==		==3D models==

Neo222 at 03:20, 3 January 2017

2017-01-03T03:20:57Z

← Older revision		Revision as of 03:20, 3 January 2017
Line 2:		Line 2:

	==How to Get Started==		==How to Get Started==
	{{see also\|How to Get Started ~~as a~~ VR ~~Developer~~}}		{{see also\|How to Get Started in VR Development}}
	{{:How to Get Started ~~as a~~ VR ~~Developer~~}}		{{:How to Get Started in VR Development}}

	==SDKs==		==SDKs==

Neo222 at 03:04, 3 January 2017

2017-01-03T03:04:27Z

← Older revision		Revision as of 03:04, 3 January 2017
Line 1:		Line 1:
	{{stub}}		{{stub}}

			==How to Get Started==
			{{see also\|How to Get Started as a VR Developer}}
			{{:How to Get Started as a VR Developer}}

	==SDKs==		==SDKs==

Copsaur7 at 05:11, 19 May 2016

2016-05-19T05:11:36Z

← Older revision		Revision as of 05:11, 19 May 2016
Line 17:		Line 17:
	*'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].		*'''[[SteamVR Runtime]]''' is responsible for [[reprojection]] and supports [[Rift]] and [[Vive]].

	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.		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.

	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:		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:

Copsaur7: /* App Stores */

2016-05-19T03:40:25Z

App Stores

← Older revision		Revision as of 03:40, 19 May 2016
Line 31:		Line 31:

	*'''[[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.		*'''[[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.

			===Example===
			[[Project Cars]] on Steam supports both [[OpenVR]] and [[OVR]]. The Oculus Home version supports only OVR as of today.

			#Project Cars on Home + Rift -> will run natively
			#Project Cars on Steam + Vive -> will run natively
			#Project Cars on Steam + Rift + launched as Rift app -> will run natively
			#Project Cars on Home + Vive -> won't run
			#Project Cars on Steam + Rift + launched as SteamVR app -> will run via SteamVR

	==Wrappers and Injectors==		==Wrappers and Injectors==

← Older revision		Revision as of 00:29, 28 October 2025
Line 25:		Line 25:
	For beginners, the recommended path is to:		For beginners, the recommended path is to:
	# Choose a game engine ([[Unity]], [[Unreal Engine]], or [[Godot]])		# Choose a game engine ([[Unity]], [[Unreal Engine]], or [[Godot]])
	# Select target [[VR headset\|VR headsets]] (~~e.g.,~~ [[Meta Quest 3]], [[Meta Quest 3S]], [[Apple Vision Pro]], [[PSVR2]])		# Select target [[VR headset\|VR headsets]] (for example [[Meta Quest 3]], [[Meta Quest 3S]], [[Apple Vision Pro]], [[PSVR2]])
	# Set up the appropriate [[SDK]] and development environment		# Set up the appropriate [[SDK]] and development environment
	# Study platform-specific guidelines and best practices		# Study platform-specific guidelines and best practices
Line 35:		Line 35:
	'''2. Install SDKs:''' For Meta devices, use the [[Meta XR SDK]]. For Apple, the [[visionOS SDK]]. Adopt [[OpenXR]] for cross-platform compatibility.		'''2. Install SDKs:''' For Meta devices, use the [[Meta XR SDK]]. For Apple, the [[visionOS SDK]]. Adopt [[OpenXR]] for cross-platform compatibility.

	'''3. Set Up Hardware:''' Ensure your development PC meets requirements (~~e.g.,~~ high-end GPU for tethered VR). For standalone devices, develop directly on the headset or use simulators like [[Meta XR Simulator]].		'''3. Set Up Hardware:''' Ensure your development PC meets requirements (for example high-end GPU for tethered VR). For standalone devices, develop directly on the headset or use simulators like [[Meta XR Simulator]].

	'''4. Learn Basics:''' Study motion tracking, anchors, environmental understanding, and depth APIs. Resources include official documentation from Meta, Apple, and Khronos Group.		'''4. Learn Basics:''' Study motion tracking, anchors, environmental understanding, and depth APIs. Resources include official documentation from Meta, Apple, and Khronos Group.
Line 288:		Line 288:
	! Community Size \|\| Larger, more beginner-friendly resources<ref name="AnimostUnityVsUnreal"></ref> \|\| Smaller but strong, particularly for high-end development<ref name="AnimostUnityVsUnreal"></ref>		! Community Size \|\| Larger, more beginner-friendly resources<ref name="AnimostUnityVsUnreal"></ref> \|\| Smaller but strong, particularly for high-end development<ref name="AnimostUnityVsUnreal"></ref>
	\|-		\|-
	! Primary Target Platform (XR) \|\| Strongest in standalone and mobile VR (~~e.g.,~~ Meta Quest)<ref name="RedditUnityVsUnreal"></ref> \|\| Strongest in PCVR and high-fidelity simulations<ref name="RedditUnityVsUnreal"></ref>		! Primary Target Platform (XR) \|\| Strongest in standalone and mobile VR (for example Meta Quest)<ref name="RedditUnityVsUnreal"></ref> \|\| Strongest in PCVR and high-fidelity simulations<ref name="RedditUnityVsUnreal"></ref>
	\|-		\|-
	! Ideal Use Cases \|\| Indie games, mobile/standalone VR/AR, rapid prototyping, projects prioritizing speed-to-market \|\| AAA games, architectural visualization, cinematic experiences, enterprise simulations requiring photorealism<ref name="WebarooUnityVsUnreal"></ref>		! Ideal Use Cases \|\| Indie games, mobile/standalone VR/AR, rapid prototyping, projects prioritizing speed-to-market \|\| AAA games, architectural visualization, cinematic experiences, enterprise simulations requiring photorealism<ref name="WebarooUnityVsUnreal"></ref>
Line 299:		Line 299:

	====Prerequisites====		====Prerequisites====
	Before creating a project, developers must use the [[Unity Hub]] to install a supported version of the Unity Editor (~~e.g.,~~ 2022.3 LTS or newer). During installation, it is crucial to include the [[Android Build Support]] module, as this is a requirement for developing applications for Android-based standalone headsets like the Meta Quest.<ref name="MetaUnitySetup">https://developers.meta.com/horizon/documentation/unity/unity-project-setup/ - Set Up Your Unity Project for Meta Quest Development</ref>		Before creating a project, developers must use the [[Unity Hub]] to install a supported version of the Unity Editor (for example 2022.3 LTS or newer). During installation, it is crucial to include the [[Android Build Support]] module, as this is a requirement for developing applications for Android-based standalone headsets like the Meta Quest.<ref name="MetaUnitySetup">https://developers.meta.com/horizon/documentation/unity/unity-project-setup/ - Set Up Your Unity Project for Meta Quest Development</ref>

	====Creating a Project and Configuring the Build Platform====		====Creating a Project and Configuring the Build Platform====
Line 379:		Line 379:
	The template includes two primary, comfort-oriented locomotion methods:<ref name="UnrealVRTemplateDocs"></ref>		The template includes two primary, comfort-oriented locomotion methods:<ref name="UnrealVRTemplateDocs"></ref>
	* '''Teleportation:''' The user can aim with one controller, which displays an arc and a target location. Releasing the thumbstick instantly moves the pawn to that location. This system relies on a [[Nav Mesh Bounds Volume]] placed in the level.		* '''Teleportation:''' The user can aim with one controller, which displays an arc and a target location. Releasing the thumbstick instantly moves the pawn to that location. This system relies on a [[Nav Mesh Bounds Volume]] placed in the level.
	* '''Snap Turn:''' Using the other controller's thumbstick, the user can rotate their view in discrete increments (~~e.g.,~~ 45 degrees). This avoids the smooth rotation that can cause motion sickness for some users.		* '''Snap Turn:''' Using the other controller's thumbstick, the user can rotate their view in discrete increments (for example 45 degrees). This avoids the smooth rotation that can cause motion sickness for some users.

	==Runtimes==		==Runtimes==
Line 461:		Line 461:

	=====Feedback=====		=====Feedback=====
	Clear and immediate feedback is essential. Interactive elements should have distinct hover states (~~e.g.,~~ highlighting or scaling up), and actions like button presses should be accompanied by both visual and auditory cues.<ref name="MetaMRDesignGuidelines"></ref>		Clear and immediate feedback is essential. Interactive elements should have distinct hover states (for example highlighting or scaling up), and actions like button presses should be accompanied by both visual and auditory cues.<ref name="MetaMRDesignGuidelines"></ref>

	===Technical Performance and Optimization===		===Technical Performance and Optimization===
Line 480:		Line 480:
	====Core Optimization Strategies====		====Core Optimization Strategies====
	* '''Reduce Draw Calls:''' Combine multiple textures into a single '''texture atlas''' and use '''static batching''' to draw multiple similar objects in a single call. For standalone Quest, developers should aim for 50-200 draw calls per frame.<ref name="MetaUnityPerfDocs"></ref><ref name="MetaDevBlogDrawCalls">https://developers.meta.com/horizon/blog/down-the-rabbit-hole-w-oculus-quest-developer-best-practices-the-store/ - Developer Best Practices</ref>		* '''Reduce Draw Calls:''' Combine multiple textures into a single '''texture atlas''' and use '''static batching''' to draw multiple similar objects in a single call. For standalone Quest, developers should aim for 50-200 draw calls per frame.<ref name="MetaUnityPerfDocs"></ref><ref name="MetaDevBlogDrawCalls">https://developers.meta.com/horizon/blog/down-the-rabbit-hole-w-oculus-quest-developer-best-practices-the-store/ - Developer Best Practices</ref>
	* '''Optimize Geometry:''' Keep polygon counts within the budget for the target platform (~~e.g.,~~ 750k-1M triangles for Quest 2). Use [[Level of Detail]] (LOD) systems.<ref name="MetaUnityPerfDocs"></ref>		* '''Optimize Geometry:''' Keep polygon counts within the budget for the target platform (for example 750k-1M triangles for Quest 2). Use [[Level of Detail]] (LOD) systems.<ref name="MetaUnityPerfDocs"></ref>
	* '''Simplify Lighting and Shaders:''' Use '''baked lighting''' whenever possible. Avoid complex, multi-pass shaders and full-screen post-processing effects on mobile hardware.<ref name="UnityBestPractices"></ref>		* '''Simplify Lighting and Shaders:''' Use '''baked lighting''' whenever possible. Avoid complex, multi-pass shaders and full-screen post-processing effects on mobile hardware.<ref name="UnityBestPractices"></ref>
	* '''Use Occlusion Culling:''' This prevents the engine from rendering objects that are completely hidden from the camera's view.<ref name="MediumVRPerfOpt">https://medium.com/@lemapp09/beginning-game-development-vr-performance-optimization-78553530ca83 - VR Performance Optimization</ref>		* '''Use Occlusion Culling:''' This prevents the engine from rendering objects that are completely hidden from the camera's view.<ref name="MediumVRPerfOpt">https://medium.com/@lemapp09/beginning-game-development-vr-performance-optimization-78553530ca83 - VR Performance Optimization</ref>
Line 570:		Line 570:
	! SideQuest \|\| Meta Quest series \|\| Low (Community-driven)<ref name="SideQuestHome"></ref> \|\| VR enthusiasts, modders, indie game followers \|\| Primary platform for sideloading, experimental content, and early access<ref name="SideQuestSetup"></ref>		! SideQuest \|\| Meta Quest series \|\| Low (Community-driven)<ref name="SideQuestHome"></ref> \|\| VR enthusiasts, modders, indie game followers \|\| Primary platform for sideloading, experimental content, and early access<ref name="SideQuestSetup"></ref>
	\|-		\|-
	! Pico Store \|\| Pico headsets (~~e.g.,~~ Pico 4) \|\| High (Similar to Quest Store)<ref name="PicoDevFAQ">https://sdk.picovr.com/docs/FAQ/chapter_twentyeight.html - Developer Platform FAQ</ref> \|\| Consumers in markets where Pico is prevalent \|\| Growing ecosystem with developer incentive programs<ref name="PicoDevProgram"></ref>		! Pico Store \|\| Pico headsets (for example Pico 4) \|\| High (Similar to Quest Store)<ref name="PicoDevFAQ">https://sdk.picovr.com/docs/FAQ/chapter_twentyeight.html - Developer Platform FAQ</ref> \|\| Consumers in markets where Pico is prevalent \|\| Growing ecosystem with developer incentive programs<ref name="PicoDevProgram"></ref>
	\|}		\|}