11/12/2023 0 Comments Sekiro ds4windowsRebased the custom changes on top of the current upstream ViGEmClient and ViGEm.NET code. Getting around to working on those prerequisites. Would still keep it in as ViGEmBus 1.17.333.0 would still need it and it should not affect the behavior in the current release. On the plus side, it looks like the way notification data is sent to clients has changed so maybe the old notification queue in the ViGEmClient isn't really necessary for the most recent version of ViGEmBus (1.18.367.0). I reported on the initial problem on the ViGEmBus repo back around February 2021 IIRC the issue is still open on the ViGEmBus GitHub issue tracker. That byte is necessary to determine if a payload should be considered a lightbar change, rumble motor change, or possibly both. It still looks like there is no way to retrieve the full output report payload so the features bytes from the report can be checked. Been a while so I should double check and make sure that is the case.Īlso, I just checked over the current ViGEmBus code and the root problem with DS4 vibration has not been addressed. Check HidHide’s guide for more info on that.I believe I re-enabled the vibration routine for the virtual DS4 shortly before the rage quit with version 3.0.18. You can check if you have HidHide installed by opening Windows’ Apps and Features and searching for it, though if it do is installed then it’s probably just not properly configured to grant DS4Windows access to hidden controllers. Its use along DS4Windows is recommended in order to prevent the infamous double input issue. HidHide is an optional (but highly recommended) third-party driver that can hide controllers from the system and only allow chosen processes to detect them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |