Now the 0x76 counts as 0x80 and 0x86 as 0x80. The sticks postions are now scaled to the valid area.Let's say you have a config file that looks like this
VPad_L_Stick_X=0x03,0x80
VPad_L_Stick_X_MinMax=0x00,0xFF
VPad_L_Stick_X_Deadzone=0x0A
Which means, movement counts from 76 to 00, and 8A to FF.
However, when you set the deadzone, when you reach 76, it counts as 76 on the gamepad. And 0x86 counts as 0x86
Sorry, had a bug displaying the correct number of loaded files.
Seems to be working now. Holding either stick completely up or down causes them to input the opposite direction but that seems like a problem with the controller config. Otherwise great appTry version 0.9a: https://github.com/Maschell/hid_to_vpad/releases/tag/0.9a
Does it still say no valid files found?
I also improved the deadzone handling.
Here a qoute from @PeeJay Bonobo
Now the 0x76 counts as 0x80 and 0x86 as 0x80. The sticks postions are now scaled to the valid area.
that happen to me as well, for some reason using the HiDTest fixes the issueI downloaded the latest loadiine and using my ps3 controller isn't working correctly. The left stick doesn't register left or right, up moves left and down moves right.
Wow using hidtest does fix the broken ps3 controller problem thank you. Is it just loadiine thats doing this or is hidtovpad doing this too.that happen to me as well, for some reason using the HiDTest fixes the issue
for my experience both Loadiine and HiDtoVPad does itWow using hidtest does fix the broken ps3 controller problem thank you. Is it just loadiine thats doing this or is hidtovpad doing this too.
I don't have a DS4 Pad, so I can't test it.Will we ever be able to use the DS4's sixaxis for the Wii U's gyro controls?
I don't have a DS4 Pad, so I can't test it.
btw. make sure to check out my twitter to get some extra information
I'm a little bit excited guys: Yesterday I started to look the the Pro Controller spoofing and got first result!
Don't except any release in near future, a LOT of work is still needed to be done.
that happen to me as well, for some reason using the HiDTest fixes the issue