search

kukugt / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

Analog controls in Smash Brothers #96

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Using my original controller (with USB converter) with Smash Brothers I
noticed something strange. In the menus, the analog stick works correctly,
but in-game, I am unable to jump and/or duck. If I map the analog controls
to other keys the movement works correctly. Other games seem to work fine
as well.

Original issue reported on code.google.com by michael....@gmail.com on 20 May 2008 at 11:54

GoogleCodeExporter commented 8 years ago 
Works flawlessly for me. I'm also using a USB adapter.
Is your adapter calibrated correctly? If not, u may try and mess around with 
jscal a
little.

Original comment by shinydo...@gmail.com on 20 May 2008 at 9:44

GoogleCodeExporter commented 8 years ago 
Hmm I have not yet used any calibration software but for other games 
(GoldenEye) it
just worked fine. Strange thing is that the stick even works correctly in the 
menus
of Smash Brothers but not ingame, where it looks like pressing up (down) does 
also
send the event for down (up). It's hard to explain but I rarely get the 
character to
jump/duck while all other movement/actions work fine.

Original comment by michael....@gmail.com on 21 May 2008 at 7:35

GoogleCodeExporter commented 8 years ago 
I have just the same problem, except I can fix it by calibrating my 
adapter/gamepad.
To be honest, it is a bit tedious to do it everytime you boot your system, but 
I'm
too lazy to write myself a udev rule doing to.
However, could you test Super Mario 64 and see, if he's running when you move 
the
control stick to its limit(s)? If not, it really might be a calibration thing.

Original comment by shinydo...@gmail.com on 21 May 2008 at 5:11

GoogleCodeExporter commented 8 years ago 
If this was a calibration issue then it should be fixable with the new
deadzoning/peak parameters in the latest SDL-Input plugin.  If the original 
reporter
tests with the latest code (build instructions in the Beta Testing header of the
google code page) and still experiences this problem, then please re-open the 
issue
report.

Original comment by richard...@gmail.com on 11 Jan 2010 at 3:43