Skip to content

Commit

Permalink
Merge pull request #34 from AlexisEvo/patch-1
Browse files Browse the repository at this point in the history
VRChat native eye tracking on Quest Pro was removed - update quest pro page
  • Loading branch information
kusomaigo authored Sep 14, 2023
2 parents a86674c + 9f16aa0 commit be318ea
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/hardware/quest-pro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ All eye and face tracking data is accessed via Meta’s Face and Eye OpenXR exte
The Quest Pro provides developers with both eye and face tracking data from a single, contained device, making it easy for native Quest developers to incorporate.
However, having it only accessible through Meta’s Oculus OpenXR extensions means there must be an OpenXR application using the Oculus runtime running somewhere.
There is currently no way for VRCFT to simultaneously extract data from the headset and send eye and face tracking to the Quest version of VRChat, so the following solutions are only for PCVR.
Note that native Eye Tracking support is now in open beta for the Quest version of VRChat for use with the Quest Pro, which does **not** require the use of VRCFaceTracking to function.
Previously, a beta version of the native VRChat Quest client included built in eye tracking support without the need for VRCFaceTracking. This version is discontinued and is no longer available.

## Setup

Expand Down Expand Up @@ -306,4 +306,4 @@ Don't see your problem here? Think your problem might be unrelated to the module
<!-- - **ALXR/ALVR methods: "[ERROR] No connection could be made because the target machine actively refused it"**
- Cause: The ALXR VRCFT server is not running.
- Solution: Usually the problem is related to [missing a step](#oculus-linkairlink-setup)
and the ALXR log may make it clear as to what step exactly was forgotten. -->
and the ALXR log may make it clear as to what step exactly was forgotten. -->

0 comments on commit be318ea

Please sign in to comment.