Search Issue Tracker
Active
Under Consideration for 1.8.X
Votes
0
Found in [Package]
1.8.2
Issue ID
ISXB-899
Regression
No
Poor CPU and GPU performance is observed when a PlayerInput component with notification behavior set to "Invoke Unity Events" is displayed in the Inspector
How to reproduce:
1. Open the attached “inspector_input_issue” project
2. Open the “SampleScene”
3. Select the “Main Camera” in the Hierarchy window
4. Open Task Manager and navigate to the Performance tab
5. Under the CPU tab, right-click and select “Change graph to → Logical processors”
6. Take note of the usage of each core
7. In the Inspector, change the Behavior field of the PlayerInput component to “Invoke Unity Events”
8. Observe the result in Task Manager
Expected result: The performance of each core is unaffected
Actual result: The utilization of one or more cores is significantly increased
Reproducible in: 1.7.0 (2021.3.39f1, 2022.3.31f1), 1.8.2 (2021.3.39f1, 2022.3.31f1, 6000.0.4f1)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: The GPU usage is also increased when switching the PlayerInput Behavior field, observed under the “3D” section of the GPU tab in Task Manager
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "ArgumentException" errors thrown when enabling “Screenshot Camera 6” GameObject in High Definition 3D Sample Template
- Inaccurate collision detection in OnTriggerStay when alternating isKinematic and Collision Detection modes in FixedUpdate
- [TMP] Usability - Font Styles button icons should display text effect
- Shader warning in 'Hidden/Universal Render Pipeline/LensFlareDataDriven' is thrown after building Universal 3D Template Project
- [URP] "ShaderData" namespace error is thrown when building a project with "URP RenderGraph Samples"
Add comment