Search Issue Tracker
Won't Fix
Won't Fix in 1.11.X
Votes
0
Found in [Package]
1.11.0
Issue ID
ISXB-1187
Regression
No
[Quest] InputUpdate 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
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
We have reproduced and profiled the issue, but we did not identified any immediate improvements we could be making, there numerous small inefficiencies accumulating over time. That being said we do have internal initiatives that will over time improve the performance of the system, but those fall outside the scope of a bug fix.
Resolution Note (1.11.X):
We have reproduced and profiled the issue, but we did not identified any immediate improvements we could be making, there numerous small inefficiencies accumulating over time. That being said we do have internal initiatives that will over time improve the performance of the system, but those fall outside the scope of a bug fix.