-
Notifications
You must be signed in to change notification settings - Fork 62
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
Problem with a 6 buttons megadrive controller #18
Comments
I guess there is something with your wiring/soldering is causing this issue. Button 9 corresponds to the HOME button on the 8bitdo M30 2.4G wireless MD/Genesis controller. |
Using your "SegaControllerUSB" Sketch. My two Sega 3 Button Controllers Model 1650 and 1650-50 are working fine. Any Idea's? |
Hi Best regards |
Just a note, I got my 8BitDo Genesis M30 2.4g Controller which works perfect with the "SegaControllerUSB" Sketch. Really cool. Need to double check why the Sega 6 Button Controller Model SJ-6000 doesn't work at all. |
Please try the "SegaControllerUSB" sketch in this branch: https://github.com/MickGyver/DaemonBite-Retro-Controllers-USB/tree/SEGA-6-Button |
Tested. Nothing better with Sega 6 Button. No function at all. |
Yes, I just noticed it was a stupid attempt at a fix, I will look at it some more when I have the time. |
No hurry... |
I've run into a similar problem with my SegaTwoControllersUSB adapter and the retro-bit official 6 button controllers. Without pressing anything, x or y will fire seemingly randomly. I also tried the SegaControllerUSB with 6 button hack on your other branch. Then both non-branded and retro-bit 6 button controllers only had the dpad, A, B, C, and Start working. |
Hello I'm wondering if there is any development on this ? I have a licensed retrobit 6 button controllers and they don't work on the two daemon bite I've made for the mister |
I have similar issues, which led me to double check my wiring. I'm using MiSTer input test, and Windows 10 USB Game controller properties. I wonder if this issue is somehow related to device IDing? When I have Player 1 connected with a 2.4Ghz 8bitdo controller, it works perfectly. When I add another receiver to Player 2, it causes sporadic inputs on Player one. When I connect an OEM Genesis 1650 as Player 2 (still with the 8bitdo as Player 1), both function correctly. Narrowing it down, either it's getting confused by 2 controllers that are the same, or something related to the XYZ of Player 2. If I knew more about the coding I'd look into it, but I can say there's an issue with Player 2 using 6 button, OR controllers being ID'd as the same. I should also add that I continuity checked ALL pads on the Arduino, and nothing adjacent is bridged at all. |
Interesting, I will try my wired licensed retrobit 6 button with a OEM controller plugged in. It would be very interesting to understand why this particular controller doesn't work with the DaemonBite but in all of my Sega Genesis (Genesises?) they work flawlessly |
Yeah, it's puzzling for sure. I don't have a Sega-branded 6 button to try,
but I can say for certain that there's issues with using my 2x M30
controllers together.
I'm repeating myself a bit, but the Player 2 controller works perfectly if
it's the only one plugged in (nothing in P1 spot), but with them both
8bitdo, I can't get anything to trigger in the P2 test at all (and it
causes issues with P1 as mentioned), until I use a different controller; then P2 and P1 work perfectly.
That said, the NES version I built works perfectly with 2x 8bitdo
controllers, and so does the SNES version.
…On Thu., Sep. 30, 2021, 1:13 p.m. Jmaxime89, ***@***.***> wrote:
Interesting, I will try my wired licensed retrobit 6 button with a OEM
controller plugged in. It would be very interesting to understand why this
particular controller doesn't work with the DaemonBite but in all of my
Sega Genesis (Genesises?) they work flawlessly
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALW24YRFZU54CIN6GXFGUFTUESLE7ANCNFSM43XQHDCA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Which Core did you use for testing? |
Genesis core. I'm using a test rom called Sega Genesis 6 button controller test https://www.romhacking.net/homebrew/126/ |
I was able to fix this for retro-bit officially licensed controllers by commenting out the code that captures home button input. Lines 162 and 234 in SegaControllers32U4.cpp |
@treeswithhumanfaces I tried commenting those two lines, but it didn't fix the problem for my retro-bit controllers. Did you have any other changes you experimented with that might've gotten it working? |
Hi
I made the controller adapter for megadrive (SegaTwoControllersUSB)
tested under windows 10 with the windows game controller application
i have several problems
I use an official 6 buttons controller and an official 3 buttons
in 3 buttons mode everything works fine (even with the 6 buttons controller configured in 3 buttons (mode button))
but in 6 buttons mode when I use the Dpad I have some buttons that are activated (4,5,6,8,9)
for example (left +down):
and when I push on the x (4) y(5) or z(6) buttons they blink instead of staying on like A,B and C buttons
What does the button 9 correspond to when there are only 8 buttons ?
Sincerely (sorry for my bad english ;) )
The text was updated successfully, but these errors were encountered: