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

Possible Upcoming Mumble Compatibility Issue with XBox One Controller on Windows #2104

Closed
laenas opened this Issue Feb 6, 2016 · 9 comments

Comments

Projects
None yet
4 participants
@laenas

laenas commented Feb 6, 2016

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.

  1. Mumble consistently chews up an entire logical core in this situation, driving CPU usage sky-high.
  2. Mumble (possibly due to CPU usage?) does not properly identify upper mouse button inputs for PTT(or even configuring PTT) and instead seems to read them as Mouse1.
    2a. This is identifiable by the fact that you'll get 'drag and drop' behavior in a channel list, despite the PTT key being something like Mouse4, and not being easily reproduceable.
  3. Mumble does not exist properly, closing the interface(and confirming you want Mumble to close) will leave an orphan process chewing up that entire logical core.
  4. This does not appear to be an issue with other VOIP solutions such as TS3, so it seems specific to something Mumble is doing.

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.
Mumble started with the gamepad connected will not exit properly until the gamepad is disconnected.

There are 2 drivers available to me:
v10.0.14257.1000 - dated 2016-01-31: Causes issues.
v6.2.11059 - dated 2014-05-26: Works as intended with no side effects.

@mkrautz

This comment has been minimized.

Show comment
Hide comment
@mkrautz

mkrautz Feb 6, 2016

Member

Thanks!

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...

Member

mkrautz commented Feb 6, 2016

Thanks!

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...

@laenas

This comment has been minimized.

Show comment
Hide comment
@laenas

laenas Feb 6, 2016

Let me know if there's any additional debug info that would be helpful to you in hunting this down.

laenas commented Feb 6, 2016

Let me know if there's any additional debug info that would be helpful to you in hunting this down.

@LazyBoot

This comment has been minimized.

Show comment
Hide comment
@LazyBoot

LazyBoot Mar 2, 2016

Looks like the windows update with the issues has been pushed live. I started having issues with mumble eating cpu cycles after yesterdays update.

mumble-cpu

LazyBoot commented Mar 2, 2016

Looks like the windows update with the issues has been pushed live. I started having issues with mumble eating cpu cycles after yesterdays update.

mumble-cpu

@mkrautz

This comment has been minimized.

Show comment
Hide comment
@mkrautz

mkrautz Mar 3, 2016

Member

Also affects 1.2.x.

Member

mkrautz commented Mar 3, 2016

Also affects 1.2.x.

@mkrautz

This comment has been minimized.

Show comment
Hide comment
@mkrautz

mkrautz Mar 3, 2016

Member

Fix is in, at 6f1331b

Will do a snapshot ASAP.

Member

mkrautz commented Mar 3, 2016

Fix is in, at 6f1331b

Will do a snapshot ASAP.

@mkrautz

This comment has been minimized.

Show comment
Hide comment
@mkrautz

mkrautz Mar 3, 2016

Member

Snapshot is available as Snapshot 1.3.0963ge174f8d~snapshot. (https://www.mumble.info)

Member

mkrautz commented Mar 3, 2016

Snapshot is available as Snapshot 1.3.0963ge174f8d~snapshot. (https://www.mumble.info)

@nheppe

This comment has been minimized.

Show comment
Hide comment
@nheppe

nheppe Mar 4, 2016

I can confirm that the above issues with the xbox one controller were present when on version 1.2.14

I can also confirm that the new snapshot resolves these issues.

nheppe commented Mar 4, 2016

I can confirm that the above issues with the xbox one controller were present when on version 1.2.14

I can also confirm that the new snapshot resolves these issues.

@mkrautz

This comment has been minimized.

Show comment
Hide comment
@mkrautz

mkrautz Mar 5, 2016

Member

Now in 1.2.x snapshot form:
https://dl.mumble.info/mumble-1.2.15~19~ga4d5b1e~snapshot.msi

I hope to release this as-is as 1.2.15, if nothing goes wrong. Feel free to test.

Member

mkrautz commented Mar 5, 2016

Now in 1.2.x snapshot form:
https://dl.mumble.info/mumble-1.2.15~19~ga4d5b1e~snapshot.msi

I hope to release this as-is as 1.2.15, if nothing goes wrong. Feel free to test.

@mkrautz

This comment has been minimized.

Show comment
Hide comment
@mkrautz

mkrautz May 1, 2016

Member

It was released with 1.2.15, but wasn't closed accordingly.

Thanks @laenas for reporting this early. :-)

Member

mkrautz commented May 1, 2016

It was released with 1.2.15, but wasn't closed accordingly.

Thanks @laenas for reporting this early. :-)

@mkrautz mkrautz closed this May 1, 2016

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