Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

input gamepad don't work #120

Open
uratom962 opened this issue Apr 13, 2021 · 8 comments
Open

input gamepad don't work #120

uratom962 opened this issue Apr 13, 2021 · 8 comments
Labels

Comments

@uratom962
Copy link

Hi everyone,

When I want to configure my gamepad, on archlinux with Mednaffe, I try to set button, Mednaffe attribute auto assign touch for all button I Need, Like that : mednaffegif

For zsnes this gamepad work fine, but I need to desactive mouse in xorg, with this conf: /etc/X11/xorg.conf.d/51-joystick.conf

Maybe I have to enter a line for this touch ( Axis 2 - ST-LIS3LV02DL ) ?

@AmatCoder
Copy link
Owner

ST-LIS3LV02DL is not a touchpad but an accelerometer.

Some laptops (HP, ThinkPad...) has one and it can acts like an analogic gaming device.
See: https://www.kernel.org/doc/html/latest/misc-devices/lis3lv02d.html

Does it work fine if you set buttons into mednafen emulator (via ALT+SHIFT+1)?

@uratom962
Copy link
Author

I don't know where I do that ? Window ?

@mirrornoir
Copy link

I can confirm I've run into this issue as well, and you're right it was HP's hard drive fall protection accelerometer. This was easily solved in my case by running sudo rmmod hp_accel to remove the acceleration driver for the current session before launching mednaffe. I was then able to successfully bind my controller inputs.

@grubbyworm
Copy link

grubbyworm commented Aug 16, 2021

I have a similar issue when using a Dualshock 4 controller where it keeps assigning each input as something like "Axis 4- (Wireless Controller). I had the same exact thing happening with a different Dualshock 4 controller.
Untitled
Also assigning controls within Mednafen itself didn't seem to do anything but cause movement to freak out.

Just to see if it would work, I decided to use my older Xbox 360 controller, and managed to assign buttons as normal. Works perfectly. I'm still curious about what's happening on my system though, or whether there's a setting I'm missing that effects the DS4 or whatever. (Unless both of my PS4 controllers have the same exact issue)

EDIT: For anyone looking this stuff up, looks like you can get around it by using DS4Windows.

@goodstuff626
Copy link

Not sure if this is the same problem is this thread, but I tried the gui input settings for pc-engine to map my inputs with my ps3 controller and it would auto assign the same key without me pressing anything for every input. But if I used shift+alt+1 in game, it let me map the buttons correct.

@AmatCoder
Copy link
Owner

Can you tell me which key? And your OS?

@goodstuff626
Copy link

goodstuff626 commented Aug 25, 2022

I'm using Windows 10 & dshidmini "SDF mode" for ps3 controller input.
I will check exactly which key when I set up mednaffe on another PC i have, just give me a few days. (I think it was either a d-pad or analog directional input automatically inputting without pressing anything.)

Edit. - Ok. Just set it up on another PC, same as other setup, PS3 controller, Windows 10. It keeps registering "Axis-7" as soon as I clear the input without me pressing anything on the controller.

@TheTaraStark
Copy link

TheTaraStark commented Apr 24, 2024

Having this same issue today with my DS4. Is it possible Axis 4- is the gyro, and it's only an issue on DPad because DPad accepts axis inputs (instead of only accepting button inputs)?

I have a similar issue when using a Dualshock 4 controller where it keeps assigning each input as something like "Axis 4- (Wireless Controller). I had the same exact thing happening with a different Dualshock 4 controller. Untitled Also assigning controls within Mednafen itself didn't seem to do anything but cause movement to freak out.

Just to see if it would work, I decided to use my older Xbox 360 controller, and managed to assign buttons as normal. Works perfectly. I'm still curious about what's happening on my system though, or whether there's a setting I'm missing that effects the DS4 or whatever. (Unless both of my PS4 controllers have the same exact issue)

EDIT: For anyone looking this stuff up, looks like you can get around it by using DS4Windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants