Emulator

Demo application included with that thing works

http://wiiyourself.gl.tter.org/

Any news on that one?

I've been have problems with my third party wiimote for ages now, i get exactly the same problem, the wiimote pairs up fine but refuses to work in any wii game, i've managed to get it to work a couple of times by going back into the wiimote options and clicking on refresh then pressing alt f5 a few times but most times the game still refuses to accept any input. i've even tried disconnecting the speaker using the game property options. i've tried other software like glovepie etc and they all work fine. these connection problems happen with HLE option selected which i use 90% of the time as the games go to slow with the LLE option even though i have an amd x6 1055t and running windows 7 x64 ultimate.

It's difficult to fix when you don't own a 3rd party wiimote.
Maybe If I feel like cleaning up the wiimote code it'll fix itself.

I can help you by providing info and testing with the remote if you wish.

Please test this fix:

http://code.google.com/p/dolphin-emu/source/detail?r=15d6c6e9fc8a437ca1fffade3ed63e35e72e5448

Tested and it does not seem to fix the issue.

I get same "Src\HW\WiimoteReal\IOWin.cpp:434 N[Wiimote]:WiimoteIOWrite[MSBT_STACK_MS]: Unable to send data to wiimote" error and wiimote will not respond.

Or maybe I screwed up something? I cloned repository, then selected "Pull" and selected "fix-3rd-party-wiimote" branch. Then I compiled it like normal. Is that correct?

Also, some time ago there was "Recording Window" or something like that in Dolphin, which allowed you to record wiimote movements. 3rd party wiimotes were working without problems with this window, which means that dolphin can read data from those wiimotes, just something is wrong with game connecting mechanism.

I can't find this "Recording Window" in new revision, so I cannot test it.

I've noticed that the Windows wiimote code (IOWin.cpp) always skips the first byte, so my fix couldn't ever help there:

	case MSBT_STACK_MS:
		i = HidD_SetOutputReport(dev_handle, buf + 1, len - 1);
                    ...
	case MSBT_STACK_BLUESOLEIL:
		return WriteFile(dev_handle, buf + 1, 22, &bytes, &hid_overlap);
                    ...

What I found while debugging my 3rd party wiimote (on linux), was that the reason the wiimote doesn't work in game, was that the game failed to configure the remote (done immediately when the game boots) (on linux, we were sending data packets instead of set reports). The MS stack code appears to be doing that already -- the HidD_SetOutputReport call makes it look like it. But I don't know anything about the Windows stack -- it may be that still sends data packets unless you configure the stack to do otherwise. Who knows.

I'd try logging the wiimote IO output the game sends to the device (hack IOWrite and IORead for example), and making sure that looks sane (the wiimote replies to all commands it should). If not, hack the WiimoteReal.cpp code to manually send the command the game is sending, and which the wiimote is failing to respond to, right after the Handshake/SetLeds code (send packet, and loop polling input and printf it). Then try to figure out why the wiimote doesn't respond. :-)

I have actually been able to connect my third party wiimote using windows stack since i started using Dolphin; however, it only registers button presses. Advanced functions like ir never worked.
The ir and motion do work fine when using "wiinremote"

Nyko Wand+
Windows 7 64bit

In Windows, there is a hard-coded PID/VID pair to detect and connect Wiimotes. At the moment, the list consists of the official Nintendo Wiimote and one other third-party one. To fix this, a selectable list of PID/VID's that have been detected is probably needed.

Issue 4668 has been merged into this issue.

Issue 4553 has been merged into this issue.

Issue 4529 has been merged into this issue.

No, the string should be used instead of PID/VID. Add another option and knives will be thrown.

Issue 4515 has been merged into this issue.

please try this build of dolphin if you are having trouble connecting non-nintendo wiimotes (on windows): https://min.us/lVwefgFOiXF8d

I am the owner of the Issue 4529 and i am agree, this is the same Issue. I can test too, but this build /\ from Godisgov is not compatible with my windows 7 X86.

http://min.us/lSiNntdE43FUS

Nothing man, sometimes only show connecting, sometimes connected and no response.

See attached some screens

k, did it show as connected under the wiimote config before this?

Yes, in the Dolphin 3.0 show was connected too. Any doubt just ask.

Guys, we can contact these other companies, what made this 3rd party wiimote works, to get the functional code. I can try here, but will be better a important representative from the project Dolphin.

It's most likely the same problem that phoklore fixed on non-windows. The first problem is just figuring out how to monitor the usb/bt traffic windows is actually sending. Maybe I can do it with vmware.

Can you link me to a page to buy one of these shitty devices?

I can't found a identical device on the web, have a lot versions.

Someone bought from the web?

MatejDro?
justn...@live.co.uk?

Just do a search on ebay for "wiimote". You will get tons of results. If device costs around 20€ or cheaper, It's probably fake one.

You sure you haven't downloaded that recent Bluetooth driver update that screws the ability to connect with HID devices

I saw customers commenting "This wiimote works with the emulator" some fakes works with Dolphin.

My bluetoth and wiimote is working with another programs, i don't thinks is driver.

Problem appears to me in Win7, WinXP and with both USB bluetooth stick and motherboard bluetooth stick. And also problem is here since I started using dolphin, which was about a year ago, I guess.

So i doubt it's trouble in recent drivers.

"My bluetoth and wiimote is working with another programs, i don't thinks is driver."

Invalid response, Do you have the Yi Ruan driver or not.

if so, Remove it from device manager with the Delete Device Drivers box ticked and reboot. Then never install this driver again.

What is the Bluetooth driver recommended?

the one windows installs is preferable, but if your device is a generic CSR you could try the Harmony stack from station drivers.

My Windows installed the Generic Bluetooth Radio, this didn't work.

And I tryed the harmony stack, the wiinote was not found.

Just link to a place to buy one of these things which actually doesn't work with dolphin, ie the one you have.

This for example

http://www.ebay.de/itm/MOTION-PLUS-MOTIONPLUS-WIIMOTE-REMOTE-CONTROLLER-NUNCHUCK-NUNCHUK-NINTENDO-WII-B-/320764301538?pt=de_entertainment_games&hash=item4aaf0ad0e2

I don't found, if you see my issue 4529 you will see the details from the box, i didn't found a box like that, and u have a chance to buy a Wiimote working on Dolphin.

Um, how about a store (not an auction). Where I can get one guaranteed not to work? I'm not taking any chances here...

I can send my Wiimote by mail, but i live far, far away, MatejDro can you send to godisgov?

One I linked is not an auction, you can buy it right away.

I don't think there is any guarantee that it will not work. Even if it would say somewhere "chinese fake wiimote", there is slight chance that it might work without problems. I don't think you can get new original wiimote for 20€, so I think this is 3rd party one.

Chinese knock-offs are not the same as "3rd party"

http://www.nyko.com/products/product-detail/?name=Wand%2B
http://www.amazon.com/Wii-Wand-Nintendo/dp/B0035L0ZCY
http://www.madcatz.com/productinfo.asp?page=442&GSProd=4534&GSCat=214&CategoryImg=Wii_Controllers

Sure, but chinese knock off can still be considered as 3rd party, right? AFAIK nyko wand also suffers from same issues.

the chinese ones tend to hav cheap/faulty parts
3rd party are factory tested before they're sold

they might still hav problems but at least there are no missing pieces

Here is a video I made with my wiimote:
http://www.youtube.com/watch?v=Wkkfw7HDX8M

I think gives a good illustration of the problem

I agree, that hardware is probably way cheaper in those knockoffs, but it does not causes the issue, since wiimote works fine on non-microsoft stack.

We gave you a lot of links above. If you want to buy it from real company, check post from mbrewski, who posted several links to some good 3rd party wiimotes. Otherwise, just go to ebay and buy cheapest wiimote you can find. It's 99,9% a chinese ripoff.

And mbrewski also confirmed in that video that Nyko's wand is suffering from that issue, so if you want to be 100% to get "broken" one, get Nyko's wand.

hmk, I didn't realize it was happening with any 3rdparty one...I thought it was specific to some weird brand.

I'll get a wand+ I guess.

i agree with MatejDro,
I still think this is an issue even if its a real 3rd party as u can see from my video above.

I agree with Nyko's hand, my problems are the same from the video.

Hello, I have the same problem with a 3rd party buying on Ebay. This Wiimote is recognized and seems to workfine with "wiinremote". Recognized by "Dolphin" but not by the game.

IOWin.cpp:IOWrite does:

	case MSBT_STACK_UNKNOWN:
		{
			// Try to auto-detect the stack type
			if (i = WriteFile(dev_handle, buf + 1, 22, &bytes, &hid_overlap))
			{
				// Bluesoleil will always return 1 here, even if it's not connected
				stack = MSBT_STACK_BLUESOLEIL;
				return i;
			}

			if (i = HidD_SetOutputReport(dev_handle, buf + 1, len - 1))
			{
				stack = MSBT_STACK_MS;
				return i;
			}

I have a hunch that that WriteFile is succeeding even with the microsoft stack, and, that a WriteFile in that stack sends a DATA packet instead of a SET_REPORT, and then we're tripping on the same issue I saw on linux.

Can anyone try forcing the stack to MSBT_STACK_MS so that autodetect code isn't reached? You just need to edit WiimoteReal.cpp, and change the line that reads

, dev_handle(0), stack(MSBT_STACK_UNKNOWN)

to:

, dev_handle(0), stack(MSBT_STACK_MS)

rebuild dolphin after the change, and try it out.

also try forcing the other path for good measure:

, dev_handle(0), stack(MSBT_STACK_BLUESOLEIL)

No Windows environment here, sorry. Someone else needs to do the builds.

Hello?

Is for us user do that?

I also have the nyko wand and the same problems

I get issues with both MSBT_STACK_UNKNOWN and MSBT_STACK_MS, however I do not get the error that I pasted in first post anymore. Wiimote will simply not function in game.

MSBT_STACK_BLUESOLEIL will not even detect wiimote (It will show "0 wiimotes detected" and wiimote will not vibrate).

Any news about that?

Maybe try your wiimote with a build of:

http://code.google.com/p/dolphin-emu/source/list?name=Wiimote

Also try the different bt stacks with that build.

Hi, I have the same problem.

This is helped me:
x86: http://www.techspot.com/drivers/driver/file/information/15159/
x64: http://drivers.softpedia.com/get/BLUETOOTH/Toshiba/Toshiba-Bluetooth-Stack-Driver-for-non-Toshiba-Notebooks-80003.shtml

Some theory is there:
http://www.kudzuworld.com/blogs/Tech/20070817A.en.aspx

Hope to help...

Koledix

I have yet to find working x64 link for Toshiba Stack.

But this issue is not about workarounds. I DON'T WANT to use workarounds. I want to use it with Windows stack.

I had the same problem with this china-wiimote:
http://www.ebay.de/itm/MOTION-PLUS-SET-CONTROLLER-WIIMOTE-REMOTE-NUNCHUK-NUNCHUCK-NINTENDO-WII-Weis-/330661226721?pt=PC_Viedeospielzubeh%C3%B6r&hash=item4cfcf1e8e1

Pairing and connecting to Dolphin worked, but it stopped working after pressing a button or starting a game.
Since I'm using Blue Soleil it works without any issues.

I can confirm I have had problem with 3rd Party Nintendo Wiimote ( motion plus - Brand : Gamer ) ..

1. Syndrome : Pairing ends up nicely, wiimote vibrates, first light comes on, yet there is no feedback from the controller whatsoever.

2. Tested : Win 7 ( x86) - Various builds ( including Dolphin-win-x86-v3.0-371 )
   I have also tested Linux Mint 11 ( codename KATYA ) and experienced the very same issue.

3. Solution : ( first fail - solution for that ? ) I've installed bluesoleil, but i got the error message "only MS btstack works with dolphin"

     Success : as mentioned above in this Forum by PETR : i've been able to successfuly test wii motion plus game with no problem  by installing the TOSHIBA stack ( however this is trial period version for 30 days ), so not all the way there yet.
   

4. Conclusion, a noob like me gets a pair of wiimotes , uses cheap usb bt dongle, installs the dolphin, pairs up, .... and it does not work. I would recommend to highlight at the DOLPHIN main web section that 3rd Party controllers are causing issues, and that the appropriate BT stack is required for proper functionality.

Moreover, as I've tested this with linux ( not the latest as of yet, altough )and had similar experience, I was suspecting DOLPHIN to be broken. Even though ppl behind this wonderful project are definitely not to blame, as they cannot possibly seek out every single 3rd party wiimote and assure its compatibility. Yet, if there is any chance on investigation on this matter within the code, it would be greatly appreciated.

I have a strange issue. My wiimote randomly disconnects after I start the game, but not each game... In some games wiimote works perfectly (new super mario, sega superstars ect.). In other games (101 in 1 sports, Grand slam tennis, ect.) wiimote works very bad (for a minute or two ) then disconnects before I press alt+f5 and alt+f6 few times(1 to 20) then disconnects again and again.... There is many games where after disconnects and pressing alt f5 I can play normally before first menu (complete level for example) then again needed to press alt f5. In most situation by pressing HOME MENU button battery indicator going down and disconnect wiimote(led still in 1 and in dolphin status : connected 1 wiimote).
I'm using the RVL-003 wiimote (china clone) and toshiba stack(also trying on BS, MS. same thing). I'm trying different BT dongles too, but same result.
Any ideas??? Any body help???

8phobos, have you tried ticking Alternate Wiimote Timing in the game properties of those games? That might help with the disconnection problems.

Ticking Alternate Wiimote Timing - was first thing I'm try. So this isn't help. There is something else.... Game will work properly 100% if wiimote does not disconnect after I push HOME MENU (in new super mario, for example). But if i push HOME MENU, and wiimote disconnects - same thing will be in game every time (grand slam tennis, ect).
I want to say that the HOME MENU button activate mechanism of disconnections (without pushing HOME BUTTON disconnections still be, but little later).

Hey, Brewski here. (the one who uploaded the video)

I can upload any logs or FIFO if you guys need it.
Just let me know

I'm not entirely sure if this even belongs here, but there's very few places to ask about this, so please forgive me.

I've got a Nyko Wand+ that I'm trying to pair up with my laptop that has the toshiba stack on it. The wand shows up in the bluetooth manager, but it never really connects. The 1 light does not stay on, and the wand does not vibrate, though Windows' device manager says it connected just fine.

I recognize this has little to do with Dolphin specifically, but I'm a little desperate. Thanks for any help.

The Lego Play & Build remote exhibits this behaviour - set wiimote settings for remote #1 to real wiimote, press refresh and the '1' LED lights on the remote and it vibrates, stays connected okay but games don't respond to input.

I've tried this with the MS stack, bluesoleil and Toshiba on Windows 7/x64.

Have also tried on my laptop with the MS stack and a different (built-in) Bluetooth adapter. Not sure where you are but in the UK the Lego controller is pretty cheap, ~£15 on Amazon.

same here, works fine with bluesoleil an toshiba but gets constants real de-sync (wiimote poweroff)with this drivers...dont now why...with both of my controllers happens the same (chinese, from dealextreme)
Ms stack syncs but buttons are not recognized...

Wait, why is this issue on hold?

Any news?

Hi there, im having the same problem as comment 75, im using a 3rd party wiimote with an integrated m+ see http://www.ebay.es/itm/261000500958?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649

When i pair up the wiimote (with all bluetooth stack types, MS, Toshiba, Bluesoleil, etc...) it vibrates, LED 1 on, trying to play any game and it just doesnt respond to any button, i have also a borrowed official wiimote and it just works perfectly but it doesnt have m+ so i cant play games that requires m+

My build is the 3.0 dirty 600, any suggestion or fix would be much appreciated, thx

I managed to make it "work" with Toshiba stack

I have connected the wiimote without the nunchuck and Dolphin said me "connect nunchuck" i connected it and somehow i passed through the calibration but something weird happened, if i move the wiimote when calibrating (on purpose, to make sure the sensor bar works) it says to me to re-check, till here all fine but then the screen "point at center with wiimote" i was pointing center moving wiimote and the cursor wasnt moving at all

I checked if something happens to the wiimote with the wiiremote program and it works fine, it detects the sensor bar and i can use wiimote as if i was using the mouse

Im just going MAD, whats happening to dolphin emulator that my wiimote doesnt work with it, all programs-checking works correctly but dolphin doesnt, its not 3rd partys wiimotes fault i can say, or at least thats my oppinion

Yep just the same problem :
wii are detected on windows, worked with WiiRemote, are detected on Dolphin but not in games.
I first tried real wiimote and it worked.
I buy 3rd party wii from dealextreme like said on post (http://forums.dolphin-emulator.com/showthread.php?tid=20726&pid=199985#pid199985)
My bluetooth : Atheros Communications on a Asus P8z68-v/gen3 mobo (driver v7.2.0.65)

I have the same problem or similar... china wiimotes won't work with windows stack, work with BlueSoleil... but plug the nunchuck make the wiimote nonresponsive.

Windows 7 x64, all versions of dolphin included Dolphin x64 v3.0 Revision 682

Sorry for the bad english hehe Bye

hi...i might be late but anyway i have the same issue as ikuk i have a wiimote dose not work on ms stack but works fine with toshiba stack but in some games(like donky kong jb) wich required a nunchuck the wiimote becomes unresponsive (but in other games works fine with nunchuck (like monster hunter tri) .but i can get it to work if i open wiimote test v 1.8 after starting the game but with some bugs in movment ..but i thought my wiimote is orginal it has nintindo logo and it is white with some words chinese probably,but im not sure because we have a lot of chinese products in my country ,so after reading her i have some douts that it is not orginal .....could someone profisional her confirm this please so i can by another wiimote or not,i can attach fotos for my wiimote if you are interested....sorry for the long talk

same problem Here.... and when i use the toshiba stack... it wont help!

See
http://forums.dolphin-emu.org/Thread-fixing-dolphin-s-wiimote-support

Thanks Billiard26 i did some researches on the web and i found a lot of stacks to use... my BT is a motherboard BT from the ASUS p8p67 Deluxe, it uses the Microsoft driver... well, i've tried the Toshiba stack(after unistalling the mobo driver) and no results, is incompatible with my BT hardware... did some researches again and found a workaround to install and make the Samsung Stack compatible with my BT... no way again........ tried the BlueSoleil and it wont recognize my BT hardware too...
My wiimote is a copy from the original one... its identical the nintendo one... no brands, no names, no nothing.

The problem is... its vibrates when synchronized but all the games wait for the inputs (please press 1.... or please press A) i press the buttons and nothing happens, i've tried to desynchronize and resynchronize, it vibrates but inside the game... nothing works...

sorry bout the ancient scroll that i'm typing.. haha.. i'll try to ask on the forum that you said, but do you have any clues about my prob? i'm stuck whit my BT because i cant workaround with toshibas.... so any help i'll be glad!

BTW Thanks!

I have a 3rd party wiimote from DX as well. I´m using a BT dongle that came with my motherboard that uses Qualcomm-Atheros stack (it still look and feel much like a MS stack). Wiimote doesn´t work at all in Dolphin, I also used Toshiba stack (disconnects occasionaly, jerky movement), BlueSoleil (diconnected almost immediately). It used to work a bit on my older PC with different USB dongle and Toshiba stack (with some disconnecting issues). It however works perfectly with this app called wiinremote (http://onakasuita.org/wii/index-e.html) with source code available on the page... could it help making it work with Dolphin?