Hello,a very big thank you to Ryochan7 for this magnificent software that I love.
-I use the controller dualshock 4 V2 and it works perfectly with the game Final fantasy 15 windows edition on my pc in windows10 pro 64bits!
-however a question intrigues me : On the official website of the inputmapper software, the developer wrote:
DS4Windows :
Depreciated
Included only for archival and historical purposes. Please use聽InputMapper聽instead.
-Can you tell me if he wrote this in all competition and adversary at ds4windows ?
-Is ds4windows better than inputmapper?
my config : i7 4790k ,asus Z97-A,msi gtx 1060 gaming X 6go,16go ram gskill trident X 2133mhz,ssd samsung 850 evo 250go,sshd seagate 2to,hdd wd 1to,power supply cooler master g550m 550W,keyboard roccat ryos mk pro,mouse corsair sabre laser rgb.
What is better is up to you.
That comment about DS4Windows being deprecated was regarding the DSDCS fork of DS4Windows. I am not sure how far back that fork originated but I think it was branched off of the electrobrains fork of DS4Windows. There are still some videos on the InputMapper YouTube channel that promote his fork of DS4Windows before it became InputMapper.
The first version of DS4Windows that I ever used was Jays2Kings version 1.4.52 and that version was the initial base for this fork. Feature wise, the two programs are mostly comparable except for the Macro Builder that is included in InputMapper. The priority for me was perceived input lag when comparing the two programs. DS4Windows was more responsive than InputMapper so that is why I started using DS4Windows.
As it stands now, InputMapper is a broken program in my opinion. IM 1.6 hardly works especially regarding BT controllers which takes a specific workaround to get my controller to be recognized by the program. Exclusive mode requires HidGuardian and I do not like the old version that the IM installer bundles. IM 1.7 has never worked on my system or in a fresh Windows 10 install on a VM. It seems that it can detect the ViGEm driver based on the About window but no output driver is present when editing profiles. It also never detects my controllers.
I hope that Wobbles gets around to updating InputMapper more often. He is doing some interesting things with the project.
Hello Ryochan7 .I thank you very much for your answer and these explanations. I use my controller dualshock 4 V2 with usb cable. personally I do not like bluetooth because it uses radio waves that could be harmful to health i do not know...
-With USB cable plugged either on the USB port of my pc monitor or the one of my keyboard, ds4windows indicates to me an input lag of 4ms. it goes very very well, I see no delay between the action to the controller and the action on my pc monitor aoc q2778vqe with display port.
I am very happy with ds4windows, and there are recent updates, thank you very much 馃槂
I finally got InputMapper 1.7 working. On the newest beta instructions, there is a note about Windows possibly blocking execution of some DLLs and that is what ended up causing the program to not work on my system.
Ensure plugins are not blocked by Windows, this will prevent them from loading in IM. See: https://beta.inputmapper.com/forum/inputmapper-1-7/controller-not-found/#post-7
https://beta.inputmapper.com/download/inputmapper-1-7-nightly-build/
I had to go through each DLL included in the Plugins directory from Explorer and unblock each one.
Now that I have had a chance to test InputMapper 1.7, I can definitely say that DS4Windows is objectively better than InputMapper 1.7 as it stands now. The latency problems from 1.6 have not been dealt with and input responsiveness is far worse than what DS4Windows offers.
Also, DS4 controller emulation performs far worse than what I could achieve with my test program although that isn't such a fair comparison.
Most helpful comment
That comment about DS4Windows being deprecated was regarding the DSDCS fork of DS4Windows. I am not sure how far back that fork originated but I think it was branched off of the electrobrains fork of DS4Windows. There are still some videos on the InputMapper YouTube channel that promote his fork of DS4Windows before it became InputMapper.
The first version of DS4Windows that I ever used was Jays2Kings version 1.4.52 and that version was the initial base for this fork. Feature wise, the two programs are mostly comparable except for the Macro Builder that is included in InputMapper. The priority for me was perceived input lag when comparing the two programs. DS4Windows was more responsive than InputMapper so that is why I started using DS4Windows.
As it stands now, InputMapper is a broken program in my opinion. IM 1.6 hardly works especially regarding BT controllers which takes a specific workaround to get my controller to be recognized by the program. Exclusive mode requires HidGuardian and I do not like the old version that the IM installer bundles. IM 1.7 has never worked on my system or in a fresh Windows 10 install on a VM. It seems that it can detect the ViGEm driver based on the About window but no output driver is present when editing profiles. It also never detects my controllers.
I hope that Wobbles gets around to updating InputMapper more often. He is doing some interesting things with the project.