Search Issue Tracker
Active
Under Consideration for 6000.0.X
Votes
4
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
codesrc
Jul 28, 2024 04:28
It looks like the list of messages that come up is not complete. I authored a duplicate bug report for this issue. We also see a warning:
Your project uses a scriptable render pipeline. You can use Camera.stereoTargetEye only with the built-in renderer.
UnityEngine.Camera:set_stereoTargetEye (UnityEngine.StereoTargetEyeMask)
OVRCameraRig:EnsureGameObjectIntegrity () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRCameraRig.cs:603)
OVRCameraRig:Awake () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRCameraRig.cs:190)
UnityEditor.EditorApplication:Internal_RestoreLastOpenedScenes ()
We also see this error:
Saving Prefab to immutable folder is not allowed: Packages/com.meta.xr.sdk.interaction.ovr/Editor/Blocks/InteractableItems/Prefabs/[BB] Pokeable Plane.prefab
UnityEditor.AssetPostprocessingInternal:PostprocessAllAssets (string[],string[],string[],string[],string[],bool)
And this debug message:
Found IOVRSkeletonDataProvider reference in OVRHandPrefab due to unassigned field.
UnityEngine.Debug:Log (object)
OVRSkeleton:Awake () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/Util/OVRSkeleton.cs:341)
These errors appeared in 6000.0.7f1 and appear to be related to the Unity Oculus XR Plugin v 4.4.0.
Btw, thank you for following up about these issues as they are a showstopper for our project. Thanks again. -M