Wii U USB GameCube Adapter returns null or NaN axes
Reported by
yonicstu...@gmail.com,
Nov 24 2016
|
|||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Steps to reproduce the problem:
1. Connect a Wii U USB GameCube Adapter to the computer.
2. Connect a GameCube controller in the adapter's port 1.
3. Download Wii U USB GameCube Driver. If required, download as well Zading and vJoy.
4. Install Wii U USB GameCube Driver.
a. When Zadig is prompted, replace original driver with WinUSB.
b. When vJoy is promopted, follow vJoy's installation process with the default configuration. If vJoy installs succesfully, skip to step 5.
c. If vJoy installation fails, run vJoy independent installer again.
d. If the failure persists, delete folder %userprofile%/usb_driver and run the installer again. Repeat d. until installation succeeds.
5. Run Wii U USB GameCube Driver/adapter. When prompted, press Start.
6. Run Chromium or Chrome dev channel, and go to https://ericlathrop.github.io/html5-gamepad/
7. Press any of the GameCube controller buttons.
What is the expected behavior?
In the JSON generated, the "axes" should return numerical values ranging from -1 to 1. This output has been reported on Firefox.
What went wrong?
The "axes" values are 'null'.
Did this work before? No
Does this work in other browsers? Yes
Chrome version: 56.0.2924.3 (Build oficial) dev (64 bits) Channel: dev
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
,
Nov 29 2016
,
Dec 8 2016
,
Jan 9 2017
bajones@, skonig@, can one of you take a look at this issue?
,
Feb 6 2017
Assigning to bajones to confirm since this bug isn't getting traction. @Brandon - feel free to reassign if someone else is a better fit! I just happen to know you've worked on GamePad :)
,
Feb 27 2017
Ping to see if one of you has ideas here. dougt@, I believe the Device API team now owns triage for GamepadAPI, is that correct? Could you help triage/route this appropriately?
,
Apr 5 2017
,
Apr 11 2018
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
,
Apr 17 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by yonicstu...@gmail.com
, Nov 24 201643.3 KB
43.3 KB View Download