Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.3f1
Issue ID
949247
Regression
No
[UWP] Input.GetJoystickNames() empty on Start in UWP builds
To reproduce:
1. Open the attached project
2. Connect at least one Controller to the PC the issue is being tested on
3. Launch "test.scene" scene in the editor to make sure the controller is detected
4. Make a UWP build and launch it
Result: Connected controllers are not detected using Input.GetJoystickNames() as they are in the editor
NOTE:
Having Input.GetJoystickNames() in Update() eventually finds the connected controllers.You can test this by setting CheckInUpdate field in "script" script to true
Reproduced on: 5.6.3p3, 2017.1.1p1, 2017.2.0b11, 2017.3.0a7 with .NET and IL2CPP scripting backends
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
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Resolution Note (2018.1.X):
This issue is due to a race-condition between the Windows device enumerator and the GetJoystickNames() method. That is, retrieving device names before enumeration completes returns an incomplete list, but there isn't a good solution to fix it for the Unity API.