Search Issue Tracker
Fixed in 1.0.0-preview.2
Votes
1
Found in [Package]
1.0.0-preview.2
Issue ID
1192379
Regression
No
[InputSystem] Custom devices not re-created after domain reload
1. Install CustomDevice sample.
2. Create an instance of the custom device using the Tools menu
3. Trigger a domain reload via a script change
4. Observe errors in console
Bit of a conundrum. Problem is that we trigger an initial update during system initialization through InputSystem.RunInitialUpdate. We do this so that MonoBehaviour.Start methods have devices available to them.
However, when system initialization is triggered by one specific third-party InputSystem.RegisterXXX call and there's another InputSystem.RegisterLayout call waiting, then any device depending on the RegisterLayout call will cause an error as the layout is not yet available.
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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note (fix version 1.0.0-preview.2):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/931