Page 1 of 1

DIY Adapter - unhandled decriptor type: 0x24

Posted: Fri Aug 11, 2017 7:48 am
by mk_xboxone
Hi All,

I built a DIY-USB a while ago and had it running on my xbox one.

Change to PS4 and trying to get it working on there.

Steps Taken:

Reprogrammed the Board to EMUPS4\atmega32u4.hex
Connected PS4 Controller via USB
Powered on the PS4
Opened Gimx-launcher
Selected Dualshock4.xml from config
Clicked Start

Error is:

windows/gpirio.c:23 gprio: failed to set primary class
global option -c with value 'Dualshock4.xml'
controller #1: option -p with value 'COM3'
now reading arguments for controller #2
subpos flag is set
force_updates flag is set
USB adapter detected, controller type is: DS4
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
unhandled decriptor type: 0x24
Timer resolution: min=156250 max=5000 current=5000
using default refresh period 10.00ms

I then get a message box with a gimx error and request to debug or close.

What I have tried:

Reinstalled Gimx along with drivers
Run as administrator
Run zadig-2.3 and changed drivers for the Wireless Controller (Interface 0) and Wireless Controller (Interface 3) but no change

Thanks in advance here Matlo, appreciate the help

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Tue Aug 15, 2017 8:26 am
by Matlo
Please post the error message.

Also note that you should not install drivers with Zadig for the Dualshock 4.

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Wed Aug 16, 2017 4:43 am
by mk_xboxone
That the only Error I get above.

It literally has a Dialog that only says gimx error with a close button. Nothing else.

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Wed Aug 16, 2017 7:53 am
by Matlo
Select "Messages>Log file", click on Start, and reproduce the issue.
Then post the content of the log file.

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Fri Aug 18, 2017 5:40 am
by mk_xboxone
Hi Matlo,

If I leave the Messages to None I get the above error.

If I set it to txt I get a CMD window with:

windows /gprio.c:23 gprio: failed t set priority class

Then the gimx has stopped working and a debug option (Winodws default message)
Behind that another dialog with Gimx Error

Notepad popsup with no txt in the log.

Thoughts?

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Fri Aug 18, 2017 6:55 am
by Matlo
Which Windows version are you running?
Did you apply all Windows updates?
Did you uninstall the drivers installed with Zadig?

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Fri Aug 18, 2017 7:09 am
by mk_xboxone
Windows Build 16251.rs3_release.17.0721-2122

Fully up to date with Updates

Which drivers should the controller be using?

WinUSB 6.1.7600.16385
libusbK 3.0.7.0
lib-usb-win32 1.2.6.0

Cheers

Re: DIY Adapter - unhandled decriptor type: 0x24

Posted: Fri Aug 18, 2017 8:50 am
by Matlo
Is this a Windows insider version? Do you have any other version to try that is not a pre-release?

As said in the Installation page of the wiki the libusbk driver is only needed for the Xbox One controller.
You can safely uninstall the libusbk drivers from the device manager.