releases/2.5.4mrtk_developmentreleases/2.1.0releases/2.2.0releases/2.3.0releases/2.4.0releases/2.5.0releases/2.5.1releases/2.5.2releases/2.5.3

We've moved!

Starting from MRTK 2.6, we are publishing both conceptual docs and API references on docs.microsoft.com. For conceptual docs, please visit our new landing page. For API references, please visit the MRTK-Unity section of the dot net API explorer. Existing content will remain here but will not be updated further.

    Show / Hide Table of Contents

    Controllers

    Controllers are created and destroyed automatically by input providers. Each controller type has a number of physical inputs defined by an axis type, telling us the data type of the input value (Digital, Single Axis, Dual Axis, Six Dof, ...), and an input type (Button Press, Trigger, Thumb Stick, Spatial Pointer, ...) describing the origin of the input. Physical inputs are mapped to input actions via in the Controller Input Mapping Profile, under the Input System Profile in the Mixed Reality Toolkit component.

    • Improve this Doc
    Back to top Generated by DocFX