Homepage › Forums › How-to and troubleshooting › C25 Joy Cons help needed
Tagged: Third Party Joy Cons C25
- This topic has 0 replies, 1 voice, and was last updated 4 years, 1 month ago by MadBee71.
-
AuthorPosts
-
2020-12-21 at 23:39 #39613MadBee71Participant
Hi Greg!
I got a new pair of third party Joy Cons (C25 Joy-Con Dual Controllers Blue-Red (NSW)), EAN: 4020628711092
They paired successfully via bluetooth in Windows 10, but they never showed up in driver4vr tracker manager.
In the main page Devices list there are ID:
Nintendo Switch Pro Controller
030000007e0500000920000000000000But in Windows 10 device manager shows:
Joy-Con (L) Device
Device BTHENUM\Dev_98B6E98CBFD7\7&166e18af&0&BluetoothDevice_98B6E98CBFD7 was configured.
Driver Name: bth.inf
Class Guid: {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.662
Driver Provider: Microsoft
Driver Section: BthGenericDevice.NT
Driver Rank: 0xFF2000
Matching Device Id: BTHENUM\GENERIC_DEVICE
Outranked Drivers:
Device Updated: false
Parent Device: BTH\MS_BTHBRB\6&154533db&0&1Siblings:
BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E98CBFD7_C00000000
BTHENUM\{00001200-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E98CBFD7_C00000000
BTHENUM\Dev_98B6E9DD90B7\7&166e18af&0&BluetoothDevice_98B6E9DD90B7
BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E9DD90B7_C00000000
BTHENUM\{00001200-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E9DD90B7_C00000000and
Joy-Con (L) Device
Device BTHENUM\Dev_98B6E9DD90B7\7&166e18af&0&BluetoothDevice_98B6E9DD90B7 was configured.
Driver Name: bth.inf
Class Guid: {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.662
Driver Provider: Microsoft
Driver Section: BthGenericDevice.NT
Driver Rank: 0xFF2000
Matching Device Id: BTHENUM\GENERIC_DEVICE
Outranked Drivers:
Device Updated: false
Parent Device: BTH\MS_BTHBRB\6&154533db&0&1Siblings:
BTHENUM\Dev_98B6E98CBFD7\7&166e18af&0&BluetoothDevice_98B6E98CBFD7
BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E98CBFD7_C00000000
BTHENUM\{00001200-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E98CBFD7_C00000000
BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E9DD90B7_C00000000
BTHENUM\{00001200-0000-1000-8000-00805f9b34fb}_VID&0002057e_PID&2009\7&166e18af&0&98B6E9DD90B7_C00000000Can you solve this problem with these infos and make these 50% cheaper controllers work with Driver4VR, please?
-
AuthorPosts
- You must be logged in to reply to this topic.