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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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).