PSX analog controls broken

langy1987

Tested this morning.

Setting all 8 to analog does indeed fix it, for Player 1 only though.

Those of you who like to do multiplayer with analog will have to wait for a long term fix :(.

backstander

@langy1987

This is what I did to get my Xbox 360 left analog stick to work in lr-pcsx-rearmed:

/opt/retropie/configs/psx/retroarch.cfg

# Joypad w/ Analog (RetroPad + Analog sticks): 5
input_libretro_device_p1 = "5"
input_libretro_device_p2 = "5"
Input_libretro_device_p3 = "5"
Input_libretro_device_p4 = "5"

# Use analog stick as dpad (left stick = 1, right stick = 2)
input_player1_analog_dpad_mode = "1"
input_player2_analog_dpad_mode = "1"
input_player3_analog_dpad_mode = "1"
input_player4_analog_dpad_mode = "1"

#include "/opt/retropie/configs/all/retroarch.cfg"

langy1987

@backstander yea this 'works' but the downside is the stick is not truly analog and is emulating the dpad.

At this moment in time the only way to get true analog is to do what @edmaul69 advised which currently only fixes Pad1.

backstander

@langy1987
Yeah it's more for the older pre-analog stick PSX games.
Maybe try removing all the input_player#_analog_dpad_mode = "1".

bmn001

Sooo...Has anyone tried reporting this to the team?

I don't see an issue for it... Is this the right project? https://github.com/notaz/pcsx_rearmed/issues

PetroRie

Thats why you shouldn't update if the current version works fine. Sorry but I dont want to sound harsh but I had other problems when I updated the Pie. I'm still on v4.0.2 and everything works fine.

mediamogul

@PetroRie

Mileage always varies where updates are concerned. I've updated my highly customized, 37 system setup with almost every point release for almost nine months now and the only time I've had trouble worth mentioning was with eDuke32 and that issue was taken care of within a month's time.

Updates always have the potential to result in regressions, but it's also worth noting that not updating has it's own set of pitfalls to deal with that often necessitate starting over completely from scratch when moving forward is finally needed. Neither approach is perfect, but neither is a terrible choice either.

bmn001

Filed a bug.

https://github.com/notaz/pcsx_rearmed/issues/79

dankcushions

wrong repo. https://github.com/libretro/pcsx_rearmed

herb_fargus

Possibly related to this commit:

https://github.com/libretro/pcsx_rearmed/commit/8342a30082638cc032c53e073f893e82f149fcb7

I haven't really tested myself but you can try rebuilding before that to see if the issue is resolved, that way you'll know that it was a commit after it that broke it.

PetroRie

@mediamogul That is kinda true bro. I used to update everything until I couldn't play MAME games anymore

bmn001

For anyone who wants to track progress on this (or chime in with their own experience) I re-filed the bug in the correct repo:
https://github.com/libretro/pcsx_rearmed/issues/88

Thanks for the clarification, @dankcushions

bmn001

This appears to be fixed...

I updated Retropie setup to 4.1.10 just now, then did an 'install from source' for lr-pcsx-rearmed.

That fixed it! I can set pad 1 to "analog" and keep the rest as "standard" and this is now correctly detected by any games I play.

I'm super confused by this, because it doesn't look like there have been any commits to this core since I filed the bug. Maybe it was a RetroPie bug?

Can anyone else who's been having this problem please try updating your biz and let me know if it fixes it for you too?