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
- ScreenCapture.CaptureScreenshot renders blocky artifacts when Super Size is greater than 1
- Multiplication and division operators do not work with Vector3 and Vector4 types when multiplied by the same type
- Lens Flare VFX is duplicated when observed through a VR Headset
- Random values are showing in the Transform Position when snapping the object to the grid after moving it slightly
- Leading bracket is left behind on the previous line when text wraps in TextMeshPro
Resolution Note (fix version 1.0.0-preview.2):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/931