You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/MixedRealityConfigurationGuide.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The Mixed Reality Toolkit centralizes as much of the configuration required to m
8
8
9
9
Configuration profiles provide reusable blocks of configuration that can be used and swapped out at runtime (with the exception of the InputActions profile) to meet the demands for most Mixed Reality projects. This allows you to style your configuration for different input types (Driving vs Flying) or different behavior's your project needs.
10
10
11
-
> For more details on profile use, please check the [Profile Usage Guide]() (Coming soon()
11
+
> For more details on profile use, please check the [Configuration Profile Usage Guide]() (Coming soon()
12
12
13
13
In some cases, we also allow you to swap out the underlying system that provides a capability with either your own service or an alternate implementation (e.g. swapping out the speech provider from an OS version to one on Azure)
14
14
@@ -86,7 +86,7 @@ The camera settings define how the camera will be setup for your Mixed Reality p
86
86
87
87
The Mixed Reality Project provides a robust and well-trained input system for routing all the input events around the project which is selected by default.
88
88
89
-
> The MRTK also allows you to write your own Input System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide]() (Coming soon)
89
+
> The MRTK also allows you to write your own Input System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide to building Registered Services]() (Coming soon)
@@ -122,7 +122,7 @@ The boundary system translates the perceived boundary reported by the underlying
122
122
123
123
The Mixed Reality Project provides a full featured Teleportation system for managing teleportation events in the project which is selected by default.
124
124
125
-
> The MRTK also allows you to write your own Teleportation System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide]() (Coming soon)
125
+
> The MRTK also allows you to write your own Teleportation System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide to building Registered Services]() (Coming soon)
@@ -134,7 +134,7 @@ The Mixed Reality Project provides a full featured Teleportation system for mana
134
134
The Mixed Reality Project provides a rebuilt Spatial Awareness system for working with spatial scanning systems in the project which is selected by default.
135
135
You can view the architecture behind the [MRTK Spatial Awareness system here](/Documentation/Architecture/SpatialAwarenessSystemArchitecture.md).
136
136
137
-
> The MRTK also allows you to write your own Spatial Awareness System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide]() (Coming soon)
137
+
> The MRTK also allows you to write your own Spatial Awareness System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide to building Registered Services]() (Coming soon)
@@ -156,7 +156,7 @@ This is only applicable for devices that can provide a scanned environment, such
156
156
157
157
An optional but highly useful feature of the MRTK is the plugin Diagnostics functionality. This presents a style of debug log in to the scene
158
158
159
-
> The MRTK also allows you to write your own Diagnostic System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide]() (Coming soon)
159
+
> The MRTK also allows you to write your own Diagnostic System and you can use the selection below to switch the system used without rewriting the toolkit. For more information on writing your own systems, [please see this guide to building Registered Services]() (Coming soon)
@@ -176,7 +176,7 @@ One of the more advanced areas of the Mixed Reality Toolkit is its [service loca
176
176
177
177
Any registered service still gets the full advantage of all of the Unity events, without the overhead and cost of implementing a MonoBehaviour or clunky singleton patterns. This allows for pure C# components with no scene overhead for running both foreground and background processes, e.g. spawning systems, runtime gamelogic, or practically anything else.
178
178
179
-
[Check out the supporting documentation for more details about creating your own Service Providers]() (Coming Soon)
179
+
Check out the [Guide to building Registered Services]() (Coming Soon) for more details about creating your own services
0 commit comments