(03-21-2013, 02:47 AM)LordVador Wrote: [ -> ] (03-21-2013, 02:22 AM)apollo003 Wrote: [ -> ]I am still not seeing the "Alternate Wiimote Timing" checkbox, though.
See the pic.
(03-21-2013, 02:22 AM)apollo003 Wrote: [ -> ]Can I also ask what the hokey Alt+F5 does?
It reconnects your Wiimote
Do I have a wrong version of dolphin? Do I also need to change paths in case I don't have write permissions for the default ones? I am the only user on this laptop but I don't think my current user is technically the administrator.
(03-21-2013, 03:05 AM)apollo003 Wrote: [ -> ] (03-21-2013, 02:47 AM)LordVador Wrote: [ -> ] (03-21-2013, 02:22 AM)apollo003 Wrote: [ -> ]Can I also ask what the hokey Alt+F5 does?
It reconnects your Wiimote
I don't know if it helps, but I was NOT getting the initialization vibration when I was hitting Alt+F5. Maybe it doesn't stay connected after I hit refresh?
(03-21-2013, 03:05 AM)apollo003 Wrote: [ -> ]Do I have a wrong version of dolphin?
No. When you open Dolphin your games should appear as a list. Right click the game
in this gamelist. Then go into Properties.
(03-21-2013, 03:05 AM)apollo003 Wrote: [ -> ]Do I also need to change paths in case I don't have write permissions for the default ones? I am the only user on this laptop but I don't think my current user is technically the administrator.
You have to indeed. Don't place Dolphin in Programs. Place it in Documents.
(03-21-2013, 03:05 AM)apollo003 Wrote: [ -> ]I don't know if it helps, but I was NOT getting the initialization vibration when I was hitting Alt+F5. Maybe it doesn't stay connected after I hit refresh?
Use Alt+F5 after launching the game (wait for the first screen). When you hit Alt+F5 it should write "Connected/not connected" in the top-left corner
Uhh hello.
I have had the same problem with Dolphin 3.5 (the stable version from the official website). I was following along this thread, did all that apollo did, and... still nothing. The wiimote is hooked up acording to Dolphin, but the game running pops up at the screen that tells you what controllers are valid for it (sideways wii-mote, which I have configured correctly for when i used emulated wiimote 1), classic or gamecube, and says "Lost Connection to Wii Remote 1". I then use Alt+F5, it writes "wiimote 1 connected", and yet, no other change. Mashing all the buttons on the wii yeilds zero response and the game will not proceed past this.
If I use an emulated wiimote instead of a real one, I can play the game just fine, but the real wiimote is.. not detected by the game? I think?
If this is a dead issue that was solved somewhere else (I realize this thread is months old), please point me to it and sorry for dragging up the dead.
Thanks if anyone can help.
(08-27-2013, 10:29 AM)ExtremeDude2 Wrote: [ -> ]Try latest versions of Dolphin
I completed
.
@myrealnameistwtich: You'll have to give us more details. BT adapter/stack you're using, if your Wiimote is an official one or not, the game you're trying to play...
(08-27-2013, 10:19 PM)LordVador Wrote: [ -> ] (08-27-2013, 10:29 AM)ExtremeDude2 Wrote: [ -> ]Try latest versions of Dolphin
I completed .
@myrealnameistwtich: You'll have to give us more details. BT adapter/stack you're using, if your Wiimote is an official one or not, the game you're trying to play...
OK, well as I said I have had the same exact situation as the OP here, but sure:
ASUS BT USB Adaptor
Windows Stack (I believe... not sure how to double check this, but I simply installed the drivers from the ASUS CD and then windows did the automatic driver instillation bit it does when you plug in a new device. I really am not sure if this makes it Windows or ASUS "stack".) - Regardless, the Wiimotes are picked up by the computer and recognized by Dolphin 3.5 (Most up to date, Stable version from the dolphin-emu.org/download site).
The wiimotes are original from the first few weeks of the launch of the Wii.
I have tried it on two games thus far, Dokapon Kingdom where I am stopped at the controller information screen (See fig 1), and then on Xenoblade Chronicals at the start menu where it says "Press any button to continue".
Figure 1
Figure 2
@ ExtremeDude2 If you mean the latest Dev version, that is what I started with originally, however I had the same issue, so I just used the most up to date version listed under Stable builds.
The Windows Bluetooth Stack is possibly the culprit --- the emulator has nothing to do with the problem obviously. Devs will have no clue of this problem, so they won't be much help. You can stop the windows bluetooth service from services.msc. I had to do this occasionally. You can confirm the device status from devices and printers menu.
The bluetooth discovery protocol appears to work fine for Windows, so you probably don't need to disable that service. The collision between the windows and a third party (i.e. toshiba, widcomm) bluetooth stack is most likely the root of the problem.
(08-31-2013, 08:40 AM)greatbrian2 Wrote: [ -> ]The Windows Bluetooth Stack is possibly the culprit --- the emulator has nothing to do with the problem obviously. Devs will have no clue of this problem, so they won't be much help. You can stop the windows bluetooth service from services.msc. I had to do this occasionally. You can confirm the device status from devices and printers menu.
The bluetooth discovery protocol appears to work fine for Windows, so you probably don't need to disable that service. The collision between the windows and a third party (i.e. toshiba, widcomm) bluetooth stack is most likely the root of the problem.
I do not have a thirdparty bluetooth stack, only the drivers that installed when my device was detected.
what is the windows bluetooth service titled in services.msc? All I see that references bluetooth is bthserv, which is described as "Bluetooth service supports discovery and association of remote Bluetooth devices. Stopping or disabling this service may cause already installed Bluetooth devices to fail to operate properly and prevent new devices from being discovered or associated."
Please give me more information.
EDIT: I stopped that bthserv, which managed to make it so Dolphin no longer found my Wiimotes. I then turned that service back on, and it all works fine. I guess that was the fix? Maybe the service had a mistake the first time it autodetected the wiimotes? I really can't say how it fixed it, but I am now playing games fine multiple wiimotes.