Yes.Thanks for the quick answer, the values are hexadecimal?
The second value is the Maximum value. So the Value which will be needed at least to represent a maximum/fully pressed Stick on this axis.
Yes.Thanks for the quick answer, the values are hexadecimal?
It works!Yes.
The second value is the Maximum value. So the Value which will be needed at least to represent a maximum/fully pressed Stick on this axis.
mk8 (from memory) works like charm But it looks like my copy of ssb4 (disc) not work. Great program anyway man!No... At some point I broke it, but it should be fixed in the newest nightly. Can you confirm it?
https://github.com/Maschell/hid_to_vpad/releases/tag/HIDtoVPAD-v0.9g-nightly-e89bfbb
It's probably fixed in the newest nightlies. Can you try them and check if you still have these crashes?
From what I understand, currently no. I wanted to do that too to play 3rd Strike with the Xbone controller. If you search "RetroArch" in this thread there's an explanation as to why it can't.So as no other homebrew could be launched after HID to VPAD it would be impossible to play RetroArch games with a Xbox Controller?
It already has Wii Remote support. But currently you have to keep the Wiimote connected to apply the patches (which will occupie the first pro controller slot)Any possibility of a Wii U Gamepad-less interface for HID-VPAD? It would be great for those of us who use a Wii U without one and launch HBL through CBHC using a Wii Remote.
I actuallz took a look at the gyro data from the DS4 but couldn't parse the data in anything useful. So unfortunately it won't happen anytime soon.Gyroscopy emulation future version?
Currently it's not possible, but in theory it would be possible to use directly the controller patcher engine in RetroArch. But I don't know if anyone of the RetroArch team is actually interested in doing it (instead of using their own hid system)So as no other homebrew could be launched after HID to VPAD it would be impossible to play RetroArch games with a Xbox Controller?
Hey, so just wondering if rumble support for xinput devices through the client would be possible or not? You've done a great job on this, btw. It's working really well with my Gamestop Xbox 360 controller, with the exception of rumble support. Not noticing any latency, really, which is great. Thanks a lot for this wonderful application!
Well, I'll give it a try tomorrow. I'm not really experienced with homebrew, so I don't know how it'll turn out.@Gamer4647 You'll need an own config file. There is a wiki with all information you need: https://github.com/Maschell/controller_patcher/wiki/5.d-Controller-|-Adding-new-devices
[vid=0e6f,pid=011e]
DPAD_MODE = DPAD_NORMAL
VPAD_BUTTON_A = 0x00,0x04
VPAD_BUTTON_B = 0x00,0x02
VPAD_BUTTON_Y = 0x00,0x01
VPAD_BUTTON_X = 0x00,0x08
VPAD_BUTTON_PLUS = 0x01,0x02
VPAD_BUTTON_MINUS = 0x01,0x01
VPAD_BUTTON_HOME = 0x01,0x10
VPAD_BUTTON_LEFT = 0x02,0x06
VPAD_BUTTON_RIGHT = 0x02,0x02
VPAD_BUTTON_UP = 0x02,0x00
VPAD_BUTTON_DOWN = 0x02,0x04
VPAD_BUTTON_L = 0x00,0x10
VPAD_BUTTON_R = 0x00,0x20
VPAD_BUTTON_ZL = 0x00,0x40
VPAD_BUTTON_ZR = 0x00,0x80
VPAD_BUTTON_STICK_L = 0x01,0x04
VPAD_BUTTON_STICK_R = 0x01,0x08
VPAD_L_STICK_X = 0x03,0x80
VPAD_L_STICK_X_MINMAX = 0x00,0xFF
VPAD_L_STICK_Y = 0x04,0x80
VPAD_L_STICK_Y_MINMAX = 0x00,0xFF
VPAD_R_STICK_X = 0x05,0x80
VPAD_R_STICK_X_MINMAX = 0x00,0xFF
VPAD_R_STICK_Y = 0x06,0x80
VPAD_R_STICK_Y_MINMAX = 0x00,0xFF
[vid=0e6f,pid=011e]
DPAD_MODE = DPAD_HAT
DPAD_MASK = 0x0F
VPAD_BUTTON_A = 0x00,0x04
VPAD_BUTTON_B = 0x00,0x02
VPAD_BUTTON_Y = 0x00,0x01
VPAD_BUTTON_X = 0x00,0x08
VPAD_BUTTON_PLUS = 0x01,0x02
VPAD_BUTTON_MINUS = 0x01,0x01
VPAD_BUTTON_HOME = 0x01,0x10
VPAD_BUTTON_DPAD_N = 0x02,0x00
VPAD_BUTTON_DPAD_NE = 0x02,0x01
VPAD_BUTTON_DPAD_E = 0x02,0x02
VPAD_BUTTON_DPAD_SE = 0x02,0x03
VPAD_BUTTON_DPAD_S = 0x02,0x04
VPAD_BUTTON_DPAD_SW = 0x02,0x05
VPAD_BUTTON_DPAD_W = 0x02,0x06
VPAD_BUTTON_DPAD_NW = 0x02,0x07
VPAD_BUTTON_DPAD_Neutral = 0x02,0x0F
VPAD_BUTTON_L = 0x00,0x10
VPAD_BUTTON_R = 0x00,0x20
VPAD_BUTTON_ZL = 0x00,0x40
VPAD_BUTTON_ZR = 0x00,0x80
VPAD_BUTTON_STICK_L = 0x01,0x04
VPAD_BUTTON_STICK_R = 0x01,0x08
VPAD_L_STICK_X = 0x03,0x80
VPAD_L_STICK_X_MINMAX = 0x00,0xFF
VPAD_L_STICK_Y = 0x04,0x80
VPAD_L_STICK_Y_MINMAX = 0x00,0xFF
VPAD_L_STICK_Y_INVERT = True
VPAD_R_STICK_X = 0x05,0x80
VPAD_R_STICK_X_MINMAX = 0x00,0xFF
VPAD_R_STICK_Y = 0x06,0x80
VPAD_R_STICK_Y_MINMAX = 0x00,0xFF
VPAD_R_STICK_Y_INVERT = True
I've put this together...
Hopefully, this'll work with the program now.
Edit: All I need to do now is sort out the dpads input and invert the Y axis on both sticks.
Edit 2: Works properly now. Tested it on Splatoon, first in a practice session on Mahi Mahi Resort. Then, I played Turf War on the same map, just for Japanese players to destroy our team. After leaving the session though, the game crashed just after the plaza loaded. I have no idea what caused it, but the save was fine and everything else worked as it should.
Code:[vid=0e6f,pid=011e] DPAD_MODE = DPAD_NORMAL VPAD_BUTTON_A = 0x00,0x04 VPAD_BUTTON_B = 0x00,0x02 VPAD_BUTTON_Y = 0x00,0x01 VPAD_BUTTON_X = 0x00,0x08 VPAD_BUTTON_PLUS = 0x01,0x02 VPAD_BUTTON_MINUS = 0x01,0x01 VPAD_BUTTON_HOME = 0x01,0x10 VPAD_BUTTON_LEFT = 0x02,0x06 VPAD_BUTTON_RIGHT = 0x02,0x02 VPAD_BUTTON_UP = 0x02,0x00 VPAD_BUTTON_DOWN = 0x02,0x04 VPAD_BUTTON_L = 0x00,0x10 VPAD_BUTTON_R = 0x00,0x20 VPAD_BUTTON_ZL = 0x00,0x40 VPAD_BUTTON_ZR = 0x00,0x80 VPAD_BUTTON_STICK_L = 0x01,0x04 VPAD_BUTTON_STICK_R = 0x01,0x08 VPAD_L_STICK_X = 0x03,0x80 VPAD_L_STICK_X_MINMAX = 0x00,0xFF VPAD_L_STICK_Y = 0x04,0x80 VPAD_L_STICK_Y_MINMAX = 0x00,0xFF VPAD_R_STICK_X = 0x05,0x80 VPAD_R_STICK_X_MINMAX = 0x00,0xFF VPAD_R_STICK_Y = 0x06,0x80 VPAD_R_STICK_Y_MINMAX = 0x00,0xFF
Code:[vid=0e6f,pid=011e] DPAD_MODE = DPAD_HAT DPAD_MASK = 0x0F VPAD_BUTTON_A = 0x00,0x04 VPAD_BUTTON_B = 0x00,0x02 VPAD_BUTTON_Y = 0x00,0x01 VPAD_BUTTON_X = 0x00,0x08 VPAD_BUTTON_PLUS = 0x01,0x02 VPAD_BUTTON_MINUS = 0x01,0x01 VPAD_BUTTON_HOME = 0x01,0x10 VPAD_BUTTON_DPAD_N = 0x02,0x00 VPAD_BUTTON_DPAD_NE = 0x02,0x01 VPAD_BUTTON_DPAD_E = 0x02,0x02 VPAD_BUTTON_DPAD_SE = 0x02,0x03 VPAD_BUTTON_DPAD_S = 0x02,0x04 VPAD_BUTTON_DPAD_SW = 0x02,0x05 VPAD_BUTTON_DPAD_W = 0x02,0x06 VPAD_BUTTON_DPAD_NW = 0x02,0x07 VPAD_BUTTON_DPAD_Neutral = 0x02,0x0F VPAD_BUTTON_L = 0x00,0x10 VPAD_BUTTON_R = 0x00,0x20 VPAD_BUTTON_ZL = 0x00,0x40 VPAD_BUTTON_ZR = 0x00,0x80 VPAD_BUTTON_STICK_L = 0x01,0x04 VPAD_BUTTON_STICK_R = 0x01,0x08 VPAD_L_STICK_X = 0x03,0x80 VPAD_L_STICK_X_MINMAX = 0x00,0xFF VPAD_L_STICK_Y = 0x04,0x80 VPAD_L_STICK_Y_MINMAX = 0x00,0xFF VPAD_L_STICK_Y_INVERT = True VPAD_R_STICK_X = 0x05,0x80 VPAD_R_STICK_X_MINMAX = 0x00,0xFF VPAD_R_STICK_Y = 0x06,0x80 VPAD_R_STICK_Y_MINMAX = 0x00,0xFF VPAD_R_STICK_Y_INVERT = True
5.d Adding a new controllerYou had better luck then me. It took me over a week to figure out the instructions and I'm not illiterate, but I couldn't get the OR values figured out. If you're experiencing crashes you can log them and send them to the OP.
I think an OR value is just whatever a neutral/default/null value changes to while pressing a button, like from 0x00 to 0x04.the value when the button is pressed (More precisely: the value that BIT OR'd)