up & down (y-axis) not working in 3.8

SeC

Hi.
Is there any way to change Y axis back from 3 to 1? It's working fine in ES and libretro emu, for for atari800/scummvm I have to change source code and recompile with Y axis changes from 1 to 3. Everyone assumes that 0 is X and 1 is Y. In Zero Delay (aka Dragonrise USD gamepad) retropie detect Y axis as 3. On Windows, it's "normal".

Also anyone noticed that sometimes control got stuck (for example in OpenTyrian when pressing pushbutton A on title causes it to repeat as stuck, pressing it again unstuck it). Sometimes also when exiting MAME, joystick down is "stuck" (need to unstack by pushing joystick down).

mediamogul

@SeC

It seems like many people are having issues with this gamepad in linux. From what I was able to glean from a search, this is a PS3 controller? If so, all ps3 buttons are pressure sensitive and are read as axis input in linux. This isn't a problem in most parts of RetroPie, as many emulators will read any positive or negative axis readings as a binary on/off state. On the other hand, this confuses a few emulators with under developed joystick support that try to guess the different qualities of a controller. To me, it sounds like both your problems stem from this issue. I believe the emulators you mentioned are confused by the controller axis order and MAME might even be confused by the pressure sensitive buttons. If this turns out to be the case, I have corrected these issues before on a few unruly controllers by using xboxdrv, but I'll hold off on a full explanation in case I'm wildly off base with the diagnosis here.

suprjami

@mediamogul It's not a PS3 controller, it's an arcade encoder. It's a PCB with plugs which you connect arcade buttons to, they're commonly used when building an arcade cabinet with a PC (or Pi) in it. Look on eBay or Amazon for "Reyann Zero Delay" and you'll see the board these guys are using.

saulart

I have the same problem. After upgrading to version 3.8, the up & down stopped working. I have the board USB Zero Delay Arcade encoder. I reconfigured the Emulation Station and Retroarch, but PIFBA is not working the y-axis.

saulart

My solution to this problem was to install Recalbox 4.0 beta 3.

robthedude81

Hi

I have this Dragonrise joystick too. it seems to work when navigating the menus, until i load into a game, once i have loaded a game up it totally screws up the config and my buttons and joystick no longer work the way i have configured them.

How can i change this?

Thanks

dpalmeira

Hi robthedude81,
I have the same problem using FBA game and Dradonrise joystick. I tried to copy:
/opt/retropie/configs/all/retroarch-joypads/DragonRiseInc.GenericUSBJoystick.cfg
into /opt/retropie/configs/fba/retroarch.cfg file, but it does not effect.

Only change my insert coin and select buttons if I change the file /opt/retropie/configs/fba/fba2x.cfg , but with the stick up/down/left/right inside the game it doesn't works.

Any idea??

dpalmeira

I just changed the emulator:
https://github.com/RetroPie/RetroPie-Setup/wiki/runcommand

from pifba to lr-fba-next or lr-fba and the controls works well, but with mi RPI b+ it's too slow. When I use pifba the sound and game go much better but controls fails...

any suggestion?

Swampy

I also have the problem with the swapped axis in non libretro emulators!

I looked at this site:
https://github.com/raspberrypi/linux/issues/1527/

Perhaps a kernel-problem?

BuZz

Looks like it - thanks for the link.

lohocla

Anyone figure this out? I'm on 8 hours messing with this.

SeC

@lohocla I fixed this my hexediting HID driver for my USB arcade controller - there's two bytes needed to change - look at my issue reported here https://github.com/raspberrypi/linux/issues/1527/ to see which bytes must be swaped.

Swampy

Is it possible to publish this fix in the main linux kernel?
My linux main-system (Ubuntu 16.04/kernel 4.4.0-31-generic) also has this problem with the joypad!

GitHub driver:
https://github.com/torvalds/linux/blob/c05c2ec96bb8b7310da1055c7b9d786a3ec6dc0c/drivers/hid/hid-dr.c

Ravneson

Is there any way of implementing a quick fix? @SeC, is hexediting the driver something easily done? (googling has only led to a limited understanding of what hexediting is..)

SeC

@Ravneson You need to install hex editor (ht for example, http://hte.sourceforge.net/, it should be in apt database). Then find hid-dr.so (find / -name hid-dr.so), edit it, look for byte pattern:
09 30 09 33 09 32 09 31 09 34
replace with
09 30 09 31 09 32 09 33 09 34

(swap 31 with 33 and vice-versa)

save file, restart, should be ok. Don't remember if driver name is as I wroted (I'm at work now, can't check). Let me know if you need more help as I can prepare simple script to make that change if you don't make it :)

Ravneson

@SeC Got ht installed just fine, but stranded on finding the driver as you mentioned it. The closest I could find was "hid-dr.ko", but that couldn't be edited by ht (or at least didn't contain the expected content).. If it isn't too much of a bother it would be great if you could check the driver name as I gave a few suspicious candidates a try to no avail.. (a script would be very gracious of you, but I'm pretty sure I can manage to edit the patterns if I just find the right file :) )

Thanks ever so much for the help! :)

SeC

@Ravneson Hey, there are 2 locations to edit:
lib\modules\4.4.11+\kernel\drivers\hid
lib\modules\4.4.11-v7+\kernel\drivers\hid

file name is hid-dr.ko

MAke changes to both files, as I don't know which one will be loaded for you. Save changes then reboot, Y axis should be fine.

Look at the picture below, I've marked pattern you need to change (just swap 33 with 31, keep in mind those are hex values, not text). Picture is from windows box, so don't worry :)

Ravneson

@SeC Thank you!! :) :) That worked just brilliantly! (for anyone else having the same issue, hexcurse turned out to be a simple & fast hex-editor that can be installed & used on ones Pi)

Cheers!

BuZz

@SeC said in up & down (y-axis) not working in 3.8:

@lohocla I fixed this my hexediting HID driver for my USB arcade controller - there's two bytes needed to change - look at my issue reported here https://github.com/raspberrypi/linux/issues/1527/ to see which bytes must be swaped.

Did you report this upstream btw as mentioned https://github.com/raspberrypi/linux/issues/1527/#issuecomment-225559930 ? (Would be good to get the fix in a future release).

SeC

@BuZz Didn't have time to prepare proper patch with description, but I have this in my TODO list this week.