HTML5 Gamepad - Logitech Driving Force GT - POV Hat Not Working
Reported by
eugene.b...@gmail.com,
Jun 14 2017
|
||||||||||||||||||
Issue descriptionChrome Version : 59.0.3071.86 URLs (if applicable) : http://html5gamepad.com Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: Firefox: OK (53.0.3) IE: What steps will reproduce the problem? (1) Connect Logitech Driving Force GT (2) Go to the referenced URL (3) Note the values returned for the POV hat (axis 9) What is the expected result? The POV hat axes (horizontal and vertical) should be assigned to separate axes, should return correct values, and be zero when idle. What happens instead? Both POV hat axes (horizontal and vertical) are assigned to axis 9. Axis 9 is returning 1.285714 when idle, 0.714286 for left, -0.428571 for right, -1 for up, and 0.142857 for down. Please provide any additional information below. Attach a screenshot if possible. Going to the same website on Firefox, the POV hat is not detected at all. This is a preferable workaround but ideally all inputs would be detected and usable. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jun 14 2017
I'm running Windows 8.1 I'll attach a series of images so I can describe what you're seeing: Dpad.jpg is my steering wheel controller highlighting the problematic control. Idle.jpg shows the value I get when I'm not even touching the controller. Left/Right/Up/Down shows the values I get when pressing those directions on the DPad.
,
Jun 14 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 15 2017
Logitech Driving Force GT game pad is not available with HYD Chrome-TE team to check this issue. so, requesting some one from MTV team to look in to it if in case this hardware is available. Thanks!
,
Sep 13 2017
Can you describe how the other buttons and axes are mapped? Here's my take on how it "should" be from the photos you posted: X O Square Triangle should be mapped as buttons 0-3 LB and RB should be buttons 4 and 5 L2 and R2 should be buttons 6 and 7 Select and Start should be buttons 8 and 9 D-pad should be buttons 12-15 Mode button should be button 16 The wheel axis should probably be mapped as axis 0 (left stick X) I don't know how the shifter, gas, brake, +, -, dial, or enter button should be mapped. Currently, all our gamepad mappings try to follow the Standard Gamepad spec: https://www.w3.org/TR/gamepad/#remapping We don't have a Standard Steering Wheel spec so even if we fix the mapping it's unlikely you'll get a good experience in games that expect a gamepad.
,
Sep 13 2017
Hi, As a matter of fact, I just mapped this wheel yesterday for Unity Rewired in both raw input and direct input. Here are the results: https://docs.google.com/spreadsheets/d/14m0azPut4B2tpYtgYA2J_sFIidziwos38gkww3H5Yzg/edit?usp=sharing
,
Sep 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 19
|
||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||
Comment 1 by hdodda@chromium.org
, Jun 14 2017Components: Blink>GamepadAPI
Labels: Needs-Feedback
1.4 MB
1.4 MB View Download