Repository navigation
[Bug] vJoy devices are not getting hidden by PadForge #515
|
Hi i noticed a bug recently.
The devices themselves are named I also have HidHide 1.5.230.0 installed, which might conflict. For sure i can open the HidHide configuration client, and that the vJoy devices are NOT checked to be hidden. Motivation: Is there a posible solution for this? Or not having HidHide and /or vJoy might be a requierement for PadForge? As always thanks for the great works on this app. |
Replies: 1 comment
|
@aguxone This was PadForge's bug, and commit 22f6e50 on the v5 dev branch fixes it. vJoy's joysticks are collections of one software device that Windows enumerates on its own, so their device IDs read Neither HidHide nor vJoy is a problem to have installed. PadForge writes HidHide's list through the HidHide driver, not its configuration client, so the client crashing after you hide a vJoy device there doesn't affect PadForge's hiding. You don't need the command-line tool for this either. The fix comes with the next v5 dev build and the next release. |
@aguxone This was PadForge's bug, and commit 22f6e50 on the v5 dev branch fixes it.
vJoy's joysticks are collections of one software device that Windows enumerates on its own, so their device IDs read
HID\HIDCLASS&COL01,HID\HIDCLASS&COL02and so on, with no vendor ID in them. PadForge hid a row by its own device node only when that ID carried a vendor ID. Every vJoy row went instead to a lookup by vendor and product ID, which never matched, so a row set to Hide from Games hid nothing while its box stayed checked. Any HID collection now counts as the row's own node. Each vJoy joystick you set to hide is hidden on its own, and the ones you leave visible stay visible to your emulators.Neit…