Vba-m won't open with wii u pro controller connected #444
Comments
|
Get a real xbox 360 controller, bluetooth pads are odd spec wise. |
|
What i think is strange is that, i don't have this problem with anything else. All my pc games and emulators run normally, only vba-m won't run with my controller |
|
@Birutath Thanks for the report. This is a little tough to debug because I believe we don't have someone who owns this controller... We can take a look, but it won't be high priority. |
|
My guess is that SDL2 isn't picking up on that properly. May need to add a special case for that. |
rkitover
added a commit
that referenced
this issue
Jun 24, 2019
Check that SDL reports any available controls for a joystick, otherwise mark it invalid and close it. When processing events for joysticks, check that each one is valid. Set initial value of controls to zero initially not after getting the initial state, previously we were getting the initial state and overwriting it with zeroes, defeating the purpose. Fix memory leak, `curval` array of controls not being cleared. Signed-off-by: Rafael Kitover <rkitover@gmail.com>
|
The error should be fixed, as for the joystick you might look into SDL2 settings. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please fill out this form:
Expected behavior
To open normaly and recognize the controller as a xbox 360 one
Actual behavior
Won't open, and insted gives a pop up that reads "unhandled Standard exception of type "st20bad_array_new_lenght" with message std::bad_array_new_lenght"; terminating the application"
Steps to reproduce the behavior
Use a wii u pro controller with wiinUsoft app, and try to open vba-m
Build details
Operating System: Windows 10 pro 64 bit
Version of code: 2.1.3
The text was updated successfully, but these errors were encountered: