#Open - Deploy Everywhere with OpenXR and MRTK3
summary
Claim: MRTK3 plus Unity’s OpenXR path lets one code once and deploy to HoloLens 2, Quest, Leap and others using the mixed reality OpenXR plugin and Unity’s input system. Feature groups replace per-vendor packages; OpenXR interaction profiles map controllers into reusable actions. Hand joint tracking surfaces as a consistent 26-joint stream via a single subsystem. Demo switches from holographic remoting to Oculus Link over USB and the scene and hand input keep working. See MRTK3 Public Preview and the Mixed Reality Feature Tool.
AI-written summary · about
chapters (12)
- 0:00Introduction to MRTK3
- 3:04Limitations of MRTK2
- 5:56OpenXR and Input in MRTK3
- 8:46Installing the Plugin
- 11:15Hand Tracking Extensions
- 13:00Configuring Features
- 15:45Interaction Profiles
- 18:33Input Action Mapping
- 21:02Unified Input Architecture
- 25:45Remoting Demo
- 27:32Quest Demo
- 31:32Q&A and Summary
related talks
46mMixing the Real and Unreal: The Future of XR in UE4
10mMixed Reality check
53mUnderstanding the Opportunity and Impact of Immersive Technologies
02h 15mUnite Austin Live - Day 2 - Vuforia, Microsoft, Google, MWU Showcase, and more
45mLocomotion: Going places in VR
25mVR: Open Source and Standards
56mBringing mixed reality to the web
25mCreating VR (and AR) on the web. Take 2.
