So, I am currently trying to connect my wii remote plus (the one with motion plus) to dolphin so that I can play Skyward Sword in glorious HD. I first saw dolphin from this video: https://www.youtube.com/watch?v=ytJcw6jIdqA Since everything in the video seemed to make sense, I went ahead and bought the stuff he suggested. Now that i'm hooking it all up though, while the little bluetooth dongle he said to get (Kinivo BTD 400) recognizes my Wii Remote Plus, when I go into the controller section of Dolphin and hit the refresh button, either it freezes for a couple seconds and does nothing, or it makes Dolphin freeze permanently, and I have to shut it down in the task manager. That was using Dolphin 5.0 I tried using a previous version Dolphin 4.0-9483, and while that doesn't seem to freeze permantly, it also doesn't seem to recognize the wii remote plus. Now, I've seen the wiki page where it talks about using Toshiba Bluetooth stack or whatever it is, and unfortunately, the Kinivo dongle doesn't seem to be compatible. However, in the video, the guy is using a Wii Remote Plus (you can see where it says motion plus inside on his wii remote) and he is able to play the game, and he never says anything about needing to use the Toshiba bluetooth stack. The only difference that I can see is that he is using Dolphin 4.0. So, my question is, what all do I need to do further to get my wii remote plus working with dolphin. Should I just go and try to use verion 4.0? Is there an alternative to Toshiba Bluetooth Stack? Is the freezing of Dolphin 5.0 a bug that is keeping me from connecting the remote? What should the controller section of Dolphin even look like when a wii remote is successfully connected? How do you even tell? The only way that I could tell so far (when it doesn't completely freeze), is that when I start up Skyward Sword, it says that my wii remote is disconnected in the little yellow text that dolphin puts in the top left corner.
Dolphin not recognizing Wii Remote Plus
|
06-28-2016, 08:20 AM
Ok, so I've been doing some more reading, and I came across this post about something called the DolphinBar. https://dolphin-emu.org/blog/2014/08/23/...ar-review/ . My question is, given that the review is 2, almost 3 years old now, is that review still relevant to the current state of dolphin (Dolphin 5.0). I tried looking elsewhere on the forums to see if people had anything to say about the dolphinbar in relation to Dolphin 5.0, but every post I saw was at least a year old. If the dolphinbar is what i need, then I can just send my current dongle and sensor bar back to amazon and get a refund, I just need to know if that is the right choice in this situation.
06-28-2016, 08:43 AM
(06-28-2016, 08:20 AM)KnobbyNobbes Wrote: Ok, so I've been doing some more reading, and I came across this post about something called the DolphinBar. https://dolphin-emu.org/blog/2014/08/23/...ar-review/ . My question is, given that the review is 2, almost 3 years old now, is that review still relevant to the current state of dolphin (Dolphin 5.0). I tried looking elsewhere on the forums to see if people had anything to say about the dolphinbar in relation to Dolphin 5.0, but every post I saw was at least a year old. If the dolphinbar is what i need, then I can just send my current dongle and sensor bar back to amazon and get a refund, I just need to know if that is the right choice in this situation. Do you have a -tr wiimote and do you use windows 7? 06-28-2016, 10:52 AM
I'm also experiencing this issue.
Here is what I currently have: Windows 10 x64 Latest stable-release of Dolphin 5 (not a dev version) A NON-TR WiiMote Plus (Zelda Gold-WiiMote) Controller A external Belkin BT USB Adapter DolphinBar (with what I think is the latest F/W installed) I've tried a few things here: 1. Using Belkin BT adapter, getting Windows 10 to pair with the WiiMote. While mostly successful, it states "Connected" in the Windows Setting Dialog, however, the WiiMote constantly blinks all 4 leds...this never ends. 1a. Fire up Dolphin 5 x64 and click on Controllers. In the Wiimotes section, i change Wiimote 1 to "Real Wiimote." 2a. In the "Real Wiimote" section, Continuous Scanning is already enabled. I click "Refresh" in this section... and Dolphin hard locks. At this point. I have to forcefully close Dolphin from TaskManager. 2. Using the DolphinBar, I can get the Wiimote to connect to the bar pretty easily. Most of the modes work from the bar with the Wiimote. 1a. I try following pretty much the same directions above (Real Wiimote, etc), yet Dolphin just cannot make use of the controller. 2a. Clicking "Refresh" in the controller dialog almost always causes Dolphin to hard lock. I've enabling as much logging as I could, but can't get any real feedback from Dolphin. The most I was able to get is the following: 47:48:349 Core.cpp:978 W[COMMON]: Want determinism <- false 47:48:452 Main.cpp:550 N[Wiimote]: Not connected 47:48:491 FileUtil.cpp:136 W[COMMON]: Delete: DeleteFile failed on C:/Users/Me/Documents/Dolphin Emulator/Wii/title/00000001/00000002/data/setting.txt: The process cannot access the file because it is being used by another process. 47:48:730 C:\dolphin\Source\Core\Core/IPC_HLE/WII_IPC_HLE_Device.h:245 W[WII_IPC_HLE]: /dev/sdio/slot1 faking Close() 47:48:730 C:\dolphin\Source\Core\Core/IPC_HLE/WII_IPC_HLE_Device.h:245 W[WII_IPC_HLE]: /dev/usb/oh1 faking Close() 47:48:730 C:\dolphin\Source\Core\Core/IPC_HLE/WII_IPC_HLE_Device.h:139 W[WII_IPC_HLE]: _Unimplemented_Device_ does not support Close() 47:50:064 IPC_HLE\WII_IPC_HLE.cpp:372 W[WII_IPC_HLE]: Trying to open /dev/usb/oh1/57e/305 as 5 47:50:129 IPC_HLE\WII_IPC_HLE_Device_usb.cpp:1571 E[WII_IPC_WIIMOTE]: HCI: CommandDeleteStoredLinkKey... Probably the security for linking has failed. Could be a problem with loading the SCONF 47:50:186 Main.cpp:550 N[Wiimote]: Connecting... 48:05:998 C:\dolphin\Source\Core\Core/IPC_HLE/WII_IPC_HLE_Device.h:245 W[WII_IPC_HLE]: /dev/sdio/slot1 faking Close() 48:05:998 C:\dolphin\Source\Core\Core/IPC_HLE/WII_IPC_HLE_Device.h:245 W[WII_IPC_HLE]: /dev/usb/oh1 faking Close() 48:05:998 C:\dolphin\Source\Core\Core/IPC_HLE/WII_IPC_HLE_Device.h:139 W[WII_IPC_HLE]: _Unimplemented_Device_ does not support Close() So, as any good user should, I downgraded back to Dolphin 4 (the latest in that version line). As I expected, connected to the WiiMote using the external BT adapter worked as expected. There was absolutely no issues at that point. At this point, I'm not sure what to do next for Dolphin 5. Has anyone else hit this issue, or even found a solution? I've tried checking the boards, but honestly, I can't find a solution there. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)