Chrome fails to recognize vJoy on a windows server 2016 VM

[danishS11]

Hi, I've installed vJoy on the Windows Server (VM) and configured it, however, chrome browser does not recognize the vJoy device connected. I do see vJoy status as "OK" in the Game Controller panel. It works on the windows 10 machine (real device) however. Is there some special configuration I need to do for it, or does it not support windows server '16?

[shauleiz]

vJoy is a normal HID. Only it is virtual. This means that if you can install an HID (e.g. steering wheel) you can install vJoy. Perhaps vJoy was not installed successfully. Perhaps your configuration cannot see HIDS.

[danishS11]

It does say that it's installed successfully and I can see vJoy in Device Manager as well as windows native HIDs. However, chrome does not recognize it no matter what I do.

[shauleiz]

Which version of vJoy is it. I see you have installe it on Windows10 1903 - this requires vJoy 2.1.9 or later. Then, I do miss something. What Chrome has to do with devices? Can you give me a link to a site that accesses vJoy or anyother HID?

On Fri, 9 Aug 2019 at 15:59, Danish S. notifications@github.com wrote:

It does say that it's installed successfully and I can see vJoy in Device Manager as well as windows native HIDs. However, chrome does not recognize it no matter what I do.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/shauleiz/vJoy/issues/31?email_source=notifications&email_token=ADGHYJB2FEUNWPS3ALXENFTQDVS2JA5CNFSM4IKKPUG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD36TB2Q#issuecomment-519909610, or mute the thread https://github.com/notifications/unsubscribe-auth/ADGHYJFSOGFZFIZCHMEIKELQDVS2JANCNFSM4IKKPUGQ .

[evilC]

I can confirm that HTML5 Gamepad Tester in chrome does indeed not see a vJoy device on a Windows Server 2016 VM.
DIView does see it, so Server 2016 does appear to support DirectInput

[shauleiz]

Aha, now I see (Well, I can't). Same problem with FireFox

However: Devices with buttons are detected when used by an application (Such as the demo feeder supplied with vJoy).

EDIT: As a matter of fact, I can see that vJoy is the 10th most popular controller used with this tester.

[evilC]

That site works fine with vJoy devices under Win10 - Dunno if it is an inherent issue with 2016, or just VMs . I could not tell you how that site reads devices however, I think it uses pure HID, not DirectInput, as it can see all the inputs of a DualShock 4, whereas DirectInput cannot

[danishS11]

I was testing the vJoy input on gamepadviewer.com and my company website. So @evilC what should be my course of action?

[evilC]

From what I can tell, HTML5 has a Gamepad API, which is what these web pages use. As the HTML5 tester I linked notes "The Gamepad API is still inconsistent across browsers and OSes" So I am guessing there is not anything you can do, it simply is not supported on this OS

[danishS11]

I see, so I guess I'll spin up a different VM and try on there. Thanks for the help!

[danishS11]

@evilC so i created a new Windows 10 VM and tried on there but it still doesn't work on that OS either. To test, I'm using gamepadviewer.com

[evilC]

It may be an issue with the VM, or could be an issue with the way that site works in a VM. Try DIView in the VM for a more accurate representation of what DirectInput sees. Or, you could be using a version of vJoy that is incompatible with that version of Windows?