Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot map controller input to different values #30

Open
raidancampbell opened this issue Apr 6, 2016 · 1 comment
Open

Cannot map controller input to different values #30

raidancampbell opened this issue Apr 6, 2016 · 1 comment

Comments

@raidancampbell
Copy link
Member

Gamepad input mappings are wonky by default, and currently must be fixed on the host computer

@prolitaaron
Copy link

prolitaaron commented Dec 6, 2016

I really hope this gets pursued by somebody; I'd do it myself if I had the knowledge. Being able to map controller inputs is make-or-break for using this application at all for a lot of people, it's conceptually sort of a core functionality type of thing.

SPECIFICALLY on Chromebooks, where there is no other way to manage input mapping. This would make Chromebooks the ultimate gaming laptop (with a powerful desktop on the same network, of course), based on their super low price for the hardware and being based entirely around Chrome anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants