Search Issue Tracker
Third Party Issue
Votes
1
Found in
2022.3.33f1
6000.0.6f1
Issue ID
UUM-92337
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"
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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Resolution Note:
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from a third-party library (PhysX), rather than Unity itself. The changes required inside PhysX to change this can and will ripple in unexpected ways and as such represent too high of a risk to do. We'll track this internally and verify during future updates of the library.
We will close this case as a third-party issue.
Cheers,
AlexRvn.
Resolution Note:
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from a third-party library (PhysX), rather than Unity itself. The changes required inside PhysX to change this can and will ripple in unexpected ways and as such represent too high of a risk to do. We'll track this internally and verify during future updates of the library.
We will close this case as a third-party issue.
Cheers,
AlexRvn.