+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Controllers (https://forums.dolphin-emu.org/Forum-controllers)
+--- Thread: Keyboard Input on Mac OS X with a recent developer build (/Thread-keyboard-input-on-mac-os-x-with-a-recent-developer-build)
Keyboard Input on Mac OS X with a recent developer build - Orinks - 09-24-2014
Hello everyone,
I got Dolphin and like it, though keyboard input works on Windows, but I unfortunately didn't get the 64Bit version of Windows for Boot Camp so can't run the Windows developer build.
What is puzzling is that I know the default hotkeys for the emulated Wiimote. Left right click for A/B, arrow keys for DPad, enter/return is start. While I'd assign these later, I usually try and press enter at the start of a game to test keyboard input. I got it to work once, but unfortunately never again. I ran it, and since I use VoiceOver put it in full screen to really get it working. It still didn't work, even when turning VOiceOver off. Anyhow, VOiceOver shouldn't be effecting keyboard input since when I pressed enter that one time and it paused the game, I was out of full screen, though even in full screen pressing the left or right mouse buttons with my mouse the command did not register. Maybe, even though I'm connected via USB, I'll head into options and see if that option actually works.
RE: Keyboard Input on Mac OS X with a recent developer build - KHg8m3r - 09-24-2014
You should reinstall Windows using your current key as 64 bit. Its pretty easy since you already have bootcamp setup, just insert a 64 bit boot cd and run the setup.exe from windows. Follow the prompts, and then click on custom install. It will boot to the CD and then let you reinstall over the current Windows, and you can choose to have your old files copied over to a folder in the new install.
As for the keyboard issue, do you have background input checked?
RE: Keyboard Input on Mac OS X with a recent developer build - Orinks - 09-24-2014
No, should I have it checked and where is it under configuration?
RE: Keyboard Input on Mac OS X with a recent developer build - KHg8m3r - 09-24-2014
When configuring the controller, its in the bottom right of the screen.
Try checking it to see if it helps.
RE: Keyboard Input on Mac OS X with a recent developer build - Orinks - 09-24-2014
Hi,
Well, I assume it's Emulated WiiRemote 1 that uses keyboard input by default, so I went in there and checked background input. The game still behaves as before, not registering any keys whatsoever. As I said in my first post, I got it to work this morning exactly one time and couldn't get it to work again. I had this issue with VMware Fusion a few years back, but I don't know if that has any connection to this. Doubtful, because OpenEmu works like a charm, and if they had Wii support in that I'd switch in a flash.
Again, Windows works, but it's sluggish since I have to use 4.2.2 and performance seems to be better on the Mac. I need as much of a lag free environment as I could possibly get because I'm playing Rhythm Heaven Fever where timing is absolutely necessary and you can't be a single millisecond off in most cases. On Windows with 4.2.2, I get about a second of lag, so I have to time my presses a second earlier than the Metronome would actually require if I were playing it on a Wii.
So if this keyboard issue is a bug, I'd love to find it, report it and have it fixed. I had a friend of mine get the app and he too had similar results.
Hope we can find some kind of solution.
RE: Keyboard Input on Mac OS X with a recent developer build - pauldacheez - 10-03-2014
Which device do you have selected in the Devices dropdown? Dolphin may or may not have selected the right input by default. For keyboards it should look like "Keyboard/0/Apple Bluetooth Keyboard"; none of the "Input/0/xxx" ones work unless they're actual gamepads.
Also, make sure to leave "Background Input" on, as they haven't completely fixed the issues surrounding that, AFAIK.