ControlService.cs.EstablishOutFeedback. Net ViGem interface and ViGem native C/C++ client DLL library. Except that V2.1.23 comes with older version of.
#DS4WINDOWS PCSX2 DRIVER#
I keep pressing the Test rumble button in Dolphin controller configuration screen few times rapidly to make it send startRumble-stopRumble-startRumble-stopRumble commands right after each other.Īt this point I don't understand why this would work any better in 2.1.23 version using 1.17.333 ViGem driver because the feedback handler is pretty much the same code. The bug seems to happen only when there are many rumble events within very short period of time (ie. NET client interface or in the ViGem 1.17.333 C/C++ native client DLL library or in the worst case in the ViGem 1.17.333 kernel device driver level. The bad news is that don't know yet if this is a bug in DS4Windows code, in ViGem.
#DS4WINDOWS PCSX2 CODE#
Looks like sometimes the ViGemFeedbackEventHandler in DS4Windows app code never receive the Large=0 Small=0 event and that's why the other rumble motor gets stuck. I debugged the "stuck rumble motor" issue using the latest 2.2.1 (actually the latest devel code, not yet published) version and interesting findings. The DS4Windows logfile should show the version stamp of DS4Windows app itself AND ViGem Any ideas about the following debug log dump? So, is this gamepad or game specific issue or a profile setting? Please attach a zipped DS4Windows profile here.Īnd make sure you all have the latest ViGem 1.17.333 vigem driver installed and if you have ever installed the ancient ScpToolkit tool then all traces of ScpToolkit is removed. Have you found any freeware games/apps/gamepad tester apps where you can duplicate this bug? Therefore it is still potentially possible that the bug occurs only via a specific game in Dolphin, but I cannot test those games you listed. However, I don't have any game ROMs for Dolphin but in the old days the rumble bug popped up even via controller configuration screen when testing rumble. Nowadays and with the latest Vigem 1.17.333 and DS4Windows 2.2.1 I cannot duplicate this bug. Some time ago when there was a bug in ViGem client driver, Dolphin gameCube/WII emulator was one app where this bug was easily seen even via the Dolphin. I really cannot duplicate this "persistent rumble" bug with the latest version. Reply to this email directly, view it on GitHub You are receiving this because you authored the thread. Please let me know if you'd like to do anything to help debug. 16:40:52.0780|INFO|Controller 1 is using Profile "Default". The log files don't indicate any kind of error.
#DS4WINDOWS PCSX2 BLUETOOTH#
Release (2.2.1), as well as whichever version of ViGEmBus (1.17.333,ġ.16.116), as well as the issue persisting on both Bluetooth and USB with aĭualshock 4 v2. Game or app doesn't send any rumble commands. Please let me know if you'd like me to do anything to help debug. Games I tried this on are Spyro Trilogy and the Dolphin Emulator, but I'm sure this happens on any game. It happens with the latest release (2.2.1), as well as whichever version of ViGEmBus (1.17.333, 1.16.116), as well as the issue persisting on both Bluetooth and USB with a Dualshock 4 v2. Light rumble retains after the game or app doesn't send any rumble commands.
0 kommentar(er)
