Search Issue Tracker
Fixed in 0.2.0-preview
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1093777
Regression
No
[Performance] Devices created very late in initialization
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/245
After the domain reload refactor, devices are not initialized and added until the first update loop.
This means that any initialization code in Monobehaviours (Awake, Start, OnEnable) cannot get access to any devices like the keyboard or mouse until after the first update has passed, which makes for very awkward initialization.
mdsitton commented 20 days ago
I'm seeing this issue on Mac in the editor but not on Windows.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment