You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering an odd issue where when cemu is opened and joycond-cemuhook stops recognizing the switch Pro Controller before it connects to the cemu UDP client. It should be noted that this does not occur with bluetooth connections, as those seem to work as intended. I will post an example of what happens:
sudo joycond-cemuhook -v ✔ 1m
Debug: Kernel module 'hid_nintendo' is installed.
Debug: Kernel module 'hid_nintendo' is loaded.
Debug: Using kernel module 'hid_nintendo'
Looking for Nintendo Switch controllers...
Debug: Started UDP server with ip 127.0.0.1, port 26760
Debug: Found dbus interface for battery level reading. Value: 100.0
================= ('127.0.0.1', 26760) ================
Device LED status Battery Lv MAC Addr
1 🎮 Pro ■ ■ □ □ □ 100.0 █ 60:6B:FF:1C:00:B4
2 ❎
3 ❎
4 ❎
=======================================================
Debug: Motion events task started device /dev/input/event22, name "Nintendo Switch Pro Controller IMU", phys "usb-0000:08:00.3-1/input0"
Debug: Input events task started
Debug: Battery level reading thread started
Debug: Motion events task ended
Debug: Input events task ended
Debug: Battery level reading task ended
Device disconnected: Nintendo Switch Pro Controller
================= ('127.0.0.1', 26760) ================
Device LED status Battery Lv MAC Addr
1 ❎
2 ❎
3 ❎
4 ❎
=======================================================
[udp] Client connected: 127.0.0.1:58905
The only additional info i could find in logs is as follows:
systemd Started Cemu - Wii U Emulator.
org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter
org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter
Now, frankly I am not sure whether this is a Cemuhook, joycond, cemu, or KDE issue, but any further guidance in narrowing this down would be very appreciated.
The text was updated successfully, but these errors were encountered:
I'm encountering an odd issue where when cemu is opened and joycond-cemuhook stops recognizing the switch Pro Controller before it connects to the cemu UDP client. It should be noted that this does not occur with bluetooth connections, as those seem to work as intended. I will post an example of what happens:
The only additional info i could find in logs is as follows:
Now, frankly I am not sure whether this is a Cemuhook, joycond, cemu, or KDE issue, but any further guidance in narrowing this down would be very appreciated.
The text was updated successfully, but these errors were encountered: