As soon as you enter the HBL "hid to vpad" gets unloaded againSuggestions I have would be
1. Launch homebrew Launcher after running this automatically.
As soon as you enter the HBL "hid to vpad" gets unloaded againSuggestions I have would be
1. Launch homebrew Launcher after running this automatically.
Don't bother with them, all they do is spam the thread.No need to be condescending and rude.
could you please try http://www.share-online.biz/dl/QZ9DPI8OPHA -> this ia a debug version with some more output
and generate a logfile when connecting the controller in loadiine and pressing a button or moving a stick ?
for each movement there will be some lines -> would be good if you could differ which lines come from which button/ direction movement
maybe if you do the steps above with the debug build and deliver the needed data maybe someone finds some time
we need the log when attaching the controller especially the lines with
vid xxxx
pid xxxx
and then the difference in the lines with HID: and about the 10 Bytes when pressing a button or moving a stick to a direction
we need for each button maybe the info pressing left is maybe byte 5 changes from 0x00 to 0x10 or like this
(for analog sticks we need byte position and range of values for the direction, most 00-7f, or 81-FF, 0x80 is in the middle untouched most times)
at the moment i dont know if i have to build a second debug version when you deliver the vid and pid -> tell me if you get the HID: + some Bytes lines
I hope this will help knowing which builds work or don't. Let me know if you need more help, I am pretty good at booting Loadiine GX2 now
so this sounds not very good
but without such a controller here it will be impossible for me to debug, it costs too much time to build x debug versions and analyse this controller
please try this version -> its build with latest loadiine but the old controller patcher
http://www.share-online.biz/dl/DODU5N8O5D8
I'm not very smart at this kind of stuff you see. Is this what you need?could you please try http://www.share-online.biz/dl/QZ9DPI8OPHA -> this ia a debug version with some more output
and generate a logfile when connecting the controller in loadiine and pressing a button or moving a stick ?
for each movement there will be some lines -> would be good if you could differ which lines come from which button/ direction movement
maybe if you do the steps above with the debug build and deliver the needed data maybe someone finds some time
we need the log when attaching the controller especially the lines with
vid xxxx
pid xxxx
and then the difference in the lines with HID: and about the 10 Bytes when pressing a button or moving a stick to a direction
we need for each button maybe the info pressing left is maybe byte 5 changes from 0x00 to 0x10 or like this
(for analog sticks we need byte position and range of values for the direction, most 00-7f, or 81-FF, 0x80 is in the middle untouched most times)
at the moment i dont know if i have to build a second debug version when you deliver the vid and pid -> tell me if you get the HID: + some Bytes lines
I'm not very smart at this kind of stuff you see. Is this what you need?
sorry but its too time consuming to do this all without having the controller here to debug and always building debug versions and waiting for response
i have more important things in my real life for spending that hours ;-)
if you want to try to build for yourself try to use the search for devkitpro / devkitppc / compile loadiine -> if not gbatemp but google will find some things
entry.o: In function `__entry_menu':
entry.c:(.text.__entry_menu+0x2a8): undefined reference to `SYSLaunchTitle'
entry.c:(.text.__entry_menu+0x31c): undefined reference to `SYSLaunchTitle'
entry.c:(.text.__entry_menu+0x338): undefined reference to `SYSLaunchTitle'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [/c/Users/A/Desktop/loadiine_gx2-Loadiine-nightly-0dffac5/loadi
ine_gx2.elf] Error 1
make: *** [build] Error 2
Once I figure it out I'll try to add the controller myself, but the hid I provided is correct.
Yeah I tried that and I still get the same error. Looks like there was some weird code in the entry.o file for smashbros. I was able to compile loadiine after I removed that weird line.did you used the msys.bat for the make call ?
Yeah I tried that and I still get the same error. Looks like there was some weird code in the entry.o file for smashbros. I was able to compile loadiine after I removed that weird line.
I have all of my inputs for my controller. How are the buttons converted from 00 00 00 00 00 00 00 00 to 0x00?
HID 00 00 0F 80 80 80 80 00 (Neutral)
HID 00 00 00 80 80 80 80 00 (Up)
HID 00 00 01 80 80 80 80 00 (Up-Right)
HID 00 00 02 80 80 80 80 00 (Right)
HID 00 00 03 80 80 80 80 00 (Down-Right)
HID 00 00 04 80 80 80 80 00 (Down)
HID 00 00 05 80 80 80 80 00 (Down-Left)
HID 00 00 06 80 80 80 80 00 (Left)
HID 00 00 07 80 80 80 80 00 (Up-Left)
HID 10 00 04 80 80 80 80 00 (L-Trigger)
HID 20 00 04 80 80 80 80 00 (R-Trigger)
HID 30 00 00 80 80 80 80 00 (L+R Trigger)
HID 01 00 04 80 80 80 80 00 (Y)
HID 02 00 04 80 80 80 80 00 (B)
HID 04 00 00 80 80 80 80 00 (A)
HID 08 00 00 80 80 80 80 00 (X)
HID 03 00 00 80 80 80 80 00 (Y+B)
HID 05 00 00 80 80 80 80 00 (Y+A)
HID 09 00 00 80 80 80 80 00 (Y+X)
HID 06 00 00 80 80 80 80 00 (B+A)
HID 0A 00 00 80 80 80 80 00 (B+X)
HID 0C 00 00 80 80 80 80 00 (X+A)
HID 00 01 00 80 80 80 80 00 (select)
HID 00 02 00 80 80 80 80 00 (start)
HID 40 00 00 80 80 80 80 00 (ZL)
HID 80 00 00 80 80 80 80 00 (ZR)
HID 00 03 00 80 80 80 80 00 (select+start)
HID 40 01 00 80 80 80 80 00 (select+ZL)
HID 80 01 00 80 80 80 80 00 (select+ZR)
HID 40 02 00 80 80 80 80 00 (start+ZL)
HID 80 02 00 80 80 80 80 00 (start+ZR)
HID C0 00 00 80 80 80 80 00 (ZL+ZR)
HID 00 00 0F 80 80 80 80 00 (Neutral)
HID 00 00 00 80 80 80 80 00 (Up)
HID 00 00 01 80 80 80 80 00 (Up-Right)
HID 00 00 02 80 80 80 80 00 (Right)
HID 00 00 03 80 80 80 80 00 (Down-Right)
HID 00 00 04 80 80 80 80 00 (Down)
HID 00 00 05 80 80 80 80 00 (Down-Left)
HID 00 00 06 80 80 80 80 00 (Left)
HID 00 00 07 80 80 80 80 00 (Up-Left)
HID 10 00 0F 80 80 80 80 00 (L-Trigger)
HID 20 00 0F 80 80 80 80 00 (R-Trigger)
HID 30 00 0F 80 80 80 80 00 (L+R Trigger)
HID 01 00 0F 80 80 80 80 00 (Y)
HID 02 00 0F 80 80 80 80 00 (B)
HID 04 00 0F 80 80 80 80 00 (A)
HID 08 00 0F 80 80 80 80 00 (X)
HID 03 00 0F 80 80 80 80 00 (Y+B)
HID 05 00 0F 80 80 80 80 00 (Y+A)
HID 09 00 0F 80 80 80 80 00 (Y+X)
HID 06 00 0F 80 80 80 80 00 (B+A)
HID 0A 00 0F 80 80 80 80 00 (B+X)
HID 0C 00 0F 80 80 80 80 00 (X+A)
HID 00 01 0F 80 80 80 80 00 (select)
HID 00 02 0F 80 80 80 80 00 (start)
HID 40 00 0F 80 80 80 80 00 (ZL)
HID 80 00 0F 80 80 80 80 00 (ZR)
HID 00 03 0F 80 80 80 80 00 (select+start)
HID 40 01 0F 80 80 80 80 00 (select+ZL)
HID 80 01 0F 80 80 80 80 00 (select+ZR)
HID 40 02 0F 80 80 80 80 00 (start+ZL)
HID 80 02 0F 80 80 80 80 00 (start+ZR)
HID C0 00 0F 80 80 80 80 00 (ZL+ZR)
NO ;-)
i dont know what your problem is
How hard is it to map the Wii U gamepad gyro to mouse?
#define HID_POKKEN_BUTTON_DPAD_N 0x00
#define HID_POKKEN_BUTTON_DPAD_NE 0x10
#define HID_POKKEN_BUTTON_DPAD_E 0x20
#define HID_POKKEN_BUTTON_DPAD_SE 0x30
#define HID_POKKEN_BUTTON_DPAD_S 0x40
#define HID_POKKEN_BUTTON_DPAD_SW 0x50
#define HID_POKKEN_BUTTON_DPAD_W 0x60
#define HID_POKKEN_BUTTON_DPAD_NW 0x70
#define HID_POKKEN_BUTTON_DPAD_NEUTRAL 0xF0
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_N], 0x05,HID_POKKEN_BUTTON_DPAD_N);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_NE], 0x05,HID_POKKEN_BUTTON_DPAD_NE);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_E], 0x05,HID_POKKEN_BUTTON_DPAD_E);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_SE], 0x05,HID_POKKEN_BUTTON_DPAD_SE);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_S], 0x05,HID_POKKEN_BUTTON_DPAD_S);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_SW], 0x05,HID_POKKEN_BUTTON_DPAD_SW);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_W], 0x05,HID_POKKEN_BUTTON_DPAD_W);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_NW], 0x05,HID_POKKEN_BUTTON_DPAD_NW);
setConfigValue((u8*)&config_controller[CONTRPD_POKKEN][CONTRPS_VPAD_BUTTON_DPAD_NEUTRAL], 0x05,HID_POKKEN_BUTTON_DPAD_NEUTRAL);
I honestly don't know what to put there. Why is the default 0x05? What should I be looking at to put in the correct result? If I compile as is, then nothing works, so I'm thinking the 0x05, 0x06 are wrong?