Meta Quest Pro Support

[ProbablePrime]

Is your feature request related to a problem? Please describe.

Meta Quest Pro owners would like to use this headset natively

Describe the solution you'd like

I'd like Resonite to support the Meta Quest Pro natively with all of its features exposed, similar to the integration with the Vive Pro Eye

Describe alternatives you've considered

There are mods to achieve this that work as a work around but it would be good to be supported natively.

Additional Context

I am pre-seeding the issue repository with commonly requested headsets to prevent those issues from being made as duplicates once open.

[Geenz]

We have an internal version of this using ALXR. It needs some more work, but we can get this pushed out.

[Meister1593]

ALVR is also willing to cooperate to integrate with Resonite for headsets like Quest Pro.

[Zeitheron]

Would be nice to have it also work with VirtualDesktop, not just AL!

[alexderpyfox]

i have a quest pro too it would be nice if the quest pro intergration would be made in such a way that people could select what streamer software they use maybe with resonite modules that connect to the native quest pro component

[DoubleStyx]

Is this for supporting face tracking natively or for directly interfacing with Resonite without any additional runtimes?

[alexderpyfox]

the modules would just be for direct integrating any streamer that adds resonite support to it no additional runtime this would also add the ability to add many more headsets efficiently and people can chose any streamer they like

[hazre]

For Eye and Face tracking features, there needs to be more parameters made available in AvatarExpressionDriver that covers all ARKit, Meta Movement (Quest Pro) and SRanipal.

For example Resonite's current eye and face tracking has no ablity to drive eye brow blendshapes.

Good example that has already all those Tracking Standards Unified is VRCFaceTracking Program.

https://docs.vrcft.io/docs/tutorial-avatars/tutorial-avatars-extras/compatibility/overview#standard-comparisons

[sjsanjsrh]

It would be nice if it wasn't dependent on SteamVR. Connecting with only the quest link performs better. And you will be free from SteamVR instability.

[alexderpyfox]

Nah it's horrible via link because it requires oculus runtime so rip any playspacemover overlay Desktop fbt etc so best would be the modular system so people can chose what software they use if they want link they can use it but others want to use steamvr

[Mrs-Feathers]

a standalone for quest would 1. make it easier for people who can't get a thousand dollar headset but are able to get a 300$ quest 2 but still dont have a gaming computer to support it to be able to join your game, so more players like me... who finds myself in a weird position that is, having a community that's active building worlds and all that for us, but i can't join or help my own community because my computer is old and quest isn't supported.

and 2. with a quest you can take it anywhere. imagine building an office with web controls via webhooks and xmlrpc and being able to pop in wherever. i dont mind not having a desktop i can pull up if i can use a vr web browser.. i've got all i need on web pages... and can use grafana to control and make stuff look nice. imagine access to a server control room wherever you are.. on a device smaller than a full laptop.

quest support would highly benefit your community.

[Geenz]

As a point of clarification - this issue is for enabling eye and mouth tracking. Not for standalone support.

[sjsanjsrh]

https://github.com/korejan/libalxr-sharp I think it would be a good idea to refer to the library.

[SlyTheFloof]

this is fantastic