I haven't dug through the code, and I don't see any debug output, so unfortunately I can't really speak to what it's doing to throw things off the rails. A few seconds after the output window shows 'Starting poll thread.', the Bluetooth connection is terminated, and the controller doesn't attempt to reconnect itself the output window doesn't give any more useful information than simply saying 'Dropped.'.
#BETTERJOY GITHUB PRO#
With the third-party controller finder in Version 6.4β, the controller shows up as 'Wireless Gamepad' when connected you can move it to the Switch Controllers window and assign it as a Pro Controller, but after applying it things go south. Hard to tell how it's handled in Windows, but the udev rules in Valve's Linux input repository work around the lack of proper IDs (the only supported gamepad not to have them, that I can see) by looking for the name the device provides ( Lic Pro Controller) over Bluetooth, which seems to be unique.
#BETTERJOY GITHUB MOD#
The controller does seem to be recognized as a Switch Pro Controller by Steam, gyroscope and all. Joycons are connected using the latest version of BetterJoy and theyre being read correctly by Steam for other games, so Im guessing the mod loader is doing something weird. If your code requires VID/PID in a standard format, you're gonna have a bad time. There's also Bluetooth product IDs and Bluetooth vendor IDs listed, but they're each set to 0000. Windows' device manager shows a hardware ID of BTHENUM\Dev_ 0A1B2C3D4E5F, where the last chunk of the string is the device's unique address, stripped of colons. The controller connects exclusively via Bluetooth and runs on AA batteries - there's zero USB interfacing at all. You've probably figured it out already, but the reason no one's been able to provide the product and vendor ID is because this device doesn't have any, at least not in the traditional PCI/USB format.
No idea if this issue's being monitored at all, but I'll toss in my two cents.
0 kommentar(er)
