(11-08-2015, 07:03 PM)NoZart Wrote:Ah, looks like we have someone who is having issues with it, much like a good friend of mine still has despite trying every mode and firmware to date, TR and non-TR remotes. I wonder what the devs have to say about this anomaly.(11-06-2015, 12:17 PM)Jhonn Wrote: I still didn't find anyone using the right settings (DolphinBar set to Mode 4, Continuous Scanning enabled, Wiimotes set to "Real" in Dolphin 4.0-2241 or newer, preferably the latest development build because 4.0.2 does not work with it) having problems other than the IR LEDs occasionally burning out due overvoltage if you do long play sessions (latest firmware claims to fix this, but knowing DolphinBar inners I'm skeptical about this "fix")...
Now you have. I have been fighting this piece of crap since it came into my home. Randomly it works, but 90% of the time i get "wiimote connected - Wiimote Disconected" at the start of a game. The other modes work ok, using the wiimote as lightgun for mame in mouse mode...
Mode4, Continuous scanning on, wiimote set to real, Build 8113. Trying normal motes and TR ones. Dolphinbar firmware is the one from february.
Waste of money.
Custom Desktop -
CPU: Intel Core i5 3570 3.4 GHz to 3.8 GHz (Turbo Boost)
GPU: MSI nVidia GTX 660 2 GB GDDR5
RAM: 8192MB DDR3 SDRAM PC2 10600 1333MHz
OS: Windows 7 Professional 64-bit
HDD: 1 TB Western Digital 7200RPM HDD
CPU: Intel Core i5 3570 3.4 GHz to 3.8 GHz (Turbo Boost)
GPU: MSI nVidia GTX 660 2 GB GDDR5
RAM: 8192MB DDR3 SDRAM PC2 10600 1333MHz
OS: Windows 7 Professional 64-bit
HDD: 1 TB Western Digital 7200RPM HDD