Open imyxh opened 2 weeks ago
ahungry
commented
2 weeks ago The driver is bluetooth - if it's wired, it's not going to use the bluetooth driver :smile:
As far as my testing concluded, dinput + bluetooth does not send/expose any rumble events, nor was I able to get any type of output via FFTest.
imyxh
commented
2 weeks ago The driver is bluetooth - if it's wired, it's not going to use the bluetooth driver 😄
Oh, I'm aware, just asking here because I'm considering writing a wired driver / adding wired functionality to this driver and this seems to be the closest thing the community has to a driver.
As far as my testing concluded, dinput + bluetooth does not send/expose any rumble events, nor was I able to get any type of output via FFTest.
Hmm. I'll play around with fftest later, but we might have to resort to packet capturing on windows.
ahungry
commented
2 weeks ago I don't think bluetooth + rumble works on Windows either (but I could be mistaken)
Hey there. Not so much a bug in anything you wrote, but I've been playing around with this controller and it does seem that the gyro data is exposed over hidraw when in dinput mode, at least when it's wired. So in principle we could pass on that gyro to SDL2, right? (What is the relation between hid drivers and SDL2? How does SDL2 pick out the axes and buttons it cares about?)
Also, I'm just curious about why you think the rumble is hardware limited. To my knowledge, rumble with dinput works on Windows. Do we just need to reverse-engineer the rumble protocol?