inputmapper xinput test status not connected

#Inputmapper xinput test status not connected how to
#Inputmapper xinput test status not connected Bluetooth
#Inputmapper xinput test status not connected mac

Makes no sense why BT % is showing 0, but shows the actual controller MAC. 07:42:09: Controller 1 is using Profile 'New' 07:42:09: Plugging in X360 Controller for input #1 07:42:07: Unplugging X360 Controller for input #1 07:42:07: Closing connection to ViGEmBus 07:41:33: Controller 1 is using Profile 'New' 07:41:33: Plugging in X360 Controller for input #1 07:41:32: Unplugging X360 Controller for input #1 07:41:32: Closing connection to ViGEmBus 07:41:30: Controller 1 is using Profile 'New' 07:41:15: Controller 1 is using Profile 'Default' 07:41:15: Plugging in X360 Controller for input #1 07:41:09: Unplugging X360 Controller for input #1

07:41:09: Closing connection to ViGEmBus 07:38:45: Controller 1 is using Profile 'Default' 07:38:45: Plugging in X360 Controller for input #1 This should be related to the issue I am having as its not 'reporting' right. The only thing I notice that is quite odd is the Battery % is showing 0 when in BT.

#Inputmapper xinput test status not connected mac

Yeah it is showing the MAC address and everything. You could try to run a special debug version also to generate loooooots of additional debug messages about the gamepad connection and handshaking process. If that works then attach the problematic profile file here for closer inspection.ĭoes 'Controllers' tab page in DS4Windows app show the status of controller and battery readings? (xx:xx:xx:xx:xx:xx MAC identifier)? Please try with a new default profile (ie. The logfile doesn't show any obvious problems. UNTICK this option if you use exclusive mode (and untick it anyway because using that option prevents the use of virtual output controller).Īnd if you use a profile in dualshock4 output mode (not as default xbox360 mode) and Steam client then check the following doc page.Īnyway. 07:18:22: Controller 1 is using Profile 'Default'Ĭheck 'Use DInput Only' option in a profile. 07:18:22: Plugging in X360 Controller for input #1 07:18:21: Unplugging X360 Controller for input #1 07:18:21: Closing connection to ViGEmBus 07:18:18: Controller 1 is using Profile 'Default' 07:18:18: Plugging in X360 Controller for input #1 07:18:18: Unplugging X360 Controller for input #1 07:18:18: Closing connection to ViGEmBus 07:14:29: Controller 1 is using Profile 'Default' 07:14:29: Plugging in X360 Controller for input #1 07:14:29: Unplugging X360 Controller for input #1 07:14:29: Closing connection to ViGEmBus 07:14:16: Controller 1 is using Profile 'Default' 07:14:16: Plugging in X360 Controller for input #1

#Inputmapper xinput test status not connected Bluetooth

Two separate computers too so It cant be the Bluetooth adapter. I also tried HIDE DS4 and it is in exclusive mode, still not working. The weirdest thing also is it shows in the joy.cpl as 'ok' but nothing freaking works.

#Inputmapper xinput test status not connected how to

General Troubleshooting doc page talks more about various potential issues and how to diagnose and provide more details here (log files etc). Option 1: 'Hide DS4 Controller' option in DS4Win app (aka exclusive mode) or Option2: 'HidGuardian' if exclusive mode doesn't work in your environment.

This is a WindowsOS issue and not reallly DS4Windows app issue) There are two alternative ways to hide the original physical controller. Please go through those doc pages for more info about hiding the original physical controller from games (especially important in BT mode because BT device will be seen by other apps as 'dead controller'. (Hide-DS4-Controller-config-option)-tips-and-issues