hellbringer616 Wrote:to clarify, He means 4.0-4.0.2 the stable versions. If you're using the SVN builds try the most recent, You should see a performance boost, as well as get your Wiimotes working.
*facepalm* That was remarkably unhelpful, not to mention patronizing. I do not need a newbie to come and "clarify" things. Besides, he complained about his wiimotes being assigned wrong, not that they
aren't working period, which is a big hint that he is not in fact using 4.0 or 4.0.2, and was referring to "4.0 era builds" instead of 4.0 directly. Nevertheless, I wish him to specify the build he is using for a stupidity check. I find it best not to underestimate stupidity and check for it just in case.
And Dolphin has not had "SVN releases" since the move from
SVN to
git years ago.
(09-29-2014, 09:27 PM)MaJoR Wrote: [ -> ]cdenfert Wrote:So it seems that this is a bug in 4.0?
Whoa whoa, what version of dolphin are you using? Wiimotes connected to the Dolphinbar won't work period in 4.0!
Hi,
I am using the 4.0.3395 build.
Whoa, Sorry man I didn't mean to come off as patronizing, I just wanted to let him know that you meant the stable versions don't have functioning DolphinBar Support, Not the development builds.. "Dolphinbar won't work period in 4.0" to me sounds like it won't work in any version of 4.0, All the dev builds are 4.0-x. I work in IT and deal with people who know nothing of programs, Over at the PCSX2 forums i also see people not understanding what a dev build is. So i just wanted to let the OP know you meant the stable releases don't work, But Dolphin 4.0-3000 or higher it does (i don't know the exact version number)
Lack of posts doesn't mean I'm a newbie, I am certainly not as knowledgeable in the subject as you I'm sure. But i know more then the average user, I just never post just read. Though i get there a lot. i often times am a member for years and have less posts then people who started only a few months ago, Just don't post is all.
Anyway, to touch on the SVN, a lot of people (in my circle anyway, Not everyone) calls it SVN instead of Dev. Slip of the tongue (so to speak) there.
Again, Sorry i came off as rude, it certainly wasn't what i was intending
(09-30-2014, 03:13 AM)cdenfert Wrote: [ -> ] (09-29-2014, 09:27 PM)MaJoR Wrote: [ -> ]cdenfert Wrote:So it seems that this is a bug in 4.0?
Whoa whoa, what version of dolphin are you using? Wiimotes connected to the Dolphinbar won't work period in 4.0!
Hi,
I am using the 4.0.3395 build.
try the 4.0.2241 doesn't work too. Only the 3.5 works.
note: Dolphinbar is upgrade to 0.3 firmware.
(09-30-2014, 10:27 AM)cdenfert Wrote: [ -> ] (09-30-2014, 03:13 AM)cdenfert Wrote: [ -> ] (09-29-2014, 09:27 PM)MaJoR Wrote: [ -> ]cdenfert Wrote:So it seems that this is a bug in 4.0?
Whoa whoa, what version of dolphin are you using? Wiimotes connected to the Dolphinbar won't work period in 4.0!
Hi,
I am using the 4.0.3395 build.
try the 4.0.2241 doesn't work too. Only the 3.5 works.
note: Dolphinbar is upgrade to 0.3 firmware.
Same problem on my 2 computers.
Anyone has this problem?
I have a strange problem with my wiimotes (originals) with the DolphinBar too. Current developer builds do not indicate wiimotes connected in the configuration screen (unlike 3.5), although they do work in most games. Having issues with 2-player Donkey Kong Country Returns - second wiimote has four lights on but completely undetected by the game. Metroid Prime keeps saying 'lost connectivity'.
I upgraded to dolphinbar firmware 03 when I bought it two weeks ago but can't find a way to downgrade to firmware 02 to test.
Anyone tried this with firmware 02?
Hello,
i already have the same problem with the lastest build: 4.0-3769.
FWIW, I'm using the DolphinBar successfully with 4.0.3644. I updated its firmware to 3.0 per the instructions on the Mayflash website, and made sure its LED was on the "4" position. In Dolphin, I configured the WiiMote to be a "real Wiimote" and enabled "continuous scan." For me, continuous scan was key - I was also confused and thought it didn't work until I enabled that.
(10-23-2014, 07:17 AM)fkane Wrote: [ -> ]FWIW, I'm using the DolphinBar successfully with 4.0.3644. I updated its firmware to 3.0 per the instructions on the Mayflash website, and made sure its LED was on the "4" position. In Dolphin, I configured the WiiMote to be a "real Wiimote" and enabled "continuous scan." For me, continuous scan was key - I was also confused and thought it didn't work until I enabled that.
it works fine with one wiimote. The problem is wiimotes being assigned wrong when using 2 or more wiimotes.
Everyone, please stop dumping in unrelated dolphinbar stuff into this thread. If you have an issue please make your own thread. From this point on, I'll be deleting any post that isn't directly related to cdenfert and his inquiry.
/being a moderator
cdenfert - On my DolphinBar with v2 firmware in 4.0-3587, I had no issues just now playing against myself in wii sports. I tried all kinds of different connection methods, and my first wiimote showed as Wiimote 1, and my Second as wiimote 2. It didn't matter which one I used as first player or anything, it just went with what I connected as. I could update to v3 to try it, but uh, yea, don't want to do that.