Open IssueSyncBot opened 1 year ago
Anything that forces a Unity version change should be gated with ifdefs & MRTK functionality be left in place but able to be disabled.
PR available for alternative socket interactor impl. #526. Wyck is adding a feature request.
Original issue opened by:
@AMollis
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
ArticulatedHandController
into two separate controllers, one for articulated hands and one for hand controllers. (MSFT Cost Estimate: 5)IInteractionModeDetectors
and 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 https://github.com/microsoft/MixedRealityToolkit-Unity/issues/11557). (MSFT Cost Estimate: 5)PokeInteractor
(MSFT Cost Estimate: 5)FuzzyGazeInteractor
. (MSFT Cost Estimate: 5)ISSUE MIGRATION
Issue migrated from: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/11679