MixedRealityToolkit-Unity
MixedRealityToolkit-Unity copied to clipboard
Platform Controller Visualization
Overview
This PR enables the loading of controller models from the platform itself. This PR also allows for backup models to be specified in the case that the platform model cannot be loaded
Changes
- Fixes: #10568, #10731
I'm really, really hesitant about all the async utilities introduced into the Core package. Do we absolutely need them? The way it sets objects to
DontDestroyOnLoad
is extremely worrying to me.Is there a way we can adapt + trim down the async utilities to something extremely tiny and doesn't pollute the Core package, or set random things to
DontDestroyOnLoad
?
The Async library has since been removed. It was vestigial from our MRTK2 implementation.
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
Fallback controller model is appearing during input simulation regardless of what the Input Simulator's simulation mode is set to (hand, controller, etc)
And on device
Is there a reason why we still have the gizmos.fbx/gizmos folder?
(these things)
Is there a reason why we still have the gizmos.fbx/gizmos folder?
(these things)
Removed these gizmos
I am a bit confused about pointerPosition vs aimPosition in this PR... Are they the same? Also I thought we were done with pointer
s in MRTK3, apparently that's not the case here
I am a bit confused about pointerPosition vs aimPosition in this PR... Are they the same? Also I thought we were done with
pointer
s in MRTK3, apparently that's not the case here
They are functionally the same in this PR. This PR shouldn't have added any new terminology which refers to pointerPosition or pointerPose. I went with using aimPose as the default in this PR to be a bit more explicit about what the orientation of the pose is supposed to represent semantically.
Our input action is still called a pointerPosition/Rotation, however, this is used as an "aimPose" logically in code.
Testing on device soon. Above reviews are just looking at code.
What's this dependency used for? on a quick scroll through here, I didn't see the namepace used, but I might have missed it.
Removed it from the amsdef
Fully vetted now to work with a moving xr rig