Dolphin, the GameCube and Wii emulator - Forums

So how exactly do I fix this? I am having the same problem as well and I am kind of new to all of this

You need to install another bluetooth stack like bluesoleil or widcomm

(03-21-2010, 10:14 PM)matejdro Wrote: [ -> ]You need to install another bluetooth stack like bluesoleil or widcomm

already did this and it didn't work

I filled out a detailed issue on the tracker list.

@Matejdro,
Could you please explain your reasoning as to recommending installing bluesoleil or widcomm drivers after my last edit?? Another user and I just recently confirmed that it's not a driver problem at this level. Reverting to an older build it is working just fine with the older WiiRemote plugin, which typically proves a changing in the code the causes this type of behavior. It is something i can replicate now, and filled out an issue, and i will be helping out at working towards finding the changed that caused this.
Another thing that's been found out, is when using an older build, saving a game save using that build, then reinstalling a newer version and loading that older version made game save, the controller's are working fine still even with newer version. Also pointing to coding issue changes. Don't worry, I will be doing the legwork to find out which specific svn change (maybe line of code) that actually broke this functionality.

@JoeCamel,
Try using an older version SVN build and see if this fixes the problem. Hopefully it will, and also report here your results. I am pretty confident it should though.

(03-22-2010, 03:48 AM)djdafreund Wrote: [ -> ]I filled out a detailed issue on the tracker list.

@Matejdro,
Could you please explain your reasoning as to recommending installing bluesoleil or widcomm drivers after my last edit?? Another user and I just recently confirmed that it's not a driver problem at this level. Reverting to an older build it is working just fine with the older WiiRemote plugin, which typically proves a changing in the code the causes this type of behavior. It is something i can replicate now, and filled out an issue, and i will be helping out at working towards finding the changed that caused this.
Another thing that's been found out, is when using an older build, saving a game save using that build, then reinstalling a newer version and loading that older version made game save, the controller's are working fine still even with newer version. Also pointing to coding issue changes. Don't worry, I will be doing the legwork to find out which specific svn change (maybe line of code) that actually broke this functionality.

@JoeCamel,
Try using an older version SVN build and see if this fixes the problem. Hopefully it will, and also report here your results. I am pretty confident it should though.

I tried downloading svn r4771 and that had no effect.

(03-22-2010, 03:48 AM)djdafreund Wrote: [ -> ]@Matejdro,
Could you please explain,

I had same issue with windows stack, old revision didnt helped, with bluesolei works.

Also try this:

1. Hit F5 (so it will say wiimote connected)
2. start pressing buttons
3. if you lucky "wiimote has been disconnected" message will appear
4. click yes and it whould work
   

Maybe its not revision problem and you were just lucky when using old revision.

Ok. That sound's like your having a different issue then this thread topic problem. Are you able to even connect your WiiRemote to your computer properly? And also, when you go into the WiiRemote plugin it shows "Connected 1 Real WiiRemote" or does it show 0? And when refreshing (try this 1st) It should vibrate once if things are connected right. If not, you are in fact having connection problems in general which could lead to either 2 things. A bad controller (happen to me with my new Nyko controller until i bought a new Nintendo one, and it connected fine after doing that.) or a non-compatible blue tooth device (not all of them are compatible, as reported in a wii remote wiki for pc connection users, the reason is that WiiRemote's aren't exactly 100% blue tooth spec'd compliant. Which explains why this is an exception for being a bit picky with working usb blue tooth devices).

This thread was actually started for WiiRemote's that are connecting just fine, and responding in the controller testing in the plugin, but button's not responding when in games.

@Matejdro,
Ok, i can understand that theory. But it is definately not lucky. I have went back and forth a dozen times to confirm, and confirmed it each and every time. This would remove the 'luck' theory, as it's something actually replicable every time. I agree with ya on the drivers in some cases, if it's connection problems, but this specific topic is for user's that are connecting just fine, and even shows axis's moving fine in the plugin recording. (i might not have been clear enough in the original post.) I was originally having connection problems myself and was told driver issues (Bluesoleil/widcomm) stuff also, and turned out that wasn't even the problem, it happened to be a bad controller, new in the box. I tested it on my friends Wii (i don't have one YET) and also didn't work on his unit. Your help is still appreciated of course, that's how i found out recently about the older revision, by a user mentioning this. And from there i started digging deep and testing a bunch to find out the bug. And can reproduce the problem and fix each time i do it.

Dunno, i have same simptoms with windows stack:

-connects fine (it shows 1 wiimote connected and rumbles when i click refresh)
-recording works fine
-game dont respond

EDIT: just uninstalled blue soleil, i will try old revision now.

Cool, give that a shot. We were using 4970 revision. I am away from home this week end, but i will be working hard on finding the specific code change that caused this, or at least the revision that broke this, don't worry. I am also finding other user's having this same problem as well in a thread in the SVN forum sections. I am about to post my finding's there to help them out as well.

(03-22-2010, 04:20 AM)djdafreund Wrote: [ -> ]Cool, give that a shot. We were using 4970 revision. I am away from home this week end, but i will be working hard on finding the specific code change that caused this, or at least the revision that broke this, don't worry. I am also finding other user's having this same problem as well in a thread in the SVN forum sections. I am about to post my finding's there to help them out as well.

I'm downloading the 4970 version now. I will come back with my results in a minute