Post by ms17 on Mar 15, 2021 16:35:39 GMT
Let me start this off by saying that I am very impressed with the capabilities of this virtual controller. I like it, and I hope that I'll be able to use it.
My use case: I'm trying to use VJoy along with pyvjoy to write automated tests for the video games I am making in Unity. The controller works well with the python framework, so it seems like a good fit so far.
Unity has errors when a VJoy controller shows up in the list of HID Devices on windows. I've tried to figure out why it has errors and it seems like the problem is the 32-bit size of the axes (they use some bit shifting logic that results in wrap-arounds for a 32-bit int). The error completely breaks the new input system in a way that the only solution is to completely disable or uninstall vjoy for it to work.
First of all, why is the HID report descriptor reporting these as 32-bit values when the maximum value is something like 15 bits? And if for some reason that's necessary, is there a way for me to change it locally so that the HID descriptor says something like 16-bits instead of 32?
I am fairly new to looking at HID descriptors and so I haven't actually had success finding the actual HID report descriptor with the hex numbers and all that. The only way I found it was by modifying some of Unity's input manager code to output what they caught in transit. Could someone also help me know how to access the HID descriptor more directly? I've spent literally hours trying to figure it out.
This is an awesome and powerful tool and I'm excited to see if I can use it. Thanks in advance for any help you guys can send. Also, if this isn't possible right now but it could be if someone sat down and gave it a shot, let me know. I'd be happy to try to contribute and get it to work.
My use case: I'm trying to use VJoy along with pyvjoy to write automated tests for the video games I am making in Unity. The controller works well with the python framework, so it seems like a good fit so far.
Unity has errors when a VJoy controller shows up in the list of HID Devices on windows. I've tried to figure out why it has errors and it seems like the problem is the 32-bit size of the axes (they use some bit shifting logic that results in wrap-arounds for a 32-bit int). The error completely breaks the new input system in a way that the only solution is to completely disable or uninstall vjoy for it to work.
First of all, why is the HID report descriptor reporting these as 32-bit values when the maximum value is something like 15 bits? And if for some reason that's necessary, is there a way for me to change it locally so that the HID descriptor says something like 16-bits instead of 32?
I am fairly new to looking at HID descriptors and so I haven't actually had success finding the actual HID report descriptor with the hex numbers and all that. The only way I found it was by modifying some of Unity's input manager code to output what they caught in transit. Could someone also help me know how to access the HID descriptor more directly? I've spent literally hours trying to figure it out.
This is an awesome and powerful tool and I'm excited to see if I can use it. Thanks in advance for any help you guys can send. Also, if this isn't possible right now but it could be if someone sat down and gave it a shot, let me know. I'd be happy to try to contribute and get it to work.
