Dolphin, the GameCube and Wii emulator - Forums
Linux and inputs. - Printable Version

+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Development Discussion (https://forums.dolphin-emu.org/Forum-development-discussion)
+--- Thread: Linux and inputs. (/Thread-linux-and-inputs)

Pages: 1 2

RE: Linux and inputs. - ulao - 12-30-2015

I looked for /etc/udev/rules.d/51-nintendo.rules but it was not there, so I created it. I changed the vip/vid and running dolphin still shows no controllers. If I run
gksudo /usr/games/dolphin-emu
I get a prompt back, no action took place.

I check both of those libs and they are already installed.

RE: Linux and inputs. - leolam - 12-30-2015

Yes, you have to create that file if it doesn't exist. Don't forget to reload udev afterwards (and check that the /dev/input/eventX files really have the correct permissions).

For gksudo, are you sure Dolphin's binary is at /usr/games/dolphin-emu? That's where it is for me with the Ubuntu PPA, but it may vary for you. Use which dolphin-emu to check.

RE: Linux and inputs. - ulao - 01-03-2016

to get gksu to work I had to first su and I couls su because the root unix password was not set. Now that the password is set I'm able to run dolphin with root permissions. This make the controller work but force feed back still fails.

RE: Linux and inputs. - leolam - 01-03-2016

That's… weird. Are you running it on a Debian or Debian-based distribution like Ubuntu or…? If so, gksudo should prompt you for your password, not root's.

Anyway, since running as root makes the controller work, this means that it is a permission issue. Just configure your system to grant your regular user the permissions to read the input devices and it should work fine.

As for force feedback, have you configured rumble in the controller settings in Dolphin? If it still won't work, try to right click on Rumble => Motor, then try every choice you have.

RE: Linux and inputs. - ulao - 01-04-2016

Yeah testing on ubuntu and it asks for a password but the password just closes the box. Once I ran in su no password was asked - gofigure.

Ok FFB, sadly I'm proly the most advanced user on the matter here. I say that because I have been working with FFB since 06 as I'm a USB developer. I have not worked on Dolphin but here is what I know.

Window: Watching USB traffic in windows when running dolphin or hitting refresh, shows (in laymans terms)
Dolphin: Hey controller are you a FFB device
Device yes I am,
Dolphin: Wacha got?
Device: constant, sine, square
Dolphin: Cool, your all set
Than I pick what I want and test it, works.

Linux:

Dolphin: ....
Device ????,
Nothing shows in the list

Mac:
Dolphin: ....
Device ????,
Nothing shows in the list

Points of interest.
Running fftest in linux
fftest : Hey controller are you a FFB device
Device: yes I am,
Test and it works

So I have concluded that FFB works in ubuntu but Dolphin never asks for it, it's like it was never developed to do so (hence why I'm here in the dev forums). Can anyone check the code? The only way to know if a controller is FFB is to either A, check the driver or B ask the device. Since this is a %100 HID ( no 3rd party drivers) device I bet the linux build is just not asking the controller like it does in windows.
In DX none managed code it looks like this

Code:
   // Look for a force feedback device we can use  
   if( FAILED( hr = g_pDI->EnumDevices( DI8DEVCLASS_GAMECTRL,    
                                        EnumFFDevicesCallback, NULL,    
                                        DIEDFL_ATTACHEDONLY | DIEDFL_FORCEFEEDBACK ) ) )    
       return hr;  
 
   if(!g_pJoystick )  
   {  
       MessageBox( NULL, _T("Force feedback or joystick device not found. ")  
                         _T("The sample will now exit."),    
                         _T("Joystick"), MB_ICONERROR | MB_OK );  
       EndDialog( hDlg, 0 );  
       return S_OK;  
   }

Not sure about SDL.

This could be why FFB does not work for osx
http://faq.iracing.com/article.php?id=209 UPADTE<--- All that did was cripple my device. I think I'd need to make one for HID PID
more talk about that here
http://www.macworld.com/article/1008250/immersion.html

RE: Linux and inputs. - leolam - 01-05-2016

So you have nothing in the Output list when you configure Rumble? I'm not sure that's a Dolphin issue since I use it with a controller that has force feedback (a Wiimote connected via Bluetooth, with the controller devices managed by xwiimote) and I definitely can use Rumble (I have constant, sine, square as choices).

RE: Linux and inputs. - ulao - 01-05-2016

Does the controller have a driver?

RE: Linux and inputs. - leolam - 01-05-2016

Well, the Wiimote's driver is xwiimote, which I linked above.

RE: Linux and inputs. - ulao - 01-06-2016

Yeah any driver based device should work, its the HID based devices like the old MS sidewinder that do not work. I'm not looking for help with the MS sidewinder just wanting to see why SDL + Dolphin does not enumerate the FFB layer of HID-PID devices. I think only a SDL dev can answer this. I think its a permission issue but running dolphin with gksu should have pretty much ruled that out. I may have to to another usb log to be sure its not the device.