Search Issue Tracker
By Design
Votes
0
Found in
5.2.2p1
Issue ID
744247
Regression
No
[UWP] Standalone Input Module doesn't get joystick input until mouse is moved
Repro steps:
1. Open project "controllers.zip" and build to Windows 10 Universal XAML on Windows 10 PC.
2. Plug in Xbox controller.
3. Build and run generated solution.
4. Try to move up/down left controller axis. UI elements are not being selected.
5. Move mouse over the screen (don't need to click anything) and try controller again - now UI elements are being selected.
Workaround: move the mouse, because UWP detects mouse presence on first mouse event.
Comments (2)
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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
robert-ferrese
May 15, 2017 02:11
Im surprised that unity marked this as ByDesign without a good workaround. Here is the fix:
Check the "Force Module Active" checkbox. This will force the input to be enabled even when mouse isnt present. Hope this helps with your xbox development :)
Katastrophe1986
Apr 22, 2016 03:07
This workaround doesn't work when you are making a UWP app for Xbox One.