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

Dinput 360 controller not detected by current version. #24

Open
LuisCondeVela opened this issue Sep 30, 2016 · 4 comments
Open

Dinput 360 controller not detected by current version. #24

LuisCondeVela opened this issue Sep 30, 2016 · 4 comments

Comments

@LuisCondeVela
Copy link

I trying to set it with a Dinput 360 controller, but its just not being detected, XOutput is just gray with the exclusivity checkbox and the Star at the end and nothing else.

the older release 0.1 did detected it and even map it automatically, but its just keeps crashing on Start.

Windows 10 64 bits, updated to date, i did installed ScpDriver and SlimDX runtime. Runned all as Administrator.

Thank you and good job.

@ericlbarrett
Copy link
Owner

Are you using a xbox 360 controller? XInput ignores 360 controllers. Though I don't know why v0.1 would detect it.

@LuisCondeVela
Copy link
Author

LuisCondeVela commented Sep 30, 2016

yes i have a 360 controller in Direct Input mode with custom drivers, XBCD, i use them so i can set dead zones and move the trigger to separate axis.

well, i guess ill look for other solutions to get it to work with UWP games. Thanks

@joao678
Copy link

joao678 commented Mar 19, 2017

I managed to fix this. Check this out!
https://github.com/joao678/XOutput-XBCD/releases/tag/v0.12

@Squall-Leonhart
Copy link

im curious what you fixed, since 0.11 works fine on xbcd o.O

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

No branches or pull requests

4 participants