Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
1
Found in [Package]
1.10.0
Issue ID
ISXB-573
Regression
No
Severe performance degradation when using multiple Input Action mappings
How to reproduce:
1. Open the “Input_Action_Amount_Performace“ project
2. Open the “SampleScene”
3. Open the Profiler (Window > Analysis > Profiler)
4. Enter Play Mode and while moving the mouse in Game view observe the Profiler
5. Exit Play Mode then in Hierarchy disable the “BobSpawner” GameObject
6. In Hierarchy enable the “FredSpawner” GameObject and Enter Play Mode
7. While moving the mouse in Game view observe the Profiler
Expected result: there is no major performance difference between the two GameObjects
Actual result: “FredSpawner” GameObject causes major performance degradation
Reproduced with: 1.1.0-preview.1 (2023.2.0a22), 1.6.1 (2021.3.28f1, 2022.3.4f1, 2023.1.4f1, 2023.2.0a22)
Could not test with: 1.0.0, 1.0.2 (2023.2.0a22) (Could not resolve scripting errors)
Reproduced on: Windows 11
Note: Also reproducible in Player → enable “Development Build” and “Autoconnect Profiler” (File > Build Settings)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
FIX: Fixed a performance issue with many objects using multiple action maps [ISXB-573](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-573).