Merge pull request #6873 from keveleigh/update-controller-doc

Update controller docs to more correctly represent the current state of features

Author: keveleigh

Assets/MixedRealityToolkit.SDK/Profiles/MixedRealityControllerConfigurationProfile.md

@@ -50,32 +50,32 @@ Your custom name for the controller, just for easy reference
 A drop down list of supported controllers by the Mixed Reality Toolkit, namely:
 
 * Windows Mixed Reality
-    * Motion Controllers
+  * Motion Controllers
+  * HoloLens 2 articulated hands
+  * HoloLens 1 hands
+  * HoloLens 1 clicker
 * OpenVR
-    * Default (fallback) controllers
-    * Oculus Touch
-    * Vive Wand 
-    * Vive Knuckles (experimental as no one has any, using Unity spec)
-* OpenXR
-    * To be supported when there is an OpenXR specification
-* Windows Gaming (these are coming soon*)
-    * Arcade stick
-    * Gamepad
-    * Joystick
-    * Racing Wheel
-* Simulator (coming soon)
+  * Default (fallback) controllers
+  * Oculus Touch
+  * Vive Wand
+  * Vive Knuckles (experimental)
+* Windows Gaming
+  * Gamepad (like Xbox)
 
 ### Handedness
 Which hand is configured for this controller definition
 > Both does not configure all controllers at this time.
 
 ### Use Default model
-For this controller only, use the model for the controller direct from the SDK (where available), so that you don't have to configure a custom model.
-> This overrides the Global Model setting
+
+For this controller only, use the model for the controller direct from the SDK (where available), so that you don't have to configure a custom model. This overrides the Global Model setting.
+
+> [!NOTE]
+> This is currently supported on both Windows Mixed Reality and OpenVR, loading any controller models provided by the platform API.
 
 ### Override Model
-Like the Global Model options, allows you to provide a model to be drawn for this specific controller.
-> This overrides the Global Model setting
+
+Like the Global Model options, allows you to provide a model to be drawn for this specific controller. This overrides the Global Model setting.
 
 ### Interaction Mappings
 The interaction mappings allow you to map logical input actions for use in your project to the various controller inputs available from the physical device.  
@@ -136,4 +136,4 @@ Source -> Included as part of the Unity SteamVR SDK, or the Steam VR Client
 
 If you use Steams Models, we recommend applying the following Prefab transform values to align the controller model when using to align with the users view:
 * Position - no change
-* Rotation - no change
+* Rotation - no change

Documentation/MixedRealityConfigurationGuide.md

@@ -297,8 +297,7 @@ In addition to the controller mapping, a separate configuration profile is provi
 
 This can be configured at a "Global" (all instances of a controller for a specific hand) or specific to an individual controller type / hand.
 
-> [!IMPORTANT]
-> The MRTK does not currently support native SDK's controller models as Unity does not yet provide the capability to load / render gLTF models, which is the default type of models provided by most SDKs. This will be enhanced when this is available.
+The MRTK also supports native SDK controller models for Windows Mixed Reality and OpenVR. These are loaded as GameObjects in your scene and positioned using the platform's controller tracking.
 
 If your controller representation in the scene needs to be offset from the physical controller position, then simply set that offset against the controller model's prefab (e.g. setting the transform position of the controller prefab with an offset position).