Specifications

It is important that you note the following properties about the Meta Quest Pro. Some of this information comes from the following database info from VRCompare (https://vr-compare.com/headset/metaquestpro):

• Per-Eye Resolution: $1800 \times 1920$
• Visible FOV: $106\degree$ Horizontal, $95.57\degree$ Vertical
• Rendered FOV: $108\degree$ Horizontal, $95.57\degree$ Vertical, $111.24\degree$ Diagonal
• IPD Range: $55-75mm$
• Binocular Overlap: $79.72\degree$
• Refresh Rage: $90Hz$
• Foveated Rendering: ✅

Refresh Rate / FPS

You need to note the refresh rate of 90Hz. This means that each eye display has an upper bound of 90FPS. What this also means is that even if a game can run at a higher FPS or if you’re trying to run Unity builds with an FPS > 90, the MQP will AT MOST run at 90Hz at all times.

The restricted refresh rate of the MQP’s displays is an important consideration for Unity development in particular. In Unity, you can access the MQP’s eye tracking module. However, Meta’s implementation ties the eye tracking sample rate itself to the frame rate. This means that:

1. If your Unity build’s FPS goes below 90FPS, your eye tracking sample rate will also decrease.
2. If your Unity build’s FPS exceeds 90FPS, the MQP’s display will be capped at 90FPS no matter what you do.

So if you want high-frequency eye tracking in your application? Then you MUST optimize your build to be as efficient as possible.

Unity + Meta All-in-One SDK + 72FPS Fixes