New issue
Advanced search Search tips

Issue 664030 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Nov 2016
Cc:
bajones@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

PS4 slim gamepads aren't mapped correctly

Reported by aicomman...@gmail.com, Nov 10 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.90 Safari/537.36

Steps to reproduce the problem:
1. Connect a PS4 Slim gamepad (054c:09cc)
2. Go to html5gamepad.com
3. Press buttons and move analog sticks

What is the expected behavior?
The buttons and analog sticks should be mapped correctly.

What went wrong?
The mapping is not correct. The original PS4 controller is mapped correctly, but the newer one that shipped with the PS4 Slim is not.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 54.0.2840.90  Channel: stable
OS Version: Fedora 24
Flash Version: Shockwave Flash 23.0 r0
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 10 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1018bb702883f08b560a30c5be2acc9aa9c85a6e

commit 1018bb702883f08b560a30c5be2acc9aa9c85a6e
Author: aicommander <aicommander@gmail.com>
Date: Thu Nov 10 09:08:16 2016

Add mapping entry for newer DualShock 4 model

This gamepad shipped with the PlayStation 4 Slim. It has the same
mapping as the original DualShock 4 but a different PID.

BUG= 664030 
TEST=http://html5gamepad.com

Review-Url: https://codereview.chromium.org/2490103002
Cr-Commit-Position: refs/heads/master@{#431216}

[modify] https://crrev.com/1018bb702883f08b560a30c5be2acc9aa9c85a6e/device/gamepad/gamepad_standard_mappings_linux.cc
[modify] https://crrev.com/1018bb702883f08b560a30c5be2acc9aa9c85a6e/device/gamepad/gamepad_standard_mappings_mac.mm
[modify] https://crrev.com/1018bb702883f08b560a30c5be2acc9aa9c85a6e/device/gamepad/gamepad_standard_mappings_win.cc

Comment 2 by dk...@chromium.org, Nov 14 2016

Cc: bajones@chromium.org
+bajones

Comment 3 by bajones@chromium.org, Nov 14 2016

Status: Fixed (was: Unconfirmed)
Should be fixed with the commit listed above.
►

Sign in to add a comment