The first problem with the x64 executable is that the progam can't find the ViGEm Bus Driver, I have the exact same problem when I tries to run it. I'm currently trying to figur out why the ViGEm Bud Driver doesn't seams to work. Was getting to this forum trying to get help 🙂
The x86 executable seams to be dynamicly linked to the ViGEmClient.dll while the x64 executable is static linked to the ViGEmClient.lib during build time. Meaning that the x86 executable requies the dll file which you can get from compiling the source code from github and copy-pase the x86 version of ViGEmClient.dll to the folder.
Its not "vigem" problem. "Vigem" is use xinput fo ps4 controller emulation and xinput you can say is xbox controller. Xbox controller has only 13 number of buttons ps4 - 14 - number 14 is touchpad click - it cannot be emulated via "x360ce" because it understands only 13 buttons. To be clear you need "vigem" can understand "vjoy" itself or can support side manufactured controllers with mapping option included. I get this way all from beginning to play Destiny via ps4 remoteplay app on my WIN10, and touchpad in this game is urgent control button - without game cannot be played, So it sad but true )))
There are no alternatives that provide the abilities that Target does. Besides complex C programming for macros, it handles HID device hiding, virtual joystick driver, and LED control of TM devices. Joystick Gremlin is the closest generic solution I think. Still no where near the abilities of the TM solution. Really the only major drawback of Target is it only works with TM devices, which isn't a problem for us folks who own those devices.
I am currently implementing Interception for keyboard / mouse IO, I take it that vmulti is output only? Can it synthesize input coming from a specific device, or just "synthetic" input? If so, can it synthesize input coming from a device which is not present on your system?