Search Issue Tracker
Fixed in 1.0.0
Votes
11
Found in [Package]
0.9.6
Issue ID
1188222
Regression
No
[Windows] HID input doesn't work in built scene for x86/32bit player
-e: the DS4 controller works well in the editor but not when built for windows standalone
--works well in editor and built on OSX, also works well with xbox360 controller
--stripping is disabled
--tested and fails Windows 2019.3 + 2020.1
-repro:
--open attached project
--plugin DS4 controller
--run GamepadVisualizer scene from samples
--notice: DS4 controller works
--build&run scene for windows standalone
--NOTICE: DS4 controller doesn't work
-workaround: switch build target from x86 to x86_64
-
kendallroth
Apr 30, 2020 03:14
Same thing here, excep the build works well for me with a PS4 controller but not a Logitech controller (set up as described here: https://forum.unity.com/threads/controller-wrongly-characterized-as-joystick-for-input-logitech-dual-action.879454/).
-
Fallout267
Apr 26, 2020 15:16
This didn't fix the problem for me. The build works fine with an Xbox controller but doesn't work with a ps4 controller despite working in unity and the build target being x82_64.
-
Peter77
Apr 08, 2020 12:26
Related forum thread:
https://forum.unity.com/threads/controller-bindings-not-working-after-build.752834/
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
- Application.systemLanguage returns "Unknown" when system language is set to Norwegian Bokmål/Nynorsk
- Project fails to load scene in WebGL due to lack of memory
- Particle System's Point Light flickers while Looping is on and Emission Rate over Time is set to 0 with Bursts Count set to 1
- Unity.IL2CPP.Building.BuilderFailedException when building on Android and using Regex in code
- [GLES2] [iOS] UnityGet2DClipping function returns wrong values
Resolution Note (fix version 1.0.0):
The fix is to the native runtime and not the Package itself.