Search Issue Tracker
Fixed in 1.2.0
Votes
0
Found in [Package]
Issue ID
1362733
Regression
No
Input Package deserializing JSON multiple times when entering/exiting playmode
Using Unity 2022.1.0a7
1. Import this project: https://github.cds.internal.unity3d.com/unity/se.perf.lostcrypt
2. Run the "EnterExitPlayMode Test" and profile (ideally using Superluminal)
3. Notice that UnityEngine.InputSystem.InputManager.AddAvailableDevicesThatAreNowRecognized shows up
4. After digging into it, it appears the same JSON is being parsed twice, looking at HID.cs
One idea:
It looks like one optimization could be to hash that utf8 string in HID.cs and store the hash, such that if it doesn't change the previous descriptorJSON result could be used, maybe, instead of re-parsing the JSON?
This should help reduce the time it takes to enter playmode when the Input package is installed in a package.
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.2.0):
Fixed in: 1.2.0