Skip to main content
LeeHall02
New Participant
March 11, 2024
Solved

Meta Quest 3 incorrectly detected as Meta Quest Pro

When using Meta XR Core SDK v62 on Unity 2022.3.20f1 Meta Quest 3 standalone it gets detected as a Meta Meta_Quest_Pro by OVRPlugin.GetSystemHeadsetType 
Running using AirLink through Unity editor on Windows Meta_Link_Quest_3

korinVR
korinVRAnswer
Honored Contributor
March 11, 2024

Have you updated to Oculus XR Plugin 4.1.1 or higher and enabled Quest 3 in OVR Manager?
If not, Quest 3 will return Meta_Quest_Pro.

 

Katsuomi Kobayashi ( @korinVR ) at FrameSynthesis Inc.
View in thread

2 replies

korinVR
korinVRAnswer
Honored Contributor
March 11, 2024

Have you updated to Oculus XR Plugin 4.1.1 or higher and enabled Quest 3 in OVR Manager?
If not, Quest 3 will return Meta_Quest_Pro.

 

Katsuomi Kobayashi ( @korinVR ) at FrameSynthesis Inc.
    LeeHall02Author
    New Participant
    March 11, 2024

    Thanks for your reply. I think I see where I was going wrong, I was just using OVRPlugin.GetSystemHeadsetType() to work around a bug with Unity's InputDevices.GetDevices returning the wrong device name for Quest 2 and Quest 3 but was not using the OVR Manager or any of the other OVR stuff. I was just selecting the Quest 2, Quest 3 and Quest Pro as target devices in the XR plugin management for Oculus
    Adding OVR Manager to my test project does seem to resolve the issue.

    Terms & ConditionsAccessibility statement