I’ve developed an open source project to create digital tours for museums and I wanted to offer support to mixed reality experiences through Meta Quest 3 headset, but I have noticed your Github samples no longer include any sample from where to start. Do you plan to offer support to that platform or you have dropped the support all together?
Hi Esteban,
We do support the Meta Quest 3. The samples aren’t in the samples package though, they’re included in the NSDK meta package as a separate installation.
If you go into Unity, open the Package Manager, and click on the NSDK Meta package, you’ll see a tab labeled “Samples” where you can import the Meta Quest 3 samples from.
No matter what I do the default examples or Meta Quest don’t work. Following the steps of your website the passthrough never works. I’ve been stuck with this for over a week now and I’m desperate.
You should update the instruction in the website because it’s not longer possible to revert to OpenXR version 1.15.1:
The only positive thing is that the space is recognised but even then the LocationMeshManager doesn’t match the real orientation. See video:
Are there any plans to update to a workable state the SDK samples for Meta Quest?
Hi Esteban,
I took some time to run through the Meta Quest setup. Unfortunately I didn’t get to building projects, so I will be picking that up next week. For the OpenXR version, what you want to do (and I’ll make sure to pass this along to our docs team) is the following:
-
Open the Package Manager
-
Click plus on top left corner to add package
-
Select “Install Package by Name”, it should be the last option.
-
Enter the following:
- Name: com.unity.xr.openxr
- Version: 1.15.1
-
Click Install
If the version is not changing to 1.15.1 try uninstalling the package and then installing it with the steps above.
That should force 1.15.1 and if you’re still setting up a project just check back afterward to make sure that nothing else overwrote the version. From my testing with my setup nothing changed the version though.
Thanks for the feedback. I was looking in the other versions for the 1.15.1 and I wasn’t considering the small textfield bellow the domain textfield. Now it works.