Search Issue Tracker
By Design
By Design in 2.0.X
Votes
0
Found in [Package]
2.0.0-pre.11
Issue ID
AVPB-777
Regression
No
[VisionOS] UI in the Metal sample for Apple Vision Pro does not work
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the Build Profiles window (File > Build Profiles)
3. Unselect all except the second Scene (InputSystem UI)
4. Build the project on “visionOS” platform
5. Run the build on an Apple Vision Pro device or visionOS simulator
6. Interact with the UI
Expected result: UI is not interactable
Actual result: UI behaves as expected, elements are interactable
Reproducible with: 2.0.0-pre.11 (6000.0.16f1)
Couldn’t test with: 2.0.0-pre.3 (6000.0.16f1), 1.3.1 (2022.3.44f1)
Reproducible on: Hybrid (Metal and RealityKit) on visionOS 2.0 Simulator - built using M1 Max MacOS 14.5
Not reproducible on: No other environment tested
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Please feel free to re-open this is the solution I described in my prior two comments doesn't work for you. We've made a note about this to improve our documentation and samples for Hybrid mode so the solution is more clear in the future. Thanks again for reaching out and helping us improve our documentation and samples.
Resolution Note (2.0.X):
Please feel free to re-open this is the solution I described in my prior two comments doesn't work for you. We've made a note about this to improve our documentation and samples for Hybrid mode so the solution is more clear in the future. Thanks again for reaching out and helping us improve our documentation and samples.