Open
Description
Original issue opened by:
Describe the problem
MRTK3 has implemented custom components on top of XRI that can now be replaced with XRI's latest feature set. We should update MRTK3 to take advantage of these new features and deprecate MRTK3's custom components.
The usage of these new components will be part of a new MRTK3 XR Rig. The existing MRTK rig may then be deprecated, in favor of using the new rig.
Tasks
- New MRTK3 XR Rig should utilize the XR Input Modality Manager for switching between controller and articulated hands. This would require XR Hands, and split MRTK3's
ArticulatedHandControllerinto two separate controllers, one for articulated hands and one for hand controllers. (MSFT Cost Estimate: 5) - New MRTK3 XR Rig should utilize XR Interaction Groups. This may replace the need for MRTK3's
IInteractionModeDetectorsand Interaction Mode Manager. However, there still needs to be a way to disable hand rays if poking or grabbing something, so this may still require some form of the Interaction Mode Manager. Whatever is done, the Interaction Mode Manager can't interfere with the handling of UGUI like it does now (see MRTK3 NonNativeKeyboard & vanilla UGUI doesn't support near touch microsoft/MixedRealityToolkit-Unity#11557). (MSFT Cost Estimate: 5) - New MRTK3 XR Rig should utilize XR Poke Interactor. This would replace the need for MRTK3's
PokeInteractor(MSFT Cost Estimate: 5) - New MRTK3 XR Rig should utilize XR Gaze Interactor or be extended upon for eye gaze input. This may replace the need for MRTK3's
FuzzyGazeInteractor. (MSFT Cost Estimate: 5) - Usie XRI's teleporting rays (MSFT Cost Estimate: 3)
ISSUE MIGRATION
Issue migrated from: microsoft/MixedRealityToolkit-Unity#11679