Search Issue Tracker
Active
Under Consideration for 2.0.X
Votes
0
Found in [Package]
2.0.1
Issue ID
MOXRB-92
Regression
No
Raycasts against ARMesh flicker on Quest 3
Steps to reproduce:
1. Download the attached user's project "Quest-Raycast-Bug.zip"
2. Switch to Android
3. Build for Quest 3
4. Enable Spatial Data Sharing via prompted dialog
5. Observe interactor + reticle flickers when moved over the spatial mesh
Expected Results: Raycasts against ARMesh does not flicker on Quest 3
Actual Results: Raycasts against ARMesh flicker on Quest 3
Reproducible on: ARFoundation 5.1.4 (2022.3.33f1), ARFoundation 6.0.2 (6000.0.6f1)
Could not test on 2021.3.39f1 due to project errors after downgrading
Reproducible with these devices:
VLNQA00609, Oculus Quest 3 (Quest 3), Android 12, CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
Could not test on Quest 2 due to application freezing on startup
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-Video of the issue is attached "QUEST-ISSUE-VIDEO-RECORDING.mp4"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Changing the Visual Element size moves it when two visual elements are close to each other
- Open Reference for Default Style Sheet asset redirects to missing page
- Undoing changes to Default Style Sheet does not show change until editor refresh
- TextMeshPro Caret has an active raycast when TMP_InputField is non-interactable
- Shadows do not smoothly fade in when transitioning between real-time shadows and baked distance shadows
Add comment