[request] Add a log warning when a virtual Xbox Controller is being used but XInput Slot 1 is not connected

[Kanuan]

Though I know DS4Windows can't know exactly which Xinput Slot a xbox controller is associated to, would it be possible to at least check if there is something connected to Xinput slot 1 after a virtual xbox controller plug-in event?

This would make easier to troubleshoot errors and give users a general direction on what could be the possible problem they are facing since the whole Xinput slot issue is not known by the average user.

[Ryochan7]

ViGEmBus technically has a way to grab which XInput slot a virtual Xbox 360 controller is using. The biggest issue is that the query is only stable in driver version 1.17.333.0; older versions would constantly error out when trying to grab that info. I didn't want to have to take another ViGEmBus version difference into account and I'm sure people would just get confused and complain anyway. This is a feature that has been filed under we can't have nice things.

Someone submitted a pull request that attempted to add the feature in but it was a bit incomplete.

#2070

[Kanuan]

My suggestion is more related to DS4Windows just directly checking if there is anything connected to XInput Slot 1 (and not each controller state) just like how it's done by the Xinput Checker tool. Something like:

1. DS4Windows Plugs-in a Virtual Xbox controller
2. Checks if there is something connected to XInput Slot 1 (not necessarily the connected controller)
3. Generate warning in the log if not