when the control is connect on, xoutput does not open or closes if open

[kfernandol]

hello i just bought a new controller. and every time i connect it and want to configure xoutput it does not open and if i disconnect it then i open the program and connect the controller it closes. before i used xoutput with another controller and it worked fine someone can help me here i leave the log XOutput.log

[tferrerm]

I think I have a very similar issue. The application crashes whenever it detects my joystick. I'm using some drivers I found online which work well with x360ce and most games (except for ForceFeedback, which is either disabled or persistent). I'm using Windows 10 1909 x64 and the joystick drivers may be outdated, but they should work just fine. XOutput crashes when using ViGEm and when using ScpToolkit as well. The program opens just fine if no joystick is connected. I attached the logs and a dump file which is generated after every crash (ignore the .txt extension). BTW I'm using a PS2 Dualshock 2 controller with an adapter. The hardware ID is HID\VID_0810&PID_0003&REV_0106

I'm using the latest build of XOutput to date (3.26).

XOutput.log ViGEmClient.dmp.txt

[tferrerm]

I tried installing XOutput with ViGEmBus in another computer (using Windows 10 1909 x64 as well), but this time using the joystick's default drivers. Predictably, it worked. However, Force Feedback is not supported by these drivers so there's that. I wonder what's wrong with the other drivers and why the application crashes when using them.

[tferrerm]

I suspect it might be related with a 64 bit DLL being used on a 32 bit driver, or something like that. joy.cpl (the control panel item dedicated to joysticks) crashes whenever I go to the Vibration Test tab. It works if I replace System32's joy.cpl with SysWOW64's joy.cpl. Also, that driver must be quite popular as it shipped with many adapters and cheap joysticks (my adapter came with a miniCD which includes the exact same drivers)

[csutorasa]

I had a few issues with vibration and vibration drivers, but finally I bought a cheap device so I can test then. Now my focus is on the new 4.x version, which will include a few new things and a full rewrite of the original application. I will try to add many options for force feedback, so I can prevent these crashes. I think you may try older versions if you want, but you may lose some other functionality.

[jammydrury]

hello i just bought a new controller. and every time i connect it and want to configure xoutput it does not open and if i disconnect it then i open the program and connect the controller it closes. before i used xoutput with another controller and it worked fine someone can help me here i leave the log XOutput.log

Version 3.17 works with the vibration drivers installed, but you may not get vibration.

[Seamas73]

The last version that working correct with my Sven X-Pad with force feedback (Win 10 identifies it with Sven's driver as PС TWIN SHOCK) is 3.22. I also tried x360ce v.4 - this apps also crashes after plugging in gamepad if driver from Sven ltd. installed

Upd. The cause of crash - is conflict of the app and Ezfrd64.dll from the forcefeedback driver of SVEN X-PAD. I tried to replace this dll with another one from internet. With the replaced dll app v.3.28 don't crash, but forcefeedback don't work, In app v.3.22 forcefeedback works even with replaced dll. ezfrd64.zip

[Squall-Leonhart]

the dll is incompatible with ASLR binaries following windows updates published in 2016, developers have the option of hot patching it similarly to what dolphin did in https://github.com/dolphin-emu/dolphin/pull/5582/commits/1210c74955f1d680eb639317d33f6324b57ec8d3

debugging results were published to dolphin-emu's forum here