Dolphin, the GameCube and Wii emulator - Forums

OK, here is a way to disable the Windows automatic installation completely
IMPORTANT -> Reverse all the changes back, after you successfully did the Installation !!!!

1. Deinstall the Bluetoothdriver. YES, you do it in the Device manager Deinstall driver !!!
2. Unplug the Bluetooth adapter, then reboot your system.

Now we disable the automatic Installation from Windows:
- Press "Win-Key & R" and type in gpedit.msc and hit enter
- go to Computer configuration -> Administative Templates -> System -> Device Installation -> Device Installation Restrictions

- Now Rightclick on " Prevent Installation of Devices not described by other policy settings" and select "Edit"
- in the new window click on "Enabled"(upper left-hand-side), then click on "apply" and "OK"

- Back in the Local Group Policy Editor, same Window and path, Right click on the Right hand side window now at
"Allow Administrators to override Device Installation Restriction policies" and in the new window, enable this one as well, Apply and OK

Now plug in your Bluetooth adapter on the Motherboard (without any Hub) and start Zadig.
This time Windows will not install any driver. SO now you can install the Zadig driver (Carefull, there are 2 libusk. One with something v3 or so....Use the pure libusk !!!)
- again verify the PID and VID in Zadig to be sure, you're on the right device !!!

When done, reverse the changes from aboce (Adminstrator Overwrite and Prevent Installation)

Reboot system once more.

Check Device manager, if Adapter is shown.

NOW start Dolphin.....

Also try deleting Wii/shared2/sys/SYSCONF and Wii/btdinf.bak.

Ok, a couple of things before I start that process. First please check the attached screen shot and confirm that's the right libusbk to install? Cause that's the only one that shows up. I get other stuff like WinUSB, libUSB-win32, but as far as libusbk goes that is the only one that shows up.


Now to also bring you up to speed with what has happen while you guys where posting and I was trying what adtbm suggested here

Quote:for testing, i would try to plug the Bluetooth adapter into the rear side of your PC (even if the EMI is bigger) but try to connect it directly to the MoBo not via a Hub.

So I sloted it in the back and... it's very strange, pffff where to begin....:

1. So I put it in the back slot, I put in the correct VID and PID and same error "passthrough is enabled but no USB device was found. Aborting." But then I decided to try putting VID and PID both back to -1 the way Dolphin did it originally and... see point 2.

2. I managed to connect the wiimote twice or so(no idea how) and try out a few games: Boom Blox froze at the character creation screen(but I was at least able to get there using the wiimote); Carnival Mini Golf I got through the tutorial and I think I could have gotten further seemed to behave best; Zelda Skyward Sword gave me a weird error, see attachment(great.... I forgot to save the screenshot, anyway it was a weird error with numbers and codes and stuff); Kororinpa and WarioWare behaved the same way, black screen would not launch.

3. After those 2 or 3 times I was unable to get it to sync again. Here's the thing, even when it was working once I closed a game I had to close Dolphin entirely then fire it up again then start a game again. If I try to start another game without closing Dolphin entirely(doesn't matter if I click reset in controllers, or I try to use the "Shutdown" button on the remote) then same deal, black screen game won't start.

4. Take this with a pinch of salt(since I've never actually touched a Wii before, therefor I have no idea how it's supposed to behave normally) but the movement of the wiimote seemed off to me, like how mouse sensitivity pisses you of in some pc games, you know? Is there any way to configure the sensitivity if/when I get it running for good?

5. In fullscreen, the wimmote hand pointer thing stops properly when it reaches the top and left sides of the screen. But on the bottom and right sides it goes of the screen...

6. Not sure if there was anything else, I've got a very crappy memory and there was a lot of strange stuff to keep track of....


P.S. Umm, ok Craftyawesome, but are you sure? WHat are those things for anyway?

P.S.S. Ok, I have to go to bed now. I've uninstalled the driver and did the whole permissions stuff. I'll try reinstalling the driver tomorrow after you confirm that the one in the screenshot is the right one, or/and if it's not then after you point me to the right one.

Yep, that is the right one !

And Craftyawesome is absolutely right, (As quoted from the Bluetooth passthrough page):

*Quote on*
Wii Remotes do not stay paired after closing the game
This means that your adapter is likely broken and does not remember Wii Remote link keys properly. Use a different adapter to avoid this issue.
This may also happen if your SYSCONF is corrupted or if you changed to a Dolphin version which doesn't have BT passthrough. If your adapter is listed as working with pairing or if you're sure it supports pairings (by having checked the HCI command replies), you can try deleting Wii/shared2/sys/SYSCONF and Wii/btdinf.bak.
*Quote off*

Morning guys,


Ok I did all those things and, we've made some headway, but things are still weird, so lets go through them:

1. I can run games and connect the wiiremote using the red button in the battery compartment, I even managed to get Wario Ware and Kororinpa to run too(zelda still won't work). But the problem remains, once I close a game I have to close the entire emulator and relaunch it if I want another game to work(otherwise I still just get a black screen)... Thing's I've tried to solve this(none worked):
a) The remote is paired, I close the game and then try to run another game.
b) The remote is paired, I press reset in controllers then I close the game then I try to run another game.
c) The remote is paired, I preset reset in contollers then I close the game, then I press refresh, then I try to run another game.

2. Wario Ware did give me an error(see attachment it's the one that gives yes and no option) when I launched it, although it seemed to play fine after I pressed ok at the error prompt.

3. Zelda Skyward Sword still won't work and gives me the same error as yesterday(this time I remembered to save the screenshot, yay?) see attachment.(it's the one with invalid write to something)

4. The remote hand cursor still has problems going of the screen when I go to the edges. Is there any way to contain it both when I run fullscreen, but also, specially when I run it windowed contain it within the game window?

5. I can only connect the wiimote using the red button from inside the battery compartment. Pressing the 1+2 buttons as suggested in the wiki does not work, it just blinks for a good long while and then nothing. Is there really no way to connect it without the red button(I've explained my fears with this)?!

6. On a game where I used Dolphins save state feature, I can't connect the remote after loading up the save. It states here that it should work.


Think that's all I got, but here's something important(I think, maybe) for you guys to consider. Initially, before I had the adapter, I installed Dolphin 5.0(this one has an actual installer as you may know) and messed around with it a bit, opened some games(even zelda opened with no errors back then), tried different options, etc.
A day or 2 later while reading up on more wikis and guides and posts(so as to be ready for when the adapter arrives.... ironic, ha?) I noticed that version 5.0 might not have bluetooth passthrough. I created a thread, asked people to confirm this, they confirmed it and recommended that I install the latest beta version. So I uninstalled 5.0 and "installed" the latest version. I use "" because that beta one didn't actually have an installer, it was just a zip archive with all the files already in it, so I just created a folder(same name and place as where the uninstalled 5.0 had if this matters) and copied them.

Now I SPECIFICALLY!! asked people in that thread "Hey do I need to worry about any leftover files, registry keys, etc. from the first installation before updating?". They all(including a developer ) said no. Nobody figured worth mentioning about the giant folder with a ton of subfolders and files the dolphin creates in my documents...?

My point is, does any of this matter or am I just rambling like an idiot? Should I attempt a clean "reinstall" of dolphin? If you say yes, then please, I beg you!!! is there anything, ANYTHING else at all that I should know about(no matter how insignificant) apart from the main dolphin folder and the folder in my documents? Does it create any stuff in users/appdata or something, any registry keys at all and what search terms do you recommend I use in the registry(besides dolphin obviously), etc.?
If I go this route should I also remove and install the adapter driver again?



P.S. Thank you everyone sooo very much for all the help, in this thread and all the others. If I sound pissed off above, I'm not blaming anyone, and it's not that I don't appreciate what everyone is doing, I'm just frustrated with my own life and how it seems to pretty much always f*** everything up.

I would rename your dolphin emulator folder (the one in documents, not by the exe) and see if there is still issues.a

I renamed it, and although it didn't help much a couple of things have changed!:

1. Still have to close the emulator if I want to run a game after just closing one, that hasn't changed.

2. Wario ware gives me the same error, still seems to work fine if I press ok on that error.

3. Now Skyward Sword gives me the same error as Wario ware instead of the one it was previously giving me, but sadly unlike Wario the game doesn't work if I press ok at the error. It just stays at the safety screen(the one that appears on all wii games about strapping your wiimote)
LE: After writing point nr. 4 I figured I'd open Dolphin again and see what happens if for Skyward Sword I click no on that error instead of yes. And guess what, this time the error didn't even appear, and the game kinda ran well(I got as far as creating a new profile before I decided to shut it down).

What I mean by kinda? Well, lets ignore the crappy 20 fps(I always expected to have to upgrade my pc before this particular title got good performance) but it connected the wiimote without and problems, it detected that I attached that other thing to the remote after it prompted me to do so and it calibrated when I set it on a flat plane.
The problem, and I don't know if this was caused by whatever is causing the other issues or by my poor pc specs, heck I don't even know if it's an actual problem or what the game is supposed to do, someone who has played it will have to confirm; anyway the problem is when the opening cinematic started there was one strange line of voice(which I don't even think it was in english and sounded a bit distorted too) but then the rest of the cinematic(which ran at a steady 30fps) there was no voice for the text.

4. The best(maybe only?) piece of good news is that now I discovered that I can connect the wiimote by just pressing the 1 button or the 2 button(so not both of them at the same time as the wiki says), that usually works instantly or after a few tries. Not sure if this is a change or not as before I was always trying to press them both at the same time, but it is very welcome news that I don't have to press the red button anymore.


Now I don't know if this matters anymore since messing with the emulator seems to change things so maybe this is more a software issue then a hardware one?
But I did remember that when I first plugged the adapter in my system and windows did it's thing it didn't just say "generic bluetooth radio ready to use"(this is the one I installed libusk to and this is the one that I removed and reinstalled while disabling the automatic windows installation like adtbm suggested) there where 2 or 3 more stuff that it added that where all "ready to use". Sadly I was too much of a stupid retarded idiot to think to take a screenshot of that, and now I have no way of remembering what they where....

I thought 1 and 2 was only for real wiimote (emulated Bluetooth). I would try to reinstall windows/install to a separate drive but that's probably not an option. I feel like maybe 2 drivers work with Passthrough so try it?

Yeah, you're spot on, with all the things I've got going on over here and all the eccentricities of having everything set to my liking, reinstalling windows would take me about 3 days, if not longer.... So that is totally not an option, at least not yet, in around 3-4 months time I'm gonna upgrade my pc(new motherboard, processor, etc.) and the nightmare of having to reinstall windows will, unfortunately, have to happen then...

Quote:I feel like maybe 2 drivers work with Passthrough so try it?

I have no idea what you're talking about here...?

I think, what craftyawesome means, is, that you maybe installed the Zadig pass through driver
in the first attempt, maybe to a wrong USB device and now you have two passthrough active.

If this would be the case, you would need to deinstall all usb device drivers
and then let windows automatically reinstall the drivers. like this you could remove the
incorrect pass through device and could ensure that you only have the Bluetooth Adapter in passthrough.

At this point i would say as well, that your problem is Hardware/Driver related and this would be, were i would
continue to investigate.