Search Issue Tracker
By Design
By Design in 2.2.X
Votes
11
Found in [Package]
2.2.4
Issue ID
XRVOSB-85
Regression
No
Player framerate performance degrades when Spatial and Plane Meshes are updated
How to reproduce:
1. Open the attached “IN-98419.zip” Project
2. Build and Run on a VisionOS Device
3. Observe the FPS in the custom UI Window shown in the Player
4. Spawn multiple GameObjects in the Player with the Pinch Gesture
5. Move the Headset around and observe the FPS in the custom UI Window in the Player
Expected result: Stable framerate performance around ~90fps
Actual result: Erratic framerate, drops to ~70fps very rarely goes lower
Reproducible with: 2.2.4 (6000.0.49f1, 6000.1.4f1)
Couldn’t test with:
1.3.12 (2022.3.62f1) - Compilation errors related to unsupported methods after downgrading
2.2.4 (6000.2.0b2) - IL2CPP Compilation error during Build Time
Testing environment: macOS 15.3.2 (M3)
Reproducible on: Apple Vision Pro 2.5
Notes:
- User has noted that the issue happens due to “Spatial Meshes” or “AR Planes” being updated every frame
- The Project is based on the Unity Polyspatial Sample, specifically Mixed Reality demo
Comments (1)
-
daveXR
May 25, 2025 21:54
It's super important to get this fixed, as the frequent frame drops are quite distracting. Additionally, it interferes with hand tracking, causing problems when trying to toss virtual objects.
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
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
- The cogwheel button in the Build History window gets distorted when the Build History window is resized or options are ticked in the toolbar
- Unity Hub (Arm64) fails to start when installed on Windows 11 (Arm64)
Resolution Note:
I checked out the users project, observed the results. Then upgraded to our latest packages and observed the noticeable improvement in performance.
A fellow developer pointed me to this thread:
https://discussions.unity.com/t/visionpro-framerate-hitch-every-time-spatial-mesh-updated/1556394/16
Which references the exact same video from this bug.
At the end of the thread the user that logged the bug reported being happy with the results starting with our 2.3.1 version of our packages:
User reported "Oh my gosh, thank you thank you thank you!! To you and the team – it’s running SO much smoother now!!!"
I think we can close this one.
Resolution Note (2.2.X):
I checked out the users project, observed the results. Then upgraded to our latest packages and observed the noticeable improvement in performance.
A fellow developer pointed me to this thread:
https://discussions.unity.com/t/visionpro-framerate-hitch-every-time-spatial-mesh-updated/1556394/16
Which references the exact same video from this bug.
At the end of the thread the user that logged the bug reported being happy with the results starting with our 2.3.1 version of our packages:
User reported "Oh my gosh, thank you thank you thank you!! To you and the team – it’s running SO much smoother now!!!"
I think we can close this one.
Resolution Note:
Fixed in PolySpatial visionOS 2.3.1