SOLVED: Thank you ulaoulao! All I had to do was go into Dolphin 3.5 and go to Options-Configure-Gamecube and set Port 1-4 to Standard Controller and it works. I have Windows 8.1 and I have tried using Dolphin 3.5 and Dolphin 4.0.2. Nevertheless I cannot get a second controller to work. When I am in the GCPad settings and I load the profile I used on my Windows 7 PC it reads since the red buttons light up on the GCPad window and the joystick does read. But in game when I play Mario Kart I cannot select a character for player 2. Player 1 controller works fine!
Oct 6, 2017 - Fire Emblem with keyboard, fine. Mario with keyboard, ick! Follow these. How can I play on the Dolphin GameCube emulator using my computer's joypad? 37,212 Views. How can I use a gamecube controller on mac? Can reproduce as well. Running OpenEmu v. 1.0.4 on OS X Yosemite v. 10.10.3 with Chrome v. Occasionally OpenEmu will not register any keyboard input, not even to change the button layout in the preferences. Plugging in a controller is a workaround, but the keyboard doesn't work after unplugging it.
Also I am using a Xbox 360 wireless receiver and two Xbox 360 wireless controllers. EDIT: I also tried using the keyboard and mouse as an input for player 2 and player 1 as an controller. Player 1 works but player 2 still doesnt work. Which means its not the controllers acting up.
Before deleting, I tested a couple other features and found that I have a more serious problem. When closing an emulator window, the game will end but the window itself will not go away. I attempted opening another ROM and I had the same issue. Now both games I opened will start up automatically when opening the program and the dead windows will remain when I try to close them. Additionally, another issue I found when looking for core updates is that closing the updates window will crash the program.
If it helps, I have only been using the GBA emulator and the games I have tried are Pokemon FireRed and Kirby's Nightmare in Dreamland. I installed the program from this link The program worked perfectly for me until the first time I closed it, and now these issues have come up. I was originally pausing the game and returning to it rather than quitting altogether. Should I do a complete wipe and reinstall?
Thanks so much for the response. Don't download precompiled versions, compile the latest version from github directly. On Jun 6, 2013, at 4:48 PM, n-cubed wrote: Before deleting, I tested a couple other features and found that I have a more serious problem. When closing an emulator window, the game will end but the window itself will not go away.
I attempted opening another ROM and I had the same issue. Now both games I opened will start up automatically when opening the program and the dead windows will remain when I try to close them. Additionally, another issue I found when looking for core updates is that closing the updates window will crash the program. If it helps, I have only been using the GBA emulator and the games I have tried are Pokemon FireRed and Kirby's Nightmare in Dreamland. I installed the program from this link The program worked perfectly for me until the first time I closed it, and now these issues have come up. I was originally pausing the game and returning to it rather than quitting altogether.
![Mac Mac](/uploads/1/2/5/5/125575892/625955673.jpg)
Should I do a complete wipe and reinstall? Thanks so much for the response.
![Dolphin Dolphin](/uploads/1/2/5/5/125575892/549145384.png)
— Reply to this email directly or view it on GitHub. I deleted the Default.oebindings file and it solved my problem - keyboard now working absolutely fine. I am using the latest build downloaded from GitHub yesterday for full informational purposes. Thanks for the help.
On 7 Jun 2013, at 00:23, clobber wrote: I too am using the built-in keyboard as well as an external and input works on both. Are you using a new build? We haven't touched input code in some time. For fun let's try deleting /Library/Application Support/OpenEmu/Bindings Configurations/Default.oebindings and see what happens. — Reply to this email directly or view it on GitHub.