#Nacon revolution pro 1 vs 2 how to#

On Sun, Sep 22, 2019, 8:39 AM SiliconExarch It's 2019 so I don't know if this will even get any attention but my The Pro Controller 1 and it still works on my PS4. On Sun, Sep 22, 2019, 8:44 AM Sirath Icebreath wrote: If I can provide any more information to help iron out these issues I'm more than happy to. It reports a MAC address of all zeroes in the log (makes sense since it doesn't have bluetooth) and often doesn't appear in the Controller list at all when connected aside from the USB icon.

Some games tend to ignore this unless you're trying to use the d-pad whereas it renders others unplayable. With this device disabled it can enumerate the controller (Exclusive mode is sporadic) and everything apart from the touchpad works (including the gyros and light strip), although the d-pad is stuck scrolling to the left despite no input being shown in the controller properties. Modifying the search routine allows it to detect the controller however it fails to enumerate it with the error 'Index was outside the bounds of the array' unless the HID-compliant vendor-defined device (VID_146B&PID_0D01&REV_0100&MI_03&Col02) is disabled in device manager. I have had limited success in getting my Nacon Revolution to work with DS4Windows. Reply to this email directly, view it on GitHub You are receiving this because you authored the thread. PS4 controller reports so the code would only have to be changed to check I was just hoping that the Nacon Revolution would still conform to standard

Much work to modify DS4Windows to get it to work with the Nacon Revolution. Even with the HID report descriptors, it might be too Windows obtaining an HID report descriptor looks like an easier task to

#Nacon revolution pro 1 vs 2 how to#

I don't know how to obtain the HID report descriptors for a device on Is detected before failing to read a report. Does DS4Windows show anything in the Log tab regarding detecting theД¬ontroller at all? Even though the code is structured so the device mightДЄttempt to read and then remove the device before a log message wouldДЄppear, there is a chance that DS4Windows would acknowledge that the device