search

joaorb64 / joycond-cemuhook

Support for cemuhook's UDP protocol for joycond devices
MIT License
139 stars 19 forks source link

Can't assign motions in Dolphin #56

Open DemonicSavage opened 2 years ago

DemonicSavage commented 2 years ago

When I start joycond-cemuhook, it detect both my joycons perfectly: image

Yet in Dolphin, I cannot seem to be able to assign motions to Up, Down, Left, Right... in Motion Input. There are two DSUClients, I assume one for each Joy-Con (even though the Joy-Cons are made into a single one by joycond)

Am I doing something wrong here, or is this a bug?

joaorb64 commented 2 years ago

You have to use one of them for the wiimote and the other for the nunchuck if that's the case.

Usually I just use the default settings because it's just plug and play; it already has these options configured and you just have to pick the DSU from which motion comes from.

There's this guide on the wiki, even though I believe the config interface has changed a lot since when I made this: https://github.com/joaorb64/joycond-cemuhook/wiki#Dolphin

Please let me know if this isn't your case.

DemonicSavage commented 2 years ago

These are the instructions I've been following. The default settings yield no motion controls for me.

DemonicSavage commented 2 years ago

These appear in the log quite frequently:

[udp] Client connected: 127.0.0.1:36360
[udp] Client connected: 127.0.0.1:47514
[udp] Client connected: 127.0.0.1:53697
[udp] Client connected: 127.0.0.1:38342
[udp] Client disconnected: 127.0.0.1:36360
[udp] Client disconnected: 127.0.0.1:47514
[udp] Client connected: 127.0.0.1:45918
[udp] Client connected: 127.0.0.1:43796
[udp] Client disconnected: 127.0.0.1:53697
[udp] Client disconnected: 127.0.0.1:38342
[udp] Client connected: 127.0.0.1:35679
[udp] Client connected: 127.0.0.1:47799
[udp] Client connected: 127.0.0.1:59035
[udp] Client connected: 127.0.0.1:54143
[udp] Client connected: 127.0.0.1:37490
[udp] Client connected: 127.0.0.1:53660
[udp] Client connected: 127.0.0.1:41125
[udp] Client connected: 127.0.0.1:57866
[udp] Client connected: 127.0.0.1:40649
[udp] Client connected: 127.0.0.1:54371
[udp] Client connected: 127.0.0.1:33009
[udp] Client disconnected: 127.0.0.1:45918
[udp] Client disconnected: 127.0.0.1:43796
[udp] Client disconnected: 127.0.0.1:35679
[udp] Client disconnected: 127.0.0.1:47799
[udp] Client disconnected: 127.0.0.1:59035
[udp] Client disconnected: 127.0.0.1:54143
[udp] Client disconnected: 127.0.0.1:37490
[udp] Client disconnected: 127.0.0.1:53660
[udp] Client disconnected: 127.0.0.1:41125
[udp] Client disconnected: 127.0.0.1:57866
[udp] Client disconnected: 127.0.0.1:40649
joaorb64 commented 2 years ago

What is your Dolphin version? I'll try to test this on my end and try to match versions.

I'm assuming these connections/disconnections are being made by the dolphin configuration UI, but I will also check on that.

DemonicSavage commented 2 years ago

I'm on Dolphin 5.0-15360.

joaorb64 commented 2 years ago

Sorry for the delay here, I'm having issues running Dolphin on Ubuntu 21.10. There's a bug related to snap apps and Nvidia drivers affecting me, but I'll try to install from elsewhere and try this today.

joaorb64 commented 2 years ago

So I connect my controllers and open Dolphin image

I go into motion input, if I click default it shows this: image

I have joycond in the alternate input sources... image

And as soon as I select a DSU device on the top-left corner, the spheres start reacting to motion image

I'm using a 5.0-14790 appimage I found online.

dracula99gr commented 2 years ago

These dots do not move to me as well! image Using the latest dev build 16287(that i have just compiled directly from the source code) [Input via dsu seems to work but motion doesn't]

EDIT: I had to manually assign via right click every input that required motion... bruh on windows they got detected automatically via ds4windows xD image

Also accelometer sensor seems to be the real gyro for some reason o.O image