Hey there,
I've been using VirtualHere on the free tier for a couple weeks to connect a keyboard to my PC and it worked pretty flawlessly, so was happy to splash out to get the license so I could connect my controllers too. Rather foolishly I didn't test the controller itself before getting the license and have been trying to get it to work with my DualSense controller but have gotten nothing but issues.
I have the server running the CPU optimised build on a Raspberry Pi 3 Model B Rev 1.2 running Raspbian minimal on 6.1.24-v7+. My client is a Windows 11 PC. The Pi is connected directly to my router via ethernet, the client is over WiFi. Whenever I plug the DualSense in, its detected perfectly fine by both the server and the client. However, even the act of plugging it in is enough to cause a bit of disruption - my KB+M device running through VirtualHere starts to noticeably lag for a few minutes. Eventually it settles down though. However, once I try to actually use the controller in a game - in this instance, The Last of Us Part I - it might work as far as getting past the menu, but once in game, it causes the game audio to crackle horribly, inputs get stuck on and eventually causes both the controller and my other KB+M device to completely stop working until I restart one or both of the client and server. I think it's something to do with how the controller uses the audio for haptic feedback, and even in the client software the controller shows up with a speaker icon. When I disable the built in speakers/mic on the controller in the Windows audio settings it seems to behave much better. Can't seem to find anything in the logs that indicates an error except occasionally seeing `Error 22 discarding urb 0x15aafe0 for device /sys//devices/platform/soc/3f980000.usb/usb` or something along those lines, but I get that for other devices, not just the DualSense.
I would really love for this to work as it would be the perfect solution for me. Any ideas for what I could try to get this working? Server is as up-to-date as it can be AFAIK.
Thanks,
Eoin
.
I think is very likely the pi3b+ is limited with its network port. Everything is going through a single USB port - All the controllers as well as the network. All pi's before 4 use the CPU USB port for everything usb and network. So i think its basically overloading the port with data and large latency spikes are occuring because of this.
You really need to use a pi4.