Emulator

Usually when something like this happens, it's due to another program (usually a sound driver?) stealing the adapter because they use LibUSB.

I don't think this is Dolphin's bug. Please turn on logging and see if the adapter is being disconnected while you play.

Actually I think it's a Dolphin bug. It also happens to me. I never had this problem before.
See : https://forums.dolphin-emu.org/Thread-wiiu-gc-adaptater-is-slightly-broken

I played a 6+ hour marathon on netplay earlier tonight with an official GC adapter and did not run into a bug.

Unless someone can get more information, there's nothing that can be done unless a developer runs into the bug.

If a random direction is hitting, 99% of the time it means we lost connection to the adapter. If you turn on log messages, you should see the adapter getting disconnected when this bug occurs. This should give us the necessary information on how to move forward.

Thank you for your time.

Turned on the logs and the issue occured. It was just as you expected. The adaptor is reading as detaching and reattaching. I just don't know why it does this. My cables were rested on a table so they didn't drop, and the device works just fine on my WiiU. Pastebin logs are included below.
http://pastebin.com/Mem5cE6Z

Thanks for the log, it does look like windows drivers madness again. You could try removing other usb devices (such as mouse or keyboard). See https://bugs.dolphin-emu.org/issues/8552 (it was considered fixed because they weren’t using the adapter at that time, so disabling the adapter entirely fixed it), but there’s not much we can do about it, if it is this issue.

I’ll submit a libusb update to dolphin externals in the next few days, but I don't have too much hope…

mathieui wrote:

Thanks for the log, it does look like windows drivers madness again. You could try removing other usb devices (such as mouse or keyboard). See https://bugs.dolphin-emu.org/issues/8552 (it was considered fixed because they weren’t using the adapter at that time, so disabling the adapter entirely fixed it), but there’s not much we can do about it, if it is this issue.

I’ll submit a libusb update to dolphin externals in the next few days, but I don't have too much hope…

Are you still planning on updating libusb? There have been a number of complaints about random input using GameCube controllers since this report was made and it would be nice to see if updating it helps at all.

I'm experiencing this same issue on 5.0-321 (specifically while playing 0e63d4223b01d9aba596259dc155a174) with one caveat regarding when/how it is being caused: I'm only seeing the adapter disconnection while moving my mouse; otherwise, it remains connected without any issues.

libusb has now been updated to 1.0.20. Could a user who has had issues with random inputs with the Wii U adapter test with the latest Dolphin development builds to see if there is any improvement?

And now libusb has been updated to 1.0.21. I doubt that will fix any issues on master though, but there's another thing you can try.

1.0.21 introduces a new libusb backend on Windows (usbdk). Since it's an entirely new backend, it may not have this problem at all. For instructions on how to try it, see this post: https://www.reddit.com/r/emulation/comments/5k8ho4/looking_for_feedback_potentially_changing_usb/dbm3eyy/

You can ignore things that are specific to USB passthrough (whitelisting devices); all you need to do is use the special PR build, launch Dolphin and use your GC adapter as usual.

I've recently been having this problem so I figured I'd contribute to doing some testing and try to uncover the reason behind this issue.
A bit of background history:

• I've been aware of this issue for some time but have never experienced this problem for myself in the last 12-24 months of using the dolphin emulator
• Recently I've started streaming and ever since that time I've been having this issue.

Things I've tried to resolve the issue on my own:

• Plugging different controllers in the GC adapter (did not help)
• Reinstall zadig several times (did not help, except for one instance)
• Using different USB ports (did not help)
• Use different versions of dolphin (did not help)
• Disconnecting all other USB devices (did not help)

Some users on IRC suggested I tried the logger within dolphin, as other users have found:
The adapter seems to disconnect and reconnect at several intervals (can provide the logs if necessary)

After talking to JMC47 I've decided to do a quick test of the following:

• Try to minimize the amount of open processes/applications, at first I decided to kill OBS completely.

1. After OBS was killed I started up netplay and tested it with another user; the random inputs did not occur.
2. Immediately after I started OBS back up again and started streaming; the random inputs started occurring again.
   I was utilizing a Window Capture method for capturing dolphin gameplay.

I'm available for further testing if necessary, hopefully these results will help further identify the cause/problem.

Hey leoetlino,

It does seem like that is the case since most of the information I've found talks about libusb losing focus due to some reason.
So expecting a solution out of dolphin might not be realistic.

With that said in older versions of dolphin (think 4.0 development versions) this problem was not nearly as aggravating.
The difference is in that since 5.0 and up this issue will input a down/left input (and sometimes A) which causes weird behavior in games, while in 4.0 the input would simply reset to neutral (with no input of A).

Obviously both are not ideal, but I'm wondering if it's possible to make it behave more or less the same way as in 4.0.

Has anyone figured this out?

I'm still having this problem and it SUCKS. nothing i do seems to fix this. I don't even know why the USB port would behave like this. My PC and adapter should both be behaving fine, but instead I get these constant down and left inputs as my adapter fails with Dolphin. :angery:

Switched from a USB 3.0 to a USB 2.0 and it fixed the issue.

I'm encountering this symptom trying to run Dolphin in a Windows VM. Can someone tell me how to enable logs so I can confirm it's the same issue? I think it's related to the fact that KVM is emulating the USB controller and i'm hoping to purchase a PCIe USB Controller and bind the entire thing to VFIO so that KVM doesn't have to emulate the controller.

But i'd like to confirm the issue of the mayflash adapter being lost momentarily before i do that. How do i enable logging and what log should i look for to see the mayflash adapater losing connection to dolphin?

View → Show Logs and also View → Show Log Configuration. Then set the verbosity to "info", check "write to window" (and maybe "write to file"), and enable the "Controller Interface (CI)" log (and maybe "Common" and "Serial Interface (SI)").

pokechu22 wrote:

View → Show Logs and also View → Show Log Configuration. Then set the verbosity to "info", check "write to window" (and maybe "write to file"), and enable the "Controller Interface (CI)" log (and maybe "Common" and "Serial Interface (SI)").

Thank you! I will try this later tonight.

Just to confirm, i should be searching for logs similar to the following:

22:19:206 GCAdapter.cpp:353 N[SI]: GC Adapter detached
22:19:722 GCAdapter.cpp:219 N[SI]: Found GC Adapter with Vendor: 57E Product: 337 Devnum: 1
22:19:727 GCAdapter.cpp:384 N[SI]: New device connected to Port 1 of Type: 14
22:23:838 GCAdapter.cpp:353 N[SI]: GC Adapter detached
22:24:320 GCAdapter.cpp:219 N[SI]: Found GC Adapter with Vendor: 57E Product: 337 Devnum: 1
22:24:330 GCAdapter.cpp:384 N[SI]: New device connected to Port 1 of Type: 14

This seems right based on the logs posted in comment #4, i'd just like to make sure i'm correctly identifying the issue. If I see these types of logs every so often it means the adapter is being dropped and re-attached, correct?

I think so. The GC adapter code has changed a bit since then, but that should just mean that when this happens, there's more information to work with.

I colleged a set of logs, here is a brief explanation of each, between each log i closed dolphin completely

dolphinlog1.log - First log without changing anything, I enabled logging after i had already started the game so some logs are cut off
https://gist.github.com/TaakoMagnusen/2be72710143a0d80f7c6ddb14f28879d#file-dolphinlog1-log

dolphinlog2.log - Did not change anything but logging was enabled from the the start of the game.
https://gist.github.com/TaakoMagnusen/2be72710143a0d80f7c6ddb14f28879d#file-dolphinlog2-log

dolphinlog3-resintallWinUSB.log - I used Zadig to re-replace the WinUSB drivers, I did not uninstall the drivers before this. This seemed to make the issue even worse as there were more frequent bursts of errors
https://gist.github.com/TaakoMagnusen/2be72710143a0d80f7c6ddb14f28879d#file-dolphinlog3-resintallwinusb-log

dolphin-libusb-win32.log - I used zadig to install the libusb-win32 drivers, replacing WinUSB
https://gist.github.com/TaakoMagnusen/2be72710143a0d80f7c6ddb14f28879d#file-dolphin-libusb-win32-log

dolphin-deletedDriversAndReplug.log - I went to device manager -> properties -> Uninstall device (and delete drivers), I then unplugged and replugged the device and did not use Zadig to replace any drivers. this may have made it revert to winusb, im not sure
https://gist.github.com/TaakoMagnusen/2be72710143a0d80f7c6ddb14f28879d#file-dolphin-deleteddriversandreplug-log

Nothing worked, each time a "chunk" of errors came in it would result in one "downward movement" on the joystick (so the mario kart main menu which i was using to test would go down one selection).

The problem happens whenever this error occurs (each collective chunk of errors is one joystick movement):

51:24:543 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:543 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:543 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:543 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:545 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:545 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:545 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)
51:24:545 InputCommon\GCAdapter.cpp:734 E[CI]: error reading payload (size: 0, type: 21)

I do not see it saying "GC Adapater detected" though. Only that it fails to read the payload. Maybe that's just the newest error message since i'm on the latest beta of dolphin

typo, colleged -> collected

Can someone confirm that this is indeed the same error where dolphin loses connection to the mayflash adapter. I've ordered a PCIe USB controller and will try to install it tomorrow and see if passing through an entire controller to the VM helps fix this.

Just updating the thread in case someone stumbles upon. it with the same issue I had (running dolphin in a VM). In my case i was passing through the individual USB device (Mayflash gamecube adapater) and the issue was caused by the KVM having to emulate the usb controller (since it didn't own the whole device).

Ihe issue was solved by buying a PCIe USB controller (Inateck PCI-E to USB 3.0 (5 Ports) PCI Express Card and 15-Pin Power Connector) and passing binding the entire PCIe device to the Virtual Machine VFIO. This allowed the KVM to not need to emulate the USB controller and so performance was significantly improved. I'm no longer getting errors or the ghost joystick movement.

Using Dolphin 5.0 for speedrunning Melee, and I continue to run into this issue.

I found this old SmashLadder post addressing it: [[https://www.smashladder.com/blogs/view/26qo/2016-08-12/psa-controller-inputs-down-left-on-c-stick-main-stick-rando]]

I've tried to keep Zadig open, and it seems at least to reduce its frequency, and it tends to happen when I'm using my mouse or keyboard and Dolphin is not the active window.

Would still love a permanent, reliable fix for this if it ever happens!