You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not even sure that is an issue but is something that I noticed and I would like to report here.
I created a web configurator that should allow people to see the values of a controller and produce a file that can be used later to configure the ESP32S3 with this library. The problem is that on the web application I see for some controller a ReportID that I do not see on the ESP_USB_Host.
Here there is the link to test a game controller on the web, and for example the basic USB SNES clone controller display in the first byte the ReportID with a value 0, but when I plug the same device in the ESP32S3 and I check the data in the report, I see that the first value is directly the first direction of the controller and no ReportID is available.
While for more advanced controller (like the 8bitdo Pro 2) I see in the first byte a Report ID = 3 and the same in the ESP32S3.
The text was updated successfully, but these errors were encountered:
I am not even sure that is an issue but is something that I noticed and I would like to report here.
I created a web configurator that should allow people to see the values of a controller and produce a file that can be used later to configure the ESP32S3 with this library. The problem is that on the web application I see for some controller a ReportID that I do not see on the ESP_USB_Host.
Here there is the link to test a game controller on the web, and for example the basic USB SNES clone controller display in the first byte the ReportID with a value 0, but when I plug the same device in the ESP32S3 and I check the data in the report, I see that the first value is directly the first direction of the controller and no ReportID is available.
While for more advanced controller (like the 8bitdo Pro 2) I see in the first byte a Report ID = 3 and the same in the ESP32S3.
The text was updated successfully, but these errors were encountered: