Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Possible Upcoming Mumble Compatibility Issue with XBox One Controller on Windows #2104
I run the Windows 10 Fast Ring previews, and there's a potential upcoming compatibility issue between Mumble and the newer Windows drivers for the XBox One Controller(driver information at bottom of post). With the next major non-preview build landing some time this spring(probably) it may be worthwhile to identify this issue beforehand.
Have tested with Win32 1.2 latest, and Win64 1.3 snapshot latest. Both show this issue.
Have confirmed that CPU usage correctly resolves itself both if you disconnect the gamepad while mumble is running; and also returns if you reconnect the gamepad while mumble is running.
Improper input mapping does seem to require an entire Mumble restart - disconnecting mid-session will not resolve the issue.
Mumble started without the gamepad connected WILL exit properly if the gamepad is added mid-session.
There are 2 drivers available to me:
We added XInput support in some of the more recent snapshots. It's possible the driver latest insider builds doesn't work too well with DirectInput. Right now, in 1.3.0, we drive the controller in both XInput and DirectInput, at the same time.
I should try to land the code that blacklists Xbox controllers from DirectInput -- such that it is only opened via XInput -- and see if that helps you...
This was referenced
Mar 3, 2016
referenced this issue
Mar 4, 2016
Now in 1.2.x snapshot form:
I hope to release this as-is as 1.2.15, if nothing goes wrong. Feel free to test.