Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
1.1.4
Issue ID
AVPB-459
Regression
No
[VisionOS] Certain number of cubes cause FPS to drop on Vision Pro
Reproduction steps:
1. Open the attached “Repro“ project
2. Build the project on “visionOS” platform (File > Build Settings > visionOS > Build)
3. Run the project on Apple Vision Pro device
4. Connect Unity Profiler
5. Instantiate 2500 Cubes using the buttons on the screen
6. Observe Unity Profiler
Expected result: No sudden FPS drops are present
Actual result: After a certain point FPS tanks from 90 to 45
Reproducible with: 1.1.4 (2022.3.20f1)
Reproducible on: MR on Apple Vision Pro - built using M2 Pro macOS 14.2.1 (user’s platform)
Not reproducible on: MR on visionOS 1.1 Simulator - built using M1 Max macOS 14.4.1
Note: This issue was not successfully reproduced by CQA, thus submitted without local reproduction
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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Resolution Note:
This reproduces in a simple non-Unity visionOS app, so we are taking it to be an Apple issue. Whether it's really a bug is debatable: some level of scene complexity will inevitably cause performance to degrade, and doing so at integer divisors of the base FPS (90 to 45) is a conscious decision on Apple's part to ensure update smoothness. Nevertheless, we passed this along to Apple as FB14859759 (along with a non-Unity Xcode project demonstrating the issue).