Skip to content

Commit 589c2d7

Browse files
committed
Add additional general profile info
1 parent d5a3bbc commit 589c2d7

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

Documentation/Profiles/Profiles.md

+6
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,12 @@ For example, the input system's behavior is governed by an input system profile,
77
<img src="../../Documentation/Images/Profiles/input_profile.png" width="650px" style="display:block;">
88
<sup>Profile Inspector</sup>
99

10+
## Background
11+
12+
Profiles are mainly intended to support specific scenarios across multiple devices, which are handled via the data providers. This way, an app can be designed as device-agnosticly as possible and let the MRTK and the profile's data providers handle cross-platform support.
13+
14+
There are also profiles built around the input features of specific devices, such as the HoloLens 1 profile which defaults to GGV-style interactions.
15+
1016
## XR SDK
1117

1218
Currently, there are two profiles provided for XR SDK, `DefaultXRSDKConfigurationProfile` and `DefaultHoloLens2XRSDKConfigurationProfile`. As a result, not all samples scenes are fully supported due to scene- and scenario-specific configurations. Any samples that use `DefaultMixedRealityToolkitConfigurationProfile` and `DefaultHoloLens2ConfigurationProfile` _can_ be swapped over to their corresponding XR SDK profiles. If you're using OpenXR with XR SDK, use the `DefaultOpenXRConfigurationProfile` instead.

0 commit comments

Comments
 (0)