USB4MAPLE adapter

[megavolt85]

and also rotate the oled screen display 180º because of solder position I can't rotate it physically)

put to your fash card blank file with name lcdrotate

[Quiquonn]

Thank you @megavolt85 I will try it asap!

[Quiquonn]

I flashed the pico with this new uf2, and then I added a blank file with name lcdrotate in the usb storage where the vmu images are, but the screen is still in 180deg rotated, what I'm doing wrong?

and also rotate the oled screen display 180º because of solder position I can't rotate it physically)

put to your fash card blank file with name lcdrotate

usb4maple(16.05.25).7z

[Roger150]

same problem for me. the lcd are 180°

edit: new problem, after the screen rotate right, the picture ist mirrored

[megavolt85]

fixed

usb4maple(17.05.25).7z

(57.64 KiB) Downloaded 26 times

[Paxtez]

@megavolt85

The XInput is the PC mode of the GP2040. Freshly installed the PC mode is pretending to be an xbox 360 controller [ VID_045E&PID_028E#00706FA]

USB DUMP:

GP2040-XINPUT-Stock.txt

(20.42 KiB) Downloaded 20 times

You can override the VID/PID but it is hidden behind two different warnings.

Setting the VID/PID to that does set it to be a random device by Silicon Laboratories, with that VID/PID but that device is not usable by windows as a controller.

USB DUMP:

GP2040-XINPUT-Override.txt

(27.06 KiB) Downloaded 17 times

But even when in that mode, it still isn't recognized by USB4MAPLE.

I am able to have USB4MAPLE see my PS4 controller, and my GP2040 stick when in PS3 mode, so it appears that my wiring is correct.

GP2040 has its own layout that is completely consistent with the DC arcade stick, do not use PS3/PS4/XBOX etc.. modes, you need to use PC mode in which GP2040 has VID 10C4 and PID 82C0.

[megavolt85]

viewtopic.php?p=185510#p185510
Direct input, not X input

[Paxtez]

@megavolt85

Ahh, progress. I was confused since the label to that says "PS3/Direct Input" direct input isn't an option, but PS3.

But after looking at the debug log, that mode is called "Generic HID" on the GP2040.


So, it looks like the inputs are mapped incorrectly, neutral was being seen as U, and I couldn't really trigger down.

I also couldn't change the USE4MAPLE mode when in this mode, it looks like the home button also had the wrong code.

I wrote a windows usb debugger and here is the correct input codes for "Generic HID" mode. I think the neutral state shifted the directionals down.

(My debugger only has the raw codes, not second part like yours does.)

Code: Select all

HID Device: GP2040-CE (Generic) (VID: 10c4 PID: 82c0)

00 00 00 00 08 80 80 80 80: Neutral

// Please map both DPAD and left analog to DC. Different sticks use different input methods, currently only one is mapped //
00 00 00 00 08 80 00 80 80: UP [Left Analog]
00 00 00 00 08 00 80 80 80: LEFT [Left Analog]
00 00 00 00 08 80 ff 80 80: DOWN [Left Analog]
00 00 00 00 08 ff 80 80 80: RIGHT [Left Analog]

00 00 01 00 00 80 80 80 80: UP [D Pad]
00 00 04 00 06 80 80 80 80: LEFT [D Pad]
00 00 02 00 04 80 80 80 80: DOWN [D Pad]
00 00 08 00 02 80 80 80 80: RIGHT [D Pad]

/// Ignore these ///
00 00 00 00 08 80 80 80 00: UP [Right Analog]
00 00 00 00 08 80 80 00 80: LEFT [Right Analog]
00 00 00 00 08 80 80 80 ff: DOWN [Right Analog]
00 00 00 00 08 80 80 ff 80: RIGHT [Right Analog]

// These were correct //
01 00 00 00 08 80 80 80 80: DC X [GP2040 B3]
08 00 00 00 08 80 80 80 80: DC Y [GP2040 B4]
20 00 00 00 08 80 80 80 80: DC Z [GP2040 R1]
02 00 00 00 08 80 80 80 80: DC A [GP2040 B1]
04 00 00 00 08 80 80 80 80: DC B [GP2040 B2]
80 00 00 00 08 80 80 80 80: DC C [GP2040 R2]

00 02 00 00 08 80 80 80 80: Start [GP2040 S2]
00 01 00 00 08 80 80 80 80: Select [GP2040 S1] // Also also map this to start? S1 and S2 are the main start buttons for the board
00 10 00 00 08 80 80 80 80: Home [GP2040 A1]

/// Ignore these ///
00 20 00 00 08 80 80 80 80: Share [GP2040 A2]
10 00 00 00 08 80 80 80 80: LB [GP2040 L1] // Some people would love this being mapped to X+Y+Z, I kinda think it's cheating, lol
40 00 00 00 08 80 80 80 80: LT [GP2040 L2] // Some people would love this being mapped to A+B+C, I kinda think it's cheating, lol
00 04 00 00 08 80 80 80 80: L3 [GP2040 L3]
00 08 00 00 08 80 80 80 80: R3 [GP2040 R3]

If you didn't have any plans for the L/R + Home modes, could you make those go to arcade stick modes (with "R1" being mapped to "Z" and "R2" being
mapped to "C"), in addition to the Z/C + Home?

That would be hugely helpful because many people do "pad-hacks" where they solder controller PCBs to arcade buttons. Most of the time for fighting sticks and games, R1 is the 3rd top button, R2 is the 3rd bottom button. So those sticks would never work with USB4MAPLE since they would always be detected as whatever the PCB is. And since it would be a PS3 pad or whatever both R buttons would be mapped to R so they wouldn't have access to their L button. This would allow them to go to that mode and use their stick with USB4MAPLE.

FWIW One of the biggest users of Dreamcasts now are the fighting game community. I've many thousands of hours on DCs during local sessions over the last 25 years. We will often have 2-3 DCs going for 5-10 hours per session, with 1-3 sessions per week.

viewtopic.php?p=185510#p185510
Direct input, not X input

[megavolt85]

it seems that at some point in the GP2040CE project the Generic HID mode changed, after two bytes with the state of the buttons they added two more bytes, one with the state of the d-pad and one empty, so compatibility with usb4maple broke.
fixed for the new GP2040 firmware, check

usb4maple(18.05.25).7z

(57.63 KiB) Downloaded 19 times

[Paxtez]

@megavolt85

Awesome that works!


- When it arcade stick mode ideally both dpad and left analog should map to the directionals on the DC

- HOME button doesn't seem to work, when in 240p test pressing it doesn't blink it out like it does with other devices.

- Could we try making HOME+L/R also enable arcade stick mode? Arcade sticks are going to be used a whole lot more often than twin sticks (sorry Virtual On Fans!)

- Do you have a Kofi/Paypal/Venmo?

it seems that at some point in the GP2040CE project the Generic HID mode changed, after two bytes with the state of the buttons they added two more bytes, one with the state of the d-pad and one empty, so compatibility with usb4maple broke.
fixed for the new GP2040 firmware, check
usb4maple(18.05.25).7z