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
After going through all the hurdles to get the program compiled correctly, and it recognizes the pro controller, it creates a virtual 360 controller device successfully.
However, no input is recognized in Devices & Printers, and the Pro Controller's charging LED is flashing, which suggests to me that it's receiving some unexpected data and crapping out.
The command line output looks normal as you can see:
D:\Stuff\switch-pro-x-master\x64\Release>switch-pro-x.exe
FOUND PRO CONTROLLER: \?\hid#vid_057e&pid_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
REMOVED PRO CONTROLLER: \?\hid#vid_057e&pid_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
FOUND PRO CONTROLLER: \?\HID#VID_057E&PID_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
REMOVED PRO CONTROLLER: \?\HID#VID_057E&PID_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
The text was updated successfully, but these errors were encountered:
After going through all the hurdles to get the program compiled correctly, and it recognizes the pro controller, it creates a virtual 360 controller device successfully.
However, no input is recognized in Devices & Printers, and the Pro Controller's charging LED is flashing, which suggests to me that it's receiving some unexpected data and crapping out.
The command line output looks normal as you can see:
D:\Stuff\switch-pro-x-master\x64\Release>switch-pro-x.exe
FOUND PRO CONTROLLER: \?\hid#vid_057e&pid_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
REMOVED PRO CONTROLLER: \?\hid#vid_057e&pid_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
FOUND PRO CONTROLLER: \?\HID#VID_057E&PID_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
REMOVED PRO CONTROLLER: \?\HID#VID_057E&PID_2009#6&35c399e5&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
The text was updated successfully, but these errors were encountered: