Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2023.1.0b8
Issue ID
UUM-32288
Regression
No
The Profiler window shows incorrect data when enabling "Deep Profile" and GO with the New Input System component
Reproduction steps:
1. Open the attached “Test Project” Project
2. Open “SampleScene” Scene
3. Open Window > Analysis > Profiler Window
4. Enabled the “Deep Profile” option
5. Enter the Play Mode
6. In the Profiler window click any frame in the “CPU Usage” category
7. Observe the “Hierarchy” tab
Expected result: The “Hierarchy” tab shows all tasks
Actual result: The “Hierarchy” tab shows only the “PreUpdate.NewInputUpdate” task
Reproducible with: 2023.1.0b8
Reproducible on: Windows 10
Notes:
- I was not able to reproduce this issue
- When disabling “InputSystem” GO the issue no longer appears
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:
We have been unable to reproduce this issue, we believe that the issue may have been fixed in the latest Input System so suggest update that to the latest version.
Resolution Note (2023.1.X):
We have been unable to reproduce this issue, we believe that the issue may have been fixed in the latest Input System so suggest update that to the latest version.