(08-21-2016, 05:53 AM)rebirthflame Wrote: [ -> ]I am having exacty the same issue, i have an official wiimote and as above the home button works. Weirdest thing is when i press the home button the pointer then appears and is usable, when i press the home button again and go back to the game the pointer disappears.
I get the rumble but in the settings screen it shows that a wiimote cannot be detected.
I have this exact same problem. I am using the 2 in 1 motion plus remote. (the 3rd party one)
(08-21-2016, 09:11 PM)Caturix Wrote: [ -> ]How did you know wich package is missing? And is there any current dependency list? Dont want to bother you with every error I get.
It's (sort of) indicated in the error message. Then a Google search for the file name should tell you which package it is
There is a list, but I think it's only for Debian-based distros (which isn't the case for Suse).
Also, as JosJuice says, you need a newer compiler (your version of Suse has GCC 5, but you have to install it as it uses 4.8 by default).
Ok finally after some trouble i got Dolphin running. Also it refreshed my linux knowledge (didnt use it for about 8 or 10 years). But enaugh offtopic now.
Dolphin is working and exactly as in windows, Dolphinbar works great in mode 1+2, but not in mode 4.
But on linux the wiimote dont even rumble, and is not displayed in wii menu. Maybe I did anything wrong? Or is it just the unsupported wiimote this time? I wonder, cause usely Linux should have better support, but it works even worse then on windows.
The guide sais you need libbluetooth-dev for real Wiimote support, i only got the non-dev one. But cause i use Dolphinbar, i dont need this. Or am i wrong?
Isn't there currently a complete lack of DolphinBar (mode 4) support for Linux...? I should probably have commented on that earlier in the topic, but I wasn't paying much attention :/
(08-17-2016, 04:17 AM)leolam Wrote: [ -> ]so if you don't mind installing a Linux distribution and you want to try, you can build it with:
Code:
git clone https://github.com/dolphin-emu/dolphin
cd dolphin
git fetch origin pull/4090/head:hidapi
git checkout hidapi
then follow the normal build instructions for Linux.
Sounds to me like a dev build wich adds Dolphinbar support to Dolphin.
It should at least rumble, otherwise it means Dolphin hasn't even detected it. Did you build master or the hidapi PR? You need the latter for DolphinBar support.
If you built the latter, and it doesn't work: enable logs (View → Show Log Configuration), select "Error" as the verbosity level, tick Log to Console and Window, and make sure "Wiimote" is checked. Then check the logs and see if there's any error.
I'd guess Dolphin doesn't have permission to use the devices. You need to install an udev rule for that.
(also, make sure Continuous Scanning is enabled and you have at least one Wiimote set to "real Wiimote")
Alternatively, if you have a Bluetooth adapter (dongle or built-in), you should be able to simply press 1+2 on the Wiimote and it'll connect.
(08-23-2016, 04:27 AM)Caturix Wrote: [ -> ]Sounds to me like a dev build wich adds Dolphinbar support to Dolphin.
Yes, you're right. Seems like the time when I wasn't paying attention was now, not before
(08-23-2016, 04:32 AM)leolam Wrote: [ -> ]I'd guess Dolphin doesn't have permission to use the devices. You need to install an udev rule for that.
Code:
09:38:618 /home/flix/dolphin/Source/Core/Core/HW/WiimoteReal/IOhidapi.cpp:20 E[Wiimote]: Could not connect to Wiimote at "/dev/hidraw4". Do you have permission to access the device?
09:38:618 /home/flix/dolphin/Source/Core/Core/HW/WiimoteReal/IOhidapi.cpp:20 E[Wiimote]: Could not connect to Wiimote at "/dev/hidraw5". Do you have permission to access the device?
09:38:618 /home/flix/dolphin/Source/Core/Core/HW/WiimoteReal/IOhidapi.cpp:20 E[Wiimote]: Could not connect to Wiimote at "/dev/hidraw6". Do you have permission to access the device?
09:38:618 /home/flix/dolphin/Source/Core/Core/HW/WiimoteReal/IOhidapi.cpp:20 E[Wiimote]: Could not connect to Wiimote at "/dev/hidraw7". Do you have permission to access the device?
Yes that is the problem. I read a lil about udev rules, but couldnt figure out how to set it (what to write in the udev file)?
And the best thing is, I ran dolphin with root rights, and finally the Wiimote worked
Really great. So it is a dolphin problem, not a wiimote problem.
Ok... another problem...
The Wiimote worked well in Monster Hunter Tri.
But then i tried Zelda: Skyward Sword: it could not detect the nunchuck, so i couldnt start it. mh3 detected the nunchuck...
Also Dolphin dont detect the Wiimote when the nunchuck is plugged in. When i plug off the nunchuck and plug it back in when the Wiimote is detected, it works though (in Mh3, not in Zelda).
Also the the udev rule does not work (did the tests as root).