Search Issue Tracker

Active

Votes

1

Found in

6000.0.0b16

6000.0.1f1

Issue ID

UUM-71393

Regression

Yes

[XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher

--

-

Steps to reproduce:
1. Download the attached user's project "v65tc2UPMf1.zip"
2. Open "Assets/Samples/Meta XR Core SDK/65.0.0/Sample Scenes/ControllerModels.unity"
3. Connect Oculus link with Quest 2/3
4. Make sure OculusXR plugin is enabled
5. Enter Play Mode

Expected Results: Input is registered and headset view is not headlocked after entering Play Mode
Actual Results: Scene is rendered in the headset with the default view headlocked and no input

Reproducible with: 6000.0.0b16, 6000.0.1f1
Not reproducible with: 2021.3.38f1, 2022.3.28f1, 6000.0.0b15

Reproducible on these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12

Testing Environment: Windows 11
Not reproducible on: No other environment tested

Notes:
-Reproducible with Meta SDK v64.0 and v65.0
-Reproducible on a new project
-Console is spammed with these messages:
Unable to process a controller whose SampleRateHz is 0 now.
UnityEngine.Debug:Log (object)
OVRHaptics/OVRHapticsOutput:Process () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRHaptics.cs:176)
OVRHaptics:Process () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRHaptics.cs:393)
OVRManager:LateUpdate () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRManager.cs:3037)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.