Search Issue Tracker
Won't Fix
Won't Fix in 1.6.X
Votes
1
Found in [Package]
1.6.1
1.6.2
Issue ID
ISXB-572
Regression
No
PreUpdate.NewInputUpdate increased by 0.01ms every Scene reload
Steps to reproduce:
1. Open the user's attached project "2022_3_LTS_SimpleVR.zip"
2. Open the "MostSimpleVRSetup" Scene
3. Open the Profiler and select in the Raw Hierarchy "PreUpdate.NewInputUpdate"
4. Configure the Input Manager Bindings under "Assets/InputSettings/Simple VR Setup.inputactions" for Quest 2
5. Add "Oculus Touch Controller Profiler" to OpenXR Interaction Profiles
6. Connect the Oculus link and enter Play Mode
7. Observe the Profiler and "PreUpdate.NewInputUpdate" increasing with 0.01ms, after 15 minutes it passes 1ms
Expected results: Warnings are added indicating that Inputs need to be cleaned up
Actual Results: PreUpdate.NewInputUpdate increased by 0.01ms every Scene reload
Reproducible in: Input System 1.6.1 (2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23)
Environment tested on: Windows 10
Notes:
-I could not observe the performance decrease when disabing OpenXR and entering Non-VR Play Mode
-In a larger project the increase is from 1ms to 5ms in 5 minutes according to the user
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.6.X):
There are no fixes planned for this Bug