Reicast : Controller deadzone setting

themyst

@Aryetis Would you be kind enough to point us to where we might be able to read up on this? I'd be up to tweak the dead zone on my DS3 to make this work if needed.

hooperre

@themyst Are you having the same issue I am with a deadzone float? Currently, there is no other reading to be found as there is no deadzone setting associated with Reicast.

themyst

@hooperre Only on NBA Showtime with my Dual Shock 3. I connected my iBuffalo SNES replica, and this particular game played perfectly, albeit without analog. Reicast automatically recognized the controller without any setup necessary. Impressive considering this isn't a Retroarch core.

Powerstone was another analog-based game I've tested and this game doesn't exhibit the analog drift like NBA Showtime did, which leads me to believe it's an emulation issue for this particular title and nothing to do with the retropie drivers.

hooperre

@themyst Same issue. Same game. Dualshock 4. Also noticing it with Fur Fighters. It wasn't the case with previous releases of Reicast. If we could rollback to the first commit until we first noticed the issue happening, I bet it would be fixed.

mud2005

I noticed this while playing tee off golf so I changed
evdev_device_id_1 = -1
joystick_device_id = 0

now I see
joystick: Found 'Logitech Logitech Dual Action' with 6 axis and 12 buttons at '/dev/input/js0'.
in the console output and I can play w/o the drift issue, but have no idea how to map the controls, they seem to work fine as the defaults.
I'm not actually using retropie while testing, but reicast in linux mint, but I assume the config would work the same in retropie

hooperre

@mud2005 Thanks for the reply. Do you think you could add this info to my github issue request?

https://github.com/reicast/reicast-emulator/issues/1027

Thanks!

mud2005

sure thing, I was just doing some more testing and unfortunately the l/r shoulder buttons aren't working.
Is it possible to map controls using /dev/input/js0?

mud2005

I did some more research, I setup xboxdrv for my controller and set a massive deadzone of 50% and STILL got analog drift... wtf, I don't think the issue has anything to do w/ controller deadzone now.
but what is causing it then? changing to the /dev/inputjs0 driver removed the problem, so is it something to do w/ reicast's evdev setup?

Aryetis

@mud2005 said in Reicast : Controller deadzone setting:

I did some more research, I setup xboxdrv for my controller and set a massive deadzone of 50% and STILL got analog drift... wtf, I don't think the issue has anything to do w/ controller deadzone now.
but what is causing it then? changing to the /dev/inputjs0 driver removed the problem, so is it something to do w/ reicast's evdev setup?

Could be wrong but I'm pretty sure that reicast is using SDL to manage inputs, NOT xboxdrv. Therefore you can tweak xboxdrv settings as much as you want it won't change reaicast internal deadzone (or lack off)

mud2005

@aryetis
I'm seeing this in the console output:
evdev: Found 'Xbox Gamepad (userspace driver)' at '/dev/input/event17'
evdev: reading mapping file: 'controller_xboxdrv.cfg'

so from what I can tell it's using evdev and loading my gamepad at /dev/input/event17 which is the xbox gamepad defined in xboxdrv