Search Issue Tracker
Fixed in 2018.1.X
Votes
4
Found in
2017.2.0f3
Issue ID
958861
Regression
No
Input.GetJoystickNames returns controllers even when they're disconnected
Steps to reproduce:
1. Download and open the attached project
2. Make sure you have any controllers connected
3. Enter Playmode
4. Observe logs of connected controllers
5. Exit Playmode
6. Disconnect controllers
7. Enter Playmode
Expected result: console logs no controllers connected
Actual result: console logs any controllers that were connected before
Reproduced 5.5.0f1, 5.6.4f1*, 2017.1.2f1, 2017.2.0f3, 2017.3.0b4, 2018.2.0a3
Notes:
- The issue is more prominent with VR controllers - it logs the name of the one connected before. For regular controllers, it still returns Input.GetJoystickNames().length as the number connected originally
- 5.6 does not log names, but still incorrectly detects number of connected controllers
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
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
rmsuhail
Jul 18, 2018 07:28
still not solved on 2018.1.6f1