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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (fix version 1.0.0-preview.2):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/931