This fixed my issue with Rock Band not detecting a microphone, but i don't want to use a microphone. I'd like to use my drums and i haven't been able to find anything on the internet about it other than one guy asking about it too. I have ps2 drums for rock band and while it detects input it doesn't detect them as drums. Therefore it wants to use a microphone. Anybody know a workaround?
Hi Jackun
I couldn't get the plugin to work with my Logitech driving force pro in raw input mode. none of the buttons were responding
Any ideas? I tried a few different combinations of pcsx2 and qemu but no luck.
(07-23-2019, 03:08 AM)Seta-San Wrote: [ -> ]it's not emulated yet.
I actually have the same issue with my (real) GT Force wheel, no way to use it in raw mode or pass-through, is it normal?
(08-31-2019, 09:14 PM)Stremon Wrote: [ -> ]I actually have the same issue with my (real) GT Force wheel, no way to use it in raw mode or pass-through, is it normal?
I can't remember if the current HID report is correct for GT Force. Can you dump some descriptors?
https://github.com/jackun/USBqemu-wheel/...scdump.zip
It shows the list of devices, should be "046d:c293" probably. String desc may give -8 error but idk how necessary they are. Some games check, others don't even care about HID report descriptors.
(08-31-2019, 09:33 PM)jackun Wrote: [ -> ]I can't remember if the current HID report is correct for GT Force. Can you dump some descriptors? https://github.com/jackun/USBqemu-wheel/...scdump.zip
It shows the list of devices, should be "046d:c293" probably. String desc may give -8 error but idk how necessary they are. Some games check, others don't even care about HID report descriptors.
Yes indeed it's "046d:c293".
Here it is
:
Code:
Select device, enter number: 12
Device descriptor: 12010002000000406d0493c2000104200001
Failed to get string descriptor 0: -8
Failed to get string descriptor 1: -8
Failed to get string descriptor 2: -8
Config descriptor 1: 0902290001010080320904000002030000000921100100012200200705810307000a0705020307000a
bNumInterfaces: 1
bInterfaceNumber 0, bInterfaceClass 3
HID report descriptor: 0601000904a1010901150025ff7508950781000902150025ff750895079100c0
I don't know if it's relevent, but when I click the configure button for the raw input, I also get that in the log:
Code:
Could not open device 0
Could not open device 1
Could not open device 2
Could not open device 4
Could not open device 5
Could not open device 6
Could not open device 8
Could not open device 9
Could not open device 10
Could not open device 12
Could not open device 14
Could not open device 15
Could not open device 16
Could not open device 17
Could not open device 18
Could not open device 19
Could not open device 22
Could not open device 23
Could not open device 24
Could not open device 25
Could not open device 26
Could not open device 27
Could not open device 28
Could not open device 29
Could not open device 30
Could not open device 31
Could not open device 32
Could not open device 33
Could not open device 34
Could not open device 35
Could not open device 36
Could not open device 37
Could not open device 38
Could not open device 39
Could not open device 40
Could not open device 41
Could not open device 42
Could not open device 43
Could not open device 44
Could not open device 45
Could not open device 46
Could not open device 47
Could not open device 48
Could not open device 49
Could not open device 50
Could not open device 51
Could not open device 52
Could not open device 53
Could not open device 54
Could not open device 55
Could not open device 56
Could not open device 57
Could not open device 58
Could not open device 59
Could not open device 60
Could not open device 62
Could not open device 63
Could not open device 64
Could not open device 65
Could not open device 66
Could not open device 67
Could not open device 68
Could not open device 69
Could not open device 70
Could not open device 71
Could not open device 72
Could not open device 73
Could not open device 74
Could not open device 75
Could not open device 76
Could not open device 77
Could not open device 78
Could not open device 80
Could not open device 81
Could not open device 82
Could not open device 84
Could not open device 86
Could not open device 87
Could not open device 88
Could not open device 89
Could not open device 93
Could not open device 94
Could not open device 95
Could not open device 96
Could not open device 98
Could not open device 100
Could not open device 101
Could not open device 102
Could not open device 104
Could not open device 105
Could not open device 106
Could not open device 107
Could not open device 108
Just in case you need, I am on Windows 10 x64, with the old Logitech drivers that support FFB (lgs510_x64.exe).
And I am using the last PCSX2 nighly.
Tell me if you need more info
(09-01-2019, 06:21 PM)Stremon Wrote: [ -> ]Yes indeed it's "046d:c293".
Something went wrong. HID report says it's a mouse
It's late now here, I'll check tomorrow if my dumper works.
(09-01-2019, 10:42 PM)jackun Wrote: [ -> ]Something went wrong. HID report says it's a mouse It's late now here, I'll check tomorrow if my dumper works.
Oh, I see
No problem, there is no rush
(09-02-2019, 12:56 PM)Stremon Wrote: [ -> ]Oh, I see
No problem, there is no rush
Tried without, but I think it still needs a libusb compatible "driver". Get installer from
https://zadig.akeo.ie/ , install WinUSB driver over GT Force, run my dumper and then uninstall WinUSB driver. Can't remember if Zadig can uninstall itself, then open Device Manager and when uninstalling check the "Delete this driver" ( or whatever the text was). But I think
GIMX project has useable HID reports already too if it still fails.
(09-02-2019, 01:02 PM)jackun Wrote: [ -> ]Tried without, but I think it still needs a libusb compatible "driver". Get installer from https://zadig.akeo.ie/ , install WinUSB driver over GT Force, run my dumper and then uninstall WinUSB driver. Can't remember if Zadig can uninstall itself, then open Device Manager and when uninstalling check the "Delete this driver" ( or whatever the text was). But I think GIMX project has useable HID reports already too if it still fails.
But using libusb drivers also means I won't be able to use my wheel in anything else than PCSX2, right?
It kind of defeat the purpose for me sadly, but I will still test it as soon as I can anyway, just to see if it works
