Using DS4 as a device within gimx config
-
- Posts: 39
- Joined: Sun Aug 16, 2015 12:58 am
Re: Using DS4 as a device within gimx config
Could you please try with the x86_64 version?
GIMX creator
-
- Posts: 39
- Joined: Sun Aug 16, 2015 12:58 am
Re: Using DS4 as a device within gimx config
I managed to control the PS4 with x86_64, which is weird since it wasn't working for me before with either 4.3 or 5.0. But there's an error coming up in terminal that keeps repeating:
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
and the DS4 disconnects after around 8 or so seconds.
Enumerate USB devices
Found 8 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
1. FilterID: 7, Port: 1, ID: 13fd:1340, Configs: 1, Speed: 3
USB\VID_13FD&PID_1340 57442D574341525731323639
Descriptor for configuration #0: size 32
2. FilterID: 9, Port: 1, ID: 8087:8009, Configs: 1, Speed: 3
USB\VID_8087&PID_8009 1
Descriptor for configuration #0: size 25
3. FilterID: 13, Port: 18, ID: 174c:3074, Configs: 1, Speed: 4
USB\VID_174C&PID_3074 18
Descriptor for configuration #0: size 31
4. FilterID: 13, Port: 5, ID: 046d:c07d, Configs: 1, Speed: 2
USB\VID_046D&PID_C07D 097734723232
Descriptor for configuration #0: size 59
5. FilterID: 13, Port: 3, ID: 174c:2074, Configs: 1, Speed: 3
USB\VID_174C&PID_2074 3
Descriptor for configuration #0: size 41
6. FilterID: 13, Port: 1, ID: 1a40:0101, Configs: 1, Speed: 3
USB\VID_1A40&PID_0101 1
Descriptor for configuration #0: size 25
7. FilterID: 13, Port: 13, ID: 054c:05c4, Configs: 1, Speed: 2
USB\VID_054C&PID_05C4 13
Descriptor for configuration #0: size 41
This is how it looks when the DS4 is connected to the USB port that I used frequently with 4.3, but no longer works
Enumerate USB devices
Found 7 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8009, Configs: 1, Speed: 3
USB\VID_8087&PID_8009 1
Descriptor for configuration #0: size 25
1. FilterID: 2, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
2. FilterID: 3, Port: 18, ID: 174c:3074, Configs: 1, Speed: 4
USB\VID_174C&PID_3074 18
Descriptor for configuration #0: size 31
3. FilterID: 3, Port: 3, ID: 174c:2074, Configs: 1, Speed: 3
USB\VID_174C&PID_2074 3
Descriptor for configuration #0: size 41
4. FilterID: 3, Port: 1, ID: 1a40:0101, Configs: 1, Speed: 3
USB\VID_1A40&PID_0101 1
Descriptor for configuration #0: size 25
5. FilterID: 3, Port: 5, ID: 046d:c07d, Configs: 1, Speed: 2
USB\VID_046D&PID_C07D 097734723232
Descriptor for configuration #0: size 59
6. FilterID: 4, Port: 1, ID: 13fd:1340, Configs: 1, Speed: 3
USB\VID_13FD&PID_1340 57442D574341525731323639
Descriptor for configuration #0: size 32
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
and the DS4 disconnects after around 8 or so seconds.
Enumerate USB devices
Found 8 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
1. FilterID: 7, Port: 1, ID: 13fd:1340, Configs: 1, Speed: 3
USB\VID_13FD&PID_1340 57442D574341525731323639
Descriptor for configuration #0: size 32
2. FilterID: 9, Port: 1, ID: 8087:8009, Configs: 1, Speed: 3
USB\VID_8087&PID_8009 1
Descriptor for configuration #0: size 25
3. FilterID: 13, Port: 18, ID: 174c:3074, Configs: 1, Speed: 4
USB\VID_174C&PID_3074 18
Descriptor for configuration #0: size 31
4. FilterID: 13, Port: 5, ID: 046d:c07d, Configs: 1, Speed: 2
USB\VID_046D&PID_C07D 097734723232
Descriptor for configuration #0: size 59
5. FilterID: 13, Port: 3, ID: 174c:2074, Configs: 1, Speed: 3
USB\VID_174C&PID_2074 3
Descriptor for configuration #0: size 41
6. FilterID: 13, Port: 1, ID: 1a40:0101, Configs: 1, Speed: 3
USB\VID_1A40&PID_0101 1
Descriptor for configuration #0: size 25
7. FilterID: 13, Port: 13, ID: 054c:05c4, Configs: 1, Speed: 2
USB\VID_054C&PID_05C4 13
Descriptor for configuration #0: size 41
This is how it looks when the DS4 is connected to the USB port that I used frequently with 4.3, but no longer works
Enumerate USB devices
Found 7 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8009, Configs: 1, Speed: 3
USB\VID_8087&PID_8009 1
Descriptor for configuration #0: size 25
1. FilterID: 2, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
2. FilterID: 3, Port: 18, ID: 174c:3074, Configs: 1, Speed: 4
USB\VID_174C&PID_3074 18
Descriptor for configuration #0: size 31
3. FilterID: 3, Port: 3, ID: 174c:2074, Configs: 1, Speed: 3
USB\VID_174C&PID_2074 3
Descriptor for configuration #0: size 41
4. FilterID: 3, Port: 1, ID: 1a40:0101, Configs: 1, Speed: 3
USB\VID_1A40&PID_0101 1
Descriptor for configuration #0: size 25
5. FilterID: 3, Port: 5, ID: 046d:c07d, Configs: 1, Speed: 2
USB\VID_046D&PID_C07D 097734723232
Descriptor for configuration #0: size 59
6. FilterID: 4, Port: 1, ID: 13fd:1340, Configs: 1, Speed: 3
USB\VID_13FD&PID_1340 57442D574341525731323639
Descriptor for configuration #0: size 32
Re: Using DS4 as a device within gimx config
The cable you are using for the DS4 may be defective. Please try another one.
GIMX creator
-
- Posts: 39
- Joined: Sun Aug 16, 2015 12:58 am
Re: Using DS4 as a device within gimx config
I'll try, but it's working fine for me currently in 4.3 with DS4.
Re: Using DS4 as a device within gimx config
I tried to reproduce your issues, and I realized that GIMX 5.0 i386 can't work on a 64bit Windows.
I had no issue running GIMX 5.0 x86_64.
Maybe you should try to uninstall all GIMX versions including USBDK (using the Programs and Features panel).
And then install GIMX 5.0 x86_64.
You should also check that your drivers are up-to-date, especially the USB controller drivers.
And if your computer has USB 2.0 ports, use them instead of USB 3.0 ports.
I had no issue running GIMX 5.0 x86_64.
Maybe you should try to uninstall all GIMX versions including USBDK (using the Programs and Features panel).
And then install GIMX 5.0 x86_64.
You should also check that your drivers are up-to-date, especially the USB controller drivers.
And if your computer has USB 2.0 ports, use them instead of USB 3.0 ports.
GIMX creator
-
- Posts: 39
- Joined: Sun Aug 16, 2015 12:58 am
Re: Using DS4 as a device within gimx config
This is my result from 5.0 x86_64
Enumerate USB devices
Found 7 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
1. FilterID: 7, Port: 1, ID: 13fd:1340, Configs: 1, Speed: 3
USB\VID_13FD&PID_1340 57442D574341525731323639
Descriptor for configuration #0: size 32
2. FilterID: 9, Port: 1, ID: 8087:8009, Configs: 1, Speed: 3
USB\VID_8087&PID_8009 1
Descriptor for configuration #0: size 25
3. FilterID: 13, Port: 18, ID: 174c:3074, Configs: 1, Speed: 4
USB\VID_174C&PID_3074 18
Descriptor for configuration #0: size 31
4. FilterID: 13, Port: 5, ID: 046d:c07d, Configs: 1, Speed: 2
USB\VID_046D&PID_C07D 097734723232
Descriptor for configuration #0: size 59
5. FilterID: 13, Port: 3, ID: 174c:2074, Configs: 1, Speed: 3
USB\VID_174C&PID_2074 3
Descriptor for configuration #0: size 41
6. FilterID: 13, Port: 13, ID: 054c:05c4, Configs: 1, Speed: 2
USB\VID_054C&PID_05C4 13
Descriptor for configuration #0: size 41
Bold is the DS4
When I start gimx_launcher I get
option -c with value 'Battlefield4.xml'
option -p with value 'COM3'
status flag is set
subpos flag is set
force_updates flag is set
Detected USB adapter: DS4.
using default refresh period: 10.00ms
A device name is empty. Multiple mice and keyboards are not managed.
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
etc.
Disconnects at around 10 seconds and I have to exit manually and restart it again to get another 10 seconds.
When I shift+esc I get
Exiting
src/windows/async.c:194 GetOverlappedResult failed with error: The I/O operation has been aborted because of either a thread exit or an application request.
Tested with 2 DS4s and 2 different official cables
Enumerate USB devices
Found 7 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
1. FilterID: 7, Port: 1, ID: 13fd:1340, Configs: 1, Speed: 3
USB\VID_13FD&PID_1340 57442D574341525731323639
Descriptor for configuration #0: size 32
2. FilterID: 9, Port: 1, ID: 8087:8009, Configs: 1, Speed: 3
USB\VID_8087&PID_8009 1
Descriptor for configuration #0: size 25
3. FilterID: 13, Port: 18, ID: 174c:3074, Configs: 1, Speed: 4
USB\VID_174C&PID_3074 18
Descriptor for configuration #0: size 31
4. FilterID: 13, Port: 5, ID: 046d:c07d, Configs: 1, Speed: 2
USB\VID_046D&PID_C07D 097734723232
Descriptor for configuration #0: size 59
5. FilterID: 13, Port: 3, ID: 174c:2074, Configs: 1, Speed: 3
USB\VID_174C&PID_2074 3
Descriptor for configuration #0: size 41
6. FilterID: 13, Port: 13, ID: 054c:05c4, Configs: 1, Speed: 2
USB\VID_054C&PID_05C4 13
Descriptor for configuration #0: size 41
Bold is the DS4
When I start gimx_launcher I get
option -c with value 'Battlefield4.xml'
option -p with value 'COM3'
status flag is set
subpos flag is set
force_updates flag is set
Detected USB adapter: DS4.
using default refresh period: 10.00ms
A device name is empty. Multiple mice and keyboards are not managed.
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)
etc.
Disconnects at around 10 seconds and I have to exit manually and restart it again to get another 10 seconds.
When I shift+esc I get
Exiting
src/windows/async.c:194 GetOverlappedResult failed with error: The I/O operation has been aborted because of either a thread exit or an application request.
Tested with 2 DS4s and 2 different official cables
Re: Using DS4 as a device within gimx config
Hi,
Thanks a lot for your tests, and for your patience.
I believe there is a bug in either GIMX 5.0 or USBDK 1.0.6.
Could you please do the following tests:
Thanks a lot for your tests, and for your patience.
I believe there is a bug in either GIMX 5.0 or USBDK 1.0.6.
Could you please do the following tests:
- Install GIMX 4.3, install USBDK 1.0.6, start GIMX and see if it works.
- Install GIMX 5.0, remove USBDK 1.0.6 using the Programs and Features panel, install USBDK 1.0.4, start GIMX and see if it works.
GIMX creator
-
- Posts: 39
- Joined: Sun Aug 16, 2015 12:58 am
Re: Using DS4 as a device within gimx config
I feel like I should be thanking you for your patience haha
I will be out of town for a day so I can't test it yet
Edit: Thank you for waiting. Here are my results:
GIMX 4.3 x64 + USB Dk 1.06 x64
PC connects to PS4 but get the "libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)" etc. and disconnect at 10 second bug.
GIMX 5.0 x64 + USB Dk 1.04 x64
I get the:
"Detected USB adapter: DS4.
libusb_init: Entity not found.
No controller was found on USB buses.
adapter_detect failed"
error.
Now to make sure that 4.3 x64 was working as normal with USB Dk 1.04 I gave that a try too after these tests. I got the same message as the 5.0 x64 + USB Dk 1.04 x64 result.
Now here's the thing. Before 5.0 came out, I never got 4.3 x64 to connect to my PS4. I actually came here on the forums and found someone else had this problem until he/she tried the i386 installer and said it worked for them. So I tried it too, and I too got it to connect to my PS4 perfectly. So after I ran these tests and tried 4.3 x64, I tried 4.3 i386 after and it worked perfectly with USB Dk 1.04, as I have been using GIMX. I can control the PS4 and I do not get the libusb error. Then I uninstalled USB Dk 1.04 and installed 1.06, and that worked perfectly too! Then I tried GIMX 5.0 i386 with the default USB Dk 1.06 and got the "adapter_detect failed" error. Same happened when I replaced USB Dk 1.06 with 1.04. Again, I'm running Windows 8.1 x64. I know it seems strange but these are my results. I hope it will help you. Thank you for being very patient and I find this software amazing. Thank you for all your hard work.
I will be out of town for a day so I can't test it yet
Edit: Thank you for waiting. Here are my results:
GIMX 4.3 x64 + USB Dk 1.06 x64
PC connects to PS4 but get the "libusb_transfer failed with status LIBUSB_TRANSFER_ERROR (endpoint=0x84)" etc. and disconnect at 10 second bug.
GIMX 5.0 x64 + USB Dk 1.04 x64
I get the:
"Detected USB adapter: DS4.
libusb_init: Entity not found.
No controller was found on USB buses.
adapter_detect failed"
error.
Now to make sure that 4.3 x64 was working as normal with USB Dk 1.04 I gave that a try too after these tests. I got the same message as the 5.0 x64 + USB Dk 1.04 x64 result.
Now here's the thing. Before 5.0 came out, I never got 4.3 x64 to connect to my PS4. I actually came here on the forums and found someone else had this problem until he/she tried the i386 installer and said it worked for them. So I tried it too, and I too got it to connect to my PS4 perfectly. So after I ran these tests and tried 4.3 x64, I tried 4.3 i386 after and it worked perfectly with USB Dk 1.04, as I have been using GIMX. I can control the PS4 and I do not get the libusb error. Then I uninstalled USB Dk 1.04 and installed 1.06, and that worked perfectly too! Then I tried GIMX 5.0 i386 with the default USB Dk 1.06 and got the "adapter_detect failed" error. Same happened when I replaced USB Dk 1.06 with 1.04. Again, I'm running Windows 8.1 x64. I know it seems strange but these are my results. I hope it will help you. Thank you for being very patient and I find this software amazing. Thank you for all your hard work.
Re: Using DS4 as a device within gimx config
Hi,
Thanks for the tests.
I think you have the same error as luk; http://gimx.fr/forum/viewtopic.php?p=7412#p7412
The problem was solved using a USB 2.0 port.
I believe this is a USBDK issue. I reported it there: https://github.com/daynix/UsbDk/issues/7
Thanks for the tests.
I think you have the same error as luk; http://gimx.fr/forum/viewtopic.php?p=7412#p7412
The problem was solved using a USB 2.0 port.
I believe this is a USBDK issue. I reported it there: https://github.com/daynix/UsbDk/issues/7
GIMX creator