Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.3f1
2022.1.4f1
2022.2.0a16
2023.1.0a1
2023.2.0a1
Issue ID
UUM-1498
Regression
No
[Oculus] Application doesn't recover after device connection was aborted and re-established with Oculus/Air link
Reproduction steps:
1. Open the user's attached project "SSAOXR.zip"
2. Make sure Quest 1/2 is attached and Oculus Link established
3. Enter Play Mode of the "SSAO_Stereo_Issues" scene
4. Unplug Quest
5. Re-plug Quest and re-establish Oculus Link connection
Expected result: Application recovers after device connection was aborted and re-established
Actual result: Application doesn't recover after device connection was aborted and re-established
Reproduces on: 2019.4.32f1, 2020.3.24f1, 2021.2.4f1, 2022.2.0b1
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Our partners at Meta indicates this is the expected behavior when using Link
Resolution Note (2023.2.X):
Our partners at Meta indicates this is the expected behavior when using Link