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
- "GUI Error: Invalid GUILayout state in ConsoleWindow view" and "NullReferenceException" errors are thrown when pinging GameObject in inactive Hierarchy from Console
- Crash on profiling::Dispatcher::AcquireFreeBuffer when the Editor's profiler session acquires a new dispatch buffer to emit UI events
- [XRIT] CurveVisualController causes "Invalid AABB" and "IsFinite(distanceForSort)" errors when startup endpoint equals origin
- Building with -nographics breaks VFX Graph Position (Depth) as an Operator
- MacOS server cannot find libMonoPosixHelper.dylib when calling GZipStream
Add comment