Open MaciejNiklasinski opened 4 years ago
What program are you using that indicates the joystick's type is "Driving"?
Ages ago I wrote in C# a vJoy feeder/remapper in which I used SharpDx.DirectInput package to detect all the connected HIDs. I have every reason to believe that it detects the device type correctly because it detects my Thrustmaster Warthog as "Joystick" and my Logitech G29 as "Driving".
Thanks for the extra information. I'll have to investigate further to see if I can figure out what DirectInput is using to determine the joystick type.
Note to myself: Looks like it may be related to this: https://docs.microsoft.com/en-us/windows/win32/api/dinputd/ns-dinputd-dijoytypeinfo?redirectedfrom=MSDN
Description of Issue
Not sure whether that's a bug report or a feature request. So regardless of what constant I will use when initializing the Joystick (JOYSTICK_TYPE_JOYSTICK/JOYSTICK_TYPE_GAMEPAD/JOYSTICK_TYPE_MULTI_AXIS) the created the device will always be of type "Driving". Almost all programs are still able to use it as normal joystick but FSUIPC beta 7, an addon to new Microsoft Flight Simulator which I intended to use to help me to map all the controls, unfortunately, doesn't (It does detect all my 'real' joysticks).
Is that a bug or the JOYSTICKTYPE* constants specifying something else and the intended HID type is "Driving"? If that's not a bug I would like to request a feature, please. I tried to look into the DynamicHID code, I know C# and JavaScript but my understanding of c++ is very slim (as you will see by looking into the attached sketch, I do realize that I follow possibly anti-pattern there but I just wanted something to work quickly and couldn't spend time on learning the language properly) so I can't see what would need to be changed if anything to change the HID type there.
Technical Details
Sketch File that Reproduces Issue
Wiring Details
Any pin wiring details that may be relevant.
Additional context
Add any other context about the problem here.