You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2024. It is now read-only.
Describe the bug
Okay so, everytime when I restart my PC, DS4Windows asks me to install the vigembus driver, tho i have it installed.
To Reproduce
Steps to reproduce the behavior:
Download DS4Windows 3.0.3
Wait for the controller to work (sometimes it works)
Restart your PC.
and you have the error
Expected behavior
One of my games were being stupid so I decided to restart my PC for it to work (this happens a lot, restarting your PC will fix the issue most of the time)
Screenshots and Logs
No logs cuz idk where it went
Desktop (please complete the following information):
Controller Make and Model: Sony DS5 v.1 (CFI-ZCT1W)
OS: Windows 10 Pro Build 20H2
DS4Windows Version 3.0.3
Additional context
nah
The text was updated successfully, but these errors were encountered:
Do you have an HP laptop or pc ? Cause if you do I would recommend you to follow this > nefarius/ViGEmBus#99. I see the ViGemBus 1.14.3.3 message on the bottom right. Pretty sure thats your issue.
I am considering almost all older ViGEmBus inquiries invalid due to a recently discovered terrible and extremely outdated HP fork of ViGEmBus. DS4Windows 3.0.4 should be able to skip that flawed fork and attempt to use the latest official ViGEmBus driver.
Describe the bug
Okay so, everytime when I restart my PC, DS4Windows asks me to install the vigembus driver, tho i have it installed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
One of my games were being stupid so I decided to restart my PC for it to work (this happens a lot, restarting your PC will fix the issue most of the time)
Screenshots and Logs
No logs cuz idk where it went
Desktop (please complete the following information):
Additional context
nah
The text was updated successfully, but these errors were encountered: