Ryochan7 / DS4Windows

Like those other ds4tools, but sexier
https://ryochan7.github.io/ds4windows-site/
GNU General Public License v3.0
6.93k stars 802 forks source link

is the Hori fighting commander ps4/ps3/pc supported? #847

Closed antervud closed 4 years ago

antervud commented 4 years ago

it's only usb wired, no bluetooth

mika-n commented 4 years ago

Some Hori controller models work, but others don't. What is the hardware VendorID/ProductID (VID/PID) identifiers of your controller model? This can be seen in DeviceManager//Properties/HardwareID screen.

Or you could run a special debug version of DS4Windows.exe executable and it should list the VID/PID in Logs tab page. https://github.com/Ryochan7/DS4Windows/wiki/Troubleshooting#detailed-debug-log-file-from-gamepad-connection-problems

Similar issue with another non-official Sony controller. https://github.com/Ryochan7/DS4Windows/issues/803

antervud commented 4 years ago

i'm waiting for delivery, should be here in few days

antervud commented 4 years ago

HID\VID_0F0D&PID_0084&REV_0100&Col01 HID\VID_0F0D&PID_0084&Col01 HID\VID_0F0D&UP:0001_U:0005 HID_DEVICE_SYSTEM_GAME HID_DEVICE_UP:0001_U:0005 HID_DEVICE

here's what i got, the pad is connected in ps4 mode, does not show up in normal ds4 nor in the debug version

mika-n commented 4 years ago

Try to run "DeviceDetectDebug9" version linked in the following page and please provide the logfile here. https://github.com/Ryochan7/DS4Windows/wiki/Troubleshooting#detailed-debug-log-file-from-gamepad-connection-problems

antervud commented 4 years ago

export.txt

mika-n commented 4 years ago

The debug version detects the Hori Fighting Commander, but does it actually work in DS4Windows? Can you re-map buttons? The gamepad has a special switch to alter how DPad keys work (dpad, left stick, right stick). Does that functionality work? If you open Joy.cpl controlPanel applet then do you see any activity in the virtual x360 gamepad controller device?

antervud commented 4 years ago

works in the debug version, does not work in the latest normal version, switch are hardware so they work without a special driver

is fine on joy.cpl, it is strangely named Controller (Sega Controller), on debug mode

mika-n commented 4 years ago

Yes. The latest official release doesn't support this new controller type yet. Only this debug version has an experimental support for it. But, if you find that the controller works good enough with the debug version then some upcoming official release probably adds supports to the gamepad.

Hmmm... The virtual output driver of DS4Windows should be "Controller (XBOX 360 for Windows)" controller in JOY:CPL controlPanel applet. I don't understand why and how it would be shown as "Controller (Sega Controller)".

Are you sure that this SegaController isn't the original physical controller? IF you don't use exclusive mode (or it fails to activate) or don't use HidGuardian then you should see two gamepad controlelrs in JOY:CPL applet. The physical original controller and a virtual x360 output controller created by DS4Windows app and ViGem driver.

The logfile you provide does have a warning message about exclusive mode (it failed to activate):

19/10/2019 19:40:05: Warning: Could not open DS4 00:00:00:00:00:10 exclusively. You must quit other applications like UWP apps (Netflix), Steam, Uplay, NVIDIA IN-GAME before activating the 'Hide DS4 Controller' option. For more info check https://github.com/Ryochan7/DS4Windows/wiki/Exclusive-Mode-(Hide-DS4-Controller-config-option)-tips-and-issues

See the following page for more tips about exlusive mode (built-in in DS4Windows app) and alternative solution of HidGuardian device driver. https://github.com/Ryochan7/DS4Windows/wiki/Exclusive-Mode-(Hide-DS4-Controller-config-option)-tips-and-issues

antervud commented 4 years ago

i had steam on probably, as of now

ds4bebug joy cpl export2.txt

seems fine now, i will try it in game then report

antervud commented 4 years ago

now that i remember, i have a sega megadrive controller clone with xinput, thats probably the first xinput device i had installed on my pc, dunno if that's related

mika-n commented 4 years ago

Okey. Probably that SegaMegadriveController device driver has hijacked the normal xbox 360 controller device, so your PC shows a different name. If things work with this clone driver then all is good.

About the Steam client and DS4Windows.exe process name there is a potential problem (=bad feature in Steam client) if you want to use the DS4Windows re-mapped device in Steam games. See the following post about how Steam actively ignores DS4 gamepad if certain other processes are running at the same time. The solution is to re-name DS4Windows.exe executable to some other name. https://github.com/Ryochan7/DS4Windows/wiki/Troubleshooting#steam-doesnt-see-the-virtual-output-controller-if-a-profile-uses-the-dualshock4-output-type-steam-sees-the-ds4-controller-only-if-ds4windows-uses-xbox360-output-controller-type

Anyway. If you are happy with the HoriFightingCommander support in the debug version then I will push those changes to wait for some upcoming official release. Until then you should use the debug version.

antervud commented 4 years ago

i tried to play tekken 7 for 3 hours online with exclusive mode, steam sat to ignore my controller device

all went fine, no weird things happened, no input drops, seems to work