Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
Issue ID
1318446
Regression
No
New Input system consumes time on main thread when old input system is selected in Player Settings & the package is not installe
An ES customer's project has been set to use "Input Manager (Old)" in the player settings. The new Input System package is not installed.
While profiling I noticed that the FixedUpdate.NewInputFixedUpdate, FrameEvents.NewInputBeforeRenderUpdate and PreUpdate.NewInputUpdate profile markers sometimes take a non-zero amount of time (0.06, 0.1 & 0.26ms respectively) on the main thread.
This appears to be consistently reproducible across builds, though it is not clear if this is due to thread preemption - the timings are quite consistent however across a number of profile captures, so this seems unlikely.
(Attached a deep profiling capture as requested by Dmytro)
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2019.4.19f1):
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.