I created and account just to post this issue that I've been having with my GC adapter and Dolphin. I bought the official GC adapter for the Switch, and from what I've heard, it's almost identical to its predecessor, the Wii U adapter. I've been using it with Dolphin, and for the past few weeks, it's been working perfectly. I installed the driver with Zadig and everything went well, with no trouble detecting the device.
However, just recently, I've been experiencing an issue that I haven't had before. When I was playing the original Animal Crossing, the controller abruptly acted up and the up input on the analog stick was permanently held. To try to fix this, I set the controller for the port I was using to "None", then back to its regular Wii U setting. This time, the game acted as if one of the triggers was constantly being held down, so my character was constantly running. I switched the controller from "None" back to Wii U for a third time, but now, I could not move or enter any input at all. Doing the same process again did nothing, so I had to stop the emulation for it to work again. I disconnected and reconnected my GC adapter multiple times but it did nothing.
So far, I've only experienced this issue with Animal Crossing, and this exact same problem happens every 30 minutes or so in the game. However, this never happened at any time when I was playing the game with the previous versions of Dolphin. This problem only surfaced when I updated Dolphin to version 5.0-9494. Another thing to note, I also installed vJoy in order to use my GameCube controller with games outside of Dolphin. I can assure you that vJoy wasn't running when I used Dolphin's native support, and I always make sure not to have it turned on. With vJoy, I haven't experienced any issues like this.
My Animal Crossing ISO is in good shape and doesn't have any problems with it that I know of. Again, it was working perfectly fine before the update. I also made sure not to change any settings, and that the settings were the same as before. One last thing, I've also been getting the "FIFO is overflown by GatherPipe, CPU thread is too fast!" error when I play the game. I know this has something to do with the Dual Core setting, but should this be happening? It wasn't happening before the update either.
However, just recently, I've been experiencing an issue that I haven't had before. When I was playing the original Animal Crossing, the controller abruptly acted up and the up input on the analog stick was permanently held. To try to fix this, I set the controller for the port I was using to "None", then back to its regular Wii U setting. This time, the game acted as if one of the triggers was constantly being held down, so my character was constantly running. I switched the controller from "None" back to Wii U for a third time, but now, I could not move or enter any input at all. Doing the same process again did nothing, so I had to stop the emulation for it to work again. I disconnected and reconnected my GC adapter multiple times but it did nothing.
So far, I've only experienced this issue with Animal Crossing, and this exact same problem happens every 30 minutes or so in the game. However, this never happened at any time when I was playing the game with the previous versions of Dolphin. This problem only surfaced when I updated Dolphin to version 5.0-9494. Another thing to note, I also installed vJoy in order to use my GameCube controller with games outside of Dolphin. I can assure you that vJoy wasn't running when I used Dolphin's native support, and I always make sure not to have it turned on. With vJoy, I haven't experienced any issues like this.
My Animal Crossing ISO is in good shape and doesn't have any problems with it that I know of. Again, it was working perfectly fine before the update. I also made sure not to change any settings, and that the settings were the same as before. One last thing, I've also been getting the "FIFO is overflown by GatherPipe, CPU thread is too fast!" error when I play the game. I know this has something to do with the Dual Core setting, but should this be happening? It wasn't happening before the update either.
![[Image: sig-22354.png]](http://www.spyber.com/sig-22354.png)