Do you still have the capped traffic you used to get the USB controller request to initialize your Thrustmaster wheel? If so can you share them?
Would be nice to understand how the Windows's driver is able to understand which wheel really is the generic 044f:b65d so that we can write a single and polyvalent init driver for the Thrustmaster wheels. I'm not sure if it's even possible (is possible on Windows to have multiple Thrustmaster models at the same time?)
You can find my capped traffic from a T150 here, the control urb is the packet n° 210, it's a Wireshark file.
Maybe the correct title for this «issue» should be something like «Polyvalent hid-tminit»
Do you still have the capped traffic you used to get the USB controller request to initialize your Thrustmaster wheel? If so can you share them?
Would be nice to understand how the Windows's driver is able to understand which wheel really is the generic 044f:b65d so that we can write a single and polyvalent init driver for the Thrustmaster wheels. I'm not sure if it's even possible (is possible on Windows to have multiple Thrustmaster models at the same time?)
You can find my capped traffic from a T150 here, the control urb is the packet n° 210, it's a Wireshark file.
Maybe the correct title for this «issue» should be something like «Polyvalent hid-tminit»