@nefarius said in Bluetooth Filter Driver for DS3-compatibility - research notes:
- Profile driver denies connection with
CONNECT_RSP_RESULT_PSM_NEG and instructs filter to disable itself for like 10 seconds
- User presses PS button on DS4 to retry connection
- Connection now successful due to filter being temporarily disabled
- Timer enables filter again on its own to minimize required user interaction
I haven't found a way to reject a connection attempt without the DS4 giving up so the only remaining inconvenience would be the user having to connect the controller twice if the filter is active. Other than that I think we thought off every possibility to minimize the negative impact on user experience.
What do you think?
Great job! Thank you for the efforts you put in this along with the team.
I'm not so into technical stuff, but I'll try my best here.
The whole "reconnect" concept reminds of InputMapper 1.6. On the other hand, DS4Windows 1.7.5+ reestablishes the connection without the user initiating it manually. Just a reminder, both of these programs use ViGEm drivers.
How does one (DS4W) achieves it while the other doesn't?