-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DC controller no functional when test in Window10 and XP's game controller test App #12
Comments
Thank you for your interest in this project! I assume you are using this release, right? https://github.com/OrangeFox86/DreamcastControllerUsbPico/releases/tag/v0.1 The LED on the board should be on once connected to USB and off when any button is pressed on the controller or the analog stick is moved. That should be a quick test to make sure basic controller communication is working. I have been mainly using Windows 11 to develop this and https://gamepad-tester.com/ to quickly test things out. You should see P1, P2, P3, P4 there and pressing buttons should register. I have a feeling that Windows is going to have trouble labeling the 4 controllers right in some circumstances (possibly with older versions) which is why it looks like P4 is labeled for all on your system. I may put in a fix in the future to only enumerate connected controllers so that it will at least look fine when a single controller is connected. I can get you a custom single player variant of the uf2 in the meantime if it seems like that is the issue here. How many controllers are you trying to wire up at the moment? |
Looks like that page enumerates the controller properly. So far so good! It sounds like you're not getting communication with the controller. Check your wiring. You made me realize that I forgot to document the pinout at the port. Refer to the image here: http://www.raphnet-tech.com/products/dreamcast_usb_circuit/dc_connector_pinout.png That should correlate to the schematic here: |
hi Sir |
I've seen this happen before when using generic HID gamepad descriptors, and it seems to be a long-known bug with Windows DirectX/drivers from forum posts I have gone through. It still happens in Windows 11 now that I've actually looked. What's worse is that Windows doesn't even seem to sort them in the proper order. I'm assuming that the web interface is grabbing raw data instead of going through DirectX which is why things show up properly at gamepad-tester.com. I think my only options here would be to either use a different USB descriptor for the device like xinput or spin up my own driver. Using xinput seems to be what most controller manufacturers are doing these days in order to avoid writing drivers. I started playing with xinput, but then I got distracted with other things. It will likely be a few more months before this gets fixed. This project will likely be very helpful. |
many thanks your quickly support ,Sir but this project really a great project for let peoples enjoy DC game on PC like DC console |
Opened up #18 to fix that bug, and I'm closing this thread out |
Dear Sir
i used p2040 board and Main.uf2, when this board to PC(connect 1set DC controller on the board) ,the game controller test app can saw 4items "4P"
![image](https://user-images.githubusercontent.com/76941051/201583621-12f7d24d-f5ef-4292-a8c4-2105aadb02fd.png)
but my DC controller no functional on game controller test APP
please help me for fix it if you did know how to fix the problem
The text was updated successfully, but these errors were encountered: