ALAS! I AM NOT DEAD! (only taking some time to sort life out)
Ok, so, updates: I've been pretty much focusing on school for the past 6 months and whatnot, and somewhat enjoying my summertime
I've also finished an updated XBox controller layout (based on the XBox One's controller) and currently working on a Gameboy Advanced skin. You can see them below:
Now, Q&A Time:
Please add support for Generic USB Joystick (Vendor: 0079 Product: 0006) PS2 USB controller.
http://html5gamepad.com/ has no issues detecting inputs, but
http://mrmcpowned.com/gamepad/ says There are currently no gamepads connected. Press any button to enable... in all browsers.
I'll need to look into fixing up the tester and gamepad JS that I've got modified for this project. The JS on HTML5 Gamepad's site is using AngularJS (an HTML/javascript library) where as mine is just barebones javascript utilizing the gamepad API. If anything I might look into using Angular instead of the current solution, but I'll have to look into it.
I would donate to get you to put out this update :D
Thanks for the kind words :D I should be able to get the skins up in a week or so.
This is the best Xinput View I've ever used!
I only wish I could download it... I think it would be even more amazing if I could have an EXE file of this :D
I might look into just packaging the whole thing as a zip file so all you have to do is open up the page in a browser. Wrapping the app in an exe seems counter productive since you'd have to chroma-key out the background instead of just having it transparent,
like how you currently can!
Love your work on this Mr McPowned, I hope the project isn't dead. I'm very excited about the Arcade Stick layout. Would you consider to do a different buttons layout?
4, 6 and 8 buttons layout, like the arcade cabinets or fightsticks. I would love to see something like this:
The stick and the buttons, nothing more, then the streamers can put it above an image of an arcade control panel. That would be awesome.
I will totally donate if this will happen!
Thank you, you're awesome.
(Sorry for my english)
Hi! Thanks for the kind words :D As for the fightstick setup, I've been thinking how to do this with a minimal amount of jaavscript being used. Basically, I set up this whole app as a sort of testament to what can be done with CSS, Images, and a minimal amount of javascript (minues the main JS used to read and write the gamepad inputs). The fightstick is where things get tricky with the way the dpad is currently set up on controller and how the knob works on a fightstick, and trign to interpret corner movements visually, like whenever the knob on the image above moves to the top right and top left. I haven't abandoned the idea, simply trying to find a way to do it in the best way possible :)
Hi there... I am very interested in this idea ... but I am having trouble getting it working. ....
1) The app seams to work fine on my Logitech GamePad controller. It is a F710... works fine...
2) I also own a Madcatz TE Ps3 Arcade Stick. I have tried it in firefox, IE, Chrome and the CLRbrowser in OBS itself. The problem is that it seams to recognize the device, but none of the buttons trigger. Like when I press the buttons the gamepad image pops up but none of the buttons work.
The buttons and everything works fine here :
http://html5gamepad.com/
3) Also if I can get it working is there a way to change the images?
Is this your app?
http://youtu.be/CfWm6DyGGmw?t=15
Also there was talk of a app called "xinput viewer" but all the links to it are broken.. dose anyone have that I can try?
Again, the answer here is similar to the first reply I made: I gotta update the thing. I'm also unsure as to what you mean by "change the images". Could you please elaborate? Also, the display used in that video isn't from my app, sorry :(
I have the same issue. This was working great until I got a Blue Yeti and now it can't catch inputs anymore
So basically the issue with this is with the gamepad API itself. For some reason or another, chrome picks up the Yeti as a gamepad sometimes and that ends up screwing the whole thing up. I, too, have a Yeti and it's a pain in the ass to try and solve. I've been trying to see if I can get the code to ignore the Yeti, since it's given a name but haven't had any luck so far. I've actually
sent in a bug report to the chrome team, but they haven't done anything about it. Maybe if more people sent them bug reports on this very issue they might look into it, but even then I'm not sure.