![]() ![]() 13:23:29: Controller 1's latency now under 10ms 13:23:20: Controller 1's latency now under 10ms 13:22:40: Controller 1's latency now under 10ms 13:22:28: Controller 1's latency now under 10ms 13:22:18: Controller 1's latency now under 10ms 13:22:08: Controller 1's latency now under 10ms 13:21:55: Controller 1's latency now under 10ms 13:20:17: Controller 1's latency now under 10ms 13:18:48: Controller 2 is using Profile "Default". 13:18:48: Associate X360 Controller for input DS4 #2 13:18:48: Plugging in virtual X360 Controller 13:18:40: Controller 1 is using Profile "Default". 13:18:40: Associate X360 Controller for input DS4 #1 13:18:40: Plugging in virtual X360 Controller ![]() 13:18:19: OS Product Name: Windows 10 Home 13:18:19: OS Version: Microsoft Windows NT 2.0 13:18:19: DS4Windows Assembly Architecture: 圆4 Including my recent log (not sure if this is always the same sequence of errors), looks like a minute after that 2nd controller is connected, latency goes all over the place. So not sure if this is really a DS4Windows error, but figured you guys are the most likely to know what I need to do! they still disconnect (from connected to paired). Exiting DS4Windows (assuming it not showing in the system tray is fully closed) and connecting just as a wireless controller.I didn't fully uninstall, just copied the files over. Rolling back to 2.2.1 as I saw some comments that the recent versions have issues.I think the only profile change I've made was making it max poll rate and making sure it was emulating 360.updating my Intel Bluetooth 5.0 driver (on TUF X570-PLUS WI-FI, which I also updated the BIOS).All three controllers are V2 (light bar in touchpad). Now everything disconnects all the time, even after removing the 3rd pairing and just trying the two again.Īll are using the default (and still only) profile. Then, I decided to buy a 3rd controller and set it up as well. I read somewhere that this might be because the PC gives less power to the front ports in comparison to the back one's so if that's true, that's also my solution.I had two PS4 controllers working great with Windows 10 and DS4Windows 2.2.6, connected via Bluetooth, playing on Cemu and Yuzu with motion and touchpad. ![]() However, I am glad to say I managed to fix the problem (I think) - I usually use my front case's USB ports and I figured why not try the back one to see if it works and to my surprise - it did! no latency error in DS4Windows, no yellow error triangle on the DS4's sound driver in Device Manager and controller seems to work great. I also unchecked said option from each USB Root Hub. either way the ds4 headphone jack driver had a yellow triangle on it which prompted me to update its drivers but whilst doing so I would get an error 10 saying it can't start it up. ![]() Under normal circumstances, Input delay should be fairly close to 4 ms while wired unless your system is being over taxed. I use the Full Performance power plan but I think another option is to disable the option "Allow the computer to turn off this device to save power" under USB Root Hub > Power Management for each entry listed in the Device Manager. After that, you might want to check your power management settings and make sure the USB ports are not being underpowered. The game controller would be listed under "Human Interface Devices" as HID-compliant game controller you will have to check in the Properties if multiple devices are listed.Įspecially with the problem that you posted, I would suggest that you uninstall both devices and attempt to have Windows set them up again. The entry listed under "Sound, video and game controllers" would correspond to the exposed audio device for the DS4 headphone jack. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |