Search Issue Tracker
Fixed
Fixed in 1.13.1, 2.2.3-preview.1, 3.2.3
Votes
0
Found in [Package]
1.12.0
2.0.0-preview.5
3.0.1
Issue ID
OXPB-2
Regression
No
[Oculus] Application does not recover when reconnecting and re-enabling Oculus Link
Reproduction steps:
1. Open the user's attached project "VRTest3b.zip"
2. Build Standalone Player
3. Connect Quest 2 via USB and Enable Oculus Link when the popup appears on the headset
4. Run the Standalone Player
5. Disconnect the USB cable
6. Reconnect the USB cable and Enable Oculus Link when the popup appears on the headset
7. Note that the application does not resume (black screen)
Expected result: Application does resume when reconnecting and enabling Oculus Link
Actual result: Application does not resume when reconnecting and enabling Oculus Link (See attached Unity2020-3-23-Fails.mp4)
Reproduces on: 2019.4.38f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
Does not reproduce on: 2018.4.36f1
Notes:
-Issue reproduces in the Editor as well when entering Play Mode with Oculus link connected
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2.2.3-preview.1):
Backport of https://github.cds.internal.unity3d.com/raw/unity/xr.sdk.oculus/pull/490