Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.15f1
2021.1
2021.2
Issue ID
1378054
Regression
No
Controller buttons mapped incorrectly when project is built for WebGL platform
Reproduction steps:
1. Open the "Hangar" Scene in the project attached by the user
2. Connect the DualShock 4 controller
3. Enter the Play mode and press the Circle button on the controller, notice that Console shows dialog log "Button 2 = Circle"
4. In the Build Settings make sure that Scenes/Hangar is added in the Scenes in Build and Platform is set to the WebGL
5. Build and Run
6. Press Shift+Ctrl+J to open the Console in the browser
7. Press the Circle button on the controller
8. Observe the Console
Expected result: Console shows dialog log "Button 2 = Circle"
Actual result: Console shows dialog log "Button 1 = X"
Reproducible with: 2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.2f1
Could not test with: 2022.1.0a15 (Building crashes)
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
- [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
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2022.2):
The mappings follow the W3 spec's definition of standard gamepad mapping. While it is indeed inconsistent with the other platforms, since the issue is only in the old input system, and changing it will break existing users' project, we won't change it, but will communicate this information either in the docs or in a forum post.