Search Issue Tracker
Active
Under Consideration for 1.11.X
Votes
0
Found in [Package]
1.11.0
Issue ID
ISXB-1187
Regression
No
[Quest] InputUpload slows down performance when the Hands XR sample is built on Quest
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/XR Hands/1.3.0/HandVisualizer/HandVisualizer.unity” Scene
3. Open Build Settings (File > Build Settings)
4. Switch to Android Platform
5. Select “Development Build“
6. Select “Autoconnect Profiler”
7. Build and Run on Quest 2
8. Open Profile Analyzer
9. Click “Pull Data“
10. In the “Name Filter“ field enter “Input”
11. Find “InputUpdate”
12. Observe Min and Max values
Expected result: Both values are small indicating good performance
Actual result: Min and Max values are high indicating poor performance
Reproducible with: 1.9.0 (6000.0.21f1), 1.11.0 (2021.3.44f1, 2022.3.47f1, 6000.0.21f1)
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment