Mixedrealitytoolkit-unity: Add Oculus Quest Support for MRTK
Overview
Oculus Quest is a great wireless VR experience that has potential to be adopted en masse by consumers. It would be great if MRTK could support this platform, to enable developers to build applications that can reach a broad audience.
Expected Behavior
Oculus would be supported either through the OpenVR data provider. Since Oculus Quest is an Android platform, the MRTK project needs to compile and deploy for Android. Finally, we need to add a controller mapping and type for the oculus quest controllers to appropriately map the inputs. We may actually be able to re-use the oculus touch controller mapping.
julenka
All 17 comments
SO to be clear from a deployment approach. The Oculus devices will support OpenVR for sideloading, as such the MRTK (WIth the Android / OpenVR controller support) should support this out of the box.
However, in order to publish to the Oculus store, the MRTK will also require native Oculus support with the Oculus APIs in an extension.
SimonDarksideJ
on 24 May 2019
@julenka Support for Oculus Quest would be awesome. Is there an estimated time when this will be added into mrtk?
ChauNTran
on 29 May 2019
Hi, at this time we don't have an estimate for when our FTEs will get to it, our team is currently focusing on increasing quality of existing features before tackling new ones. However, community contribution would be very welcome here! I'd be happy to take a look at any PR adding Oculus Quest support.
julenka
on 29 May 2019
Early version of Oculus Quest support for MRTK created by contributor tattichan from HoloLab twitter and github repo.
julenka
on 15 Jul 2019
No ETA yet on official support from Microsoft, referring to @wiwei and @chbecker-ms who can provide info about official support.
julenka
on 15 Jul 2019
XRTK is currently in the process of publishing it's native Oculus support (Rift / Quest) which is what tattichan work is based on. Once it's got past the extension review process, it should land fairly quickly after that.
SimonDarksideJ
on 15 Jul 2019
Keeping the discussion focused to what's being worked on this repo - we're currently acquiring some devices and looking to schedule time in our upcoming iteration to add this support.
wiwei
on 25 Jul 2019
Hand tracking is coming to oculus Quest early 2020!
Would be awesome to use MRTK hand tracking on Quest and HoloLens 2!
Is there any overall status update on MRTK Quest support?
SiriusA7
on 27 Sep 2019
I also have a working state with both Oculus Quest and Oculus Go now. Next up, teleport and manipulation-z-direction for the Go:
I'm using parts of the Oculus Integration pack to get controller visuals, API calls and Gradle build modifications.
Alexees
on 7 Nov 2019
Something to be aware of @Alexees as this hit us in the XRTK. Unity does not offset headset height for the Oculus platform through their app. This has to be grabbed from their API or estimated (like HL)
This is also true for OpenVR on the Quest or on PC when the Oculus client is used to host OpenVR (Instead of SteamVR)
This affects teleporting / head height. And be careful, if you offset the head pose, this will NOT correspondingly alter the controller pose, they are handled separately.
SimonDarksideJ
on 7 Nov 2019
This has to be grabbed from their API or estimated (like HL)
@SimonDarksideJ does a HL estimation algorithm exist?
Alexees
on 7 Nov 2019
Thoughts @davidkline-ms , on whether your current case of HL height offset could be used here?
My only concern with that (and the HL height offset) is it is a global settings, meaning your project either IS or is not a HL project and has to be manually set between builds.
We've taken an alternate approach in the XRTK to determine the setting is used only IF unity is not managing the headset height (as it does with WMR / OpenVR under Steam)
SimonDarksideJ
on 7 Nov 2019
Hand Tracking is finally available on the Quest!
SDK is rolling out next week!
SiriusA7
on 9 Dec 2019
Just wanted to make sure this great work by @tarukosu was linked to this issue as currently it looks like the best implementation we've got.
RoyMudie
on 30 Jan 2020
Here is another one. Supports Go and Quest:
https://github.com/HoloSpaces/MixedRealityToolkit-Unity/tree/mrtk_oculusGo
Alexees
on 30 Jan 2020
@RoyMudie just want to chime in with my own implementation. It does not support Go, but it does support controllers, link, hands, and hotswapping input methods.
My work is built on the work of @tarukosu, though it does add a number of improvements.
https://github.com/provencher/MRTK-Quest
provencher
on 30 Jan 2020
@provencher @tarukosu
https://forums.oculusvr.com/community/discussion/86022/quest-go-build-13-0-release-notes/p1
I'm sure you've seen this, but just in case you haven't...
"Remote rendering support for Unity has been added so developers can more easily build and test Hand Tracking apps through their PC" 馃憤
RoyMudie
on 5 Feb 2020
Related issues
nrchuanqi
路
3Comments
chrisfromwork
路
3Comments
Alexees
路
3Comments
StephenHodgson
路
3Comments
jimstack
路
3Comments
Most helpful comment
@RoyMudie just want to chime in with my own implementation. It does not support Go, but it does support controllers, link, hands, and hotswapping input methods.
My work is built on the work of @tarukosu, though it does add a number of improvements.
https://github.com/provencher/MRTK-Quest