Open wiesshund opened 4 years ago
I fixed this in the registry Appears to be an issue of the drivers for this specific controller
HKEY_CURRENT_USER > System > CurrentControlSet > Control > MediaProperties > PrivateProperties > Joystick > OEM delete all keys that contain VID_06A3 in the name
Do the same in HKEY_CURRENT_USER > System > CurrentControlSet > Control > MediaProperties > PrivateProperties
To debug these issues Windows Event log can help us more than the logs of the application. Althought it is a nice catch, if you delete those and it works, then the driver is faulty (as you said). Do you need more help on this?
I've this issue too with Cyborg Rumble Pad (P3600)
. It's definitely a buggy driver/Windows combination: used to work just fine on previous Windows version.
Removing/renaming SaiPF51A.Dll
in c:\Windows\System32
helped. This will disable force feedback completely. Messing with registry entries got me a nice BSOD :).
XOutput.log
ViGEmClient.dmp.zip
client log and zipped dump file from ViGEm attached OS: Windows 10 Pro 64 bit Controller type: USB Saitek P2500 Rumble Force.
Tested with both Saitek drivers and MS Generic drivers Result is same.
Controller functions otherwise in all aspects, with or without Xoutput And with both MS and Saitek drivers