Search Issue Tracker
Fixed in 1.1-preview.2
Votes
1
Found in [Package]
1.0.0
Issue ID
1251724
Regression
No
The Input System does not get re-enabled when a PlayMode input test is interrupted
How to reproduce:
1. Open the user-supplied project called "TestProject1251724.zip"
2. Open the "TestScene" Scene
3. Open Windows > Analysis > Input Debugger and observe the Devices
4. Open the Test Runner window, select "PlayMode" and press "Run All"
5. Before the test is finished, exit Play Mode
6. Enter Play Mode again and observe the Input Debug window
Expected result: the Input System is enabled and the input devices are recognized
Actual result: the Input System is disabled, and after re-entering Play mode, the input devices are not detected ("Devices (0)")
Reproducible with: 2019.3.16f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a15
Could not test with: 2017.4, 2018.4 due to the Input System package not being available
Notes:
1. After interrupting the test, the button in the Game view cannot be clicked after re-entering Play mode.
2. An error saying "A Native Collection has not been disposed, resulting in a memory leak." may occur in the Console after re-entering Play mode.
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
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
Resolution Note (fix version 1.1-preview.2):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1223.
Fixed in Input System preview.2 - 1.1.0 (Verified with Unity 2019.4.0f1)