Hi. im using VDX on windows 10, and i have ussues with its visibility when i open it over any windows, i can see it just when i have clean desktop under it.

And VDX cannot be controlled by keyboard (i mean selecting Dualshock 4 and pressing connect button). It would be really helpfull to implement keyboard input, as i can automatize VDX startup using ahk.

Thanx.

It seems VDX doesn't implement rumble/vibration support. It could be great to have this feature.

Hi,
Thanks for this great tool, i got a little feature request.
There is no need to have the window visible all the time
It would be great if you could add an option to minimize VDX to taskbar or tray.

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• I have read https://vigem.org/Community-Support/
• This isn't a feature request or a discussion topic

Bug description

When I run VDX.exe, I immediately get an error box saying, "Xinput1_3.dll is missing." However, I can confirm that that file exists at both "C:\Program Files\WindowsApps\Microsoft.DirectXRuntime_9.29.1974.0_x86__8wekyb3d8bbwe\xinput1_3.dll" and "C:\Program Files\WindowsApps\Microsoft.DirectXRuntime_9.29.1974.0_x64__8wekyb3d8bbwe\xinput1_3.dll".

Steps to reproduce

• Download VDX.exe from https://buildbot.vigem.org/builds/VDX/master/1.16.65.0/bin/x64/
• Run it.

Actual result: Error box described as above. VDX then aborts.
Expected result: I would expect some sort of installer or program to appear when I run this executable.

Machine info

CPU-Architecture: x64
Windows version: Windows 10 21H1
Software/driver version(s): VDX version 1.16.65.0

Any other helpful information

I attempted to run VDX.exe immediately after successfully installing ViGEmBusSetup_x64.msi.

So, I just updated Windows to the latest version and VDX is no longer working, before that, it worked fine.

When I open VDX without connected controller it looks just fine, but when I connect my generic controller, it shows it as controller 1 but then instantly crashes. Is there any way to debug this ?
Also it does not even open when my controller is connected and then I try running it. Just transparent window on taskbarr for one second that disappears.

Like the title says, would it be possible to add Xbox 360 to the list of emulated controllers?

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• I have read https://vigem.org/Community-Support/
• This isn't a feature request or a discussion topic

Bug description

Describe here the issue that you are experiencing.

Steps to reproduce

• using hyphens as bullet points
• list the steps
• that reproduce the bug

Actual result: Describe here what happens after you run the steps above (i.e. the buggy behaviour)
Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)

Screenshots

Machine info

CPU-Architecture: x86, x64, ARM, ARM64, ...
Windows version: Windows 10 20H2
Software/driver version(s): 1.4.14

Any other helpful information

Test

So I'm using Shibari+Fireshock+Vigem, as I was told that VDX can emulate a ps4 controller using a ps3 controller with these programs. The problem is that when I select DS4 in the menu and press connect, it will send double inputs in Windows and in Steam. I'm assuming this is because it sends input as both xbox and DS4 at the same time. I can see this also being a problem in games that natively support the ps4 controller, as it would see both the xbox inputs and the DS4 inputs at the same time as well. Is there a way to disable the xbox inputs while I've set it to use DS4? Or some other thing I'm missing?

Hi @nefarius, this is a fantastic project! One thing that could make it a lot more robust is the ability to send the emulated commands via USB.

I'm imagining a scenario where Xbox Streaming and PS Remote play aren't available (e.g. lack of wifi), so a user connects a controller to their PC, emulates the desired controller, and connects their PC to the console via a long male-to-male USB cable. The user selects the "Send over USB" option in VDX, and voila: The console behaves as if a wired controller were just connected to it.

This could allow users to use a variety of controllers* to play old Xbox 360 games that aren't forward-compatible with newer consoles.
(*or even a pair of X1 controllers, using the Xbox Accessories app's support of copilot mode)