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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment