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
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment