Then start a PS2 game via “pcsx2-config” and verify that the controls (and optionally your modified graphics settings) are working, then close that application.

You can also setup graphics settings at this point.

Start “pcsx2-config” and setup your controllers and verify that they are working correctly.

userdata/system/configs/PCSX2/PCSX2-reg.ini This issue could have been resolved if Batocera would not, upon launch of a PS2 game from Emulationstation, overwrite the configuration files in: I then launched “pcsx2-config” again and started a PS2 game and confirmed that all the controls were working perfectly.Īs soon as I exit out / go back to Batoceras Emulationstation and launch a PS2 game from the menu then my mappings are overwritten and again prevents the control sticks from working in all PS2 games - effectively preventing the PS2 emulator from being usable in Batocera 5.26. I figured out that I could (temorarily) fix that myself by starting “pcsx2-config” and correcting my mappings which then updated correctly in “/userdata/system/configs/PCSX2/inis/OnePAD.ini”. The sticks are unfortunately mapped incorrectly by Batocera in a way which prevents up and left directions on both sticks from working at all in all PS2 games. The issue here is the feature in Batocera auto-maps button mappings for the PCSX2 emulator combined with that Batocera overwrites any custom configuration for PCSX2 when launching any PS2 game from Emulationstation. These could be mapped without any problems in Batocera and they appear to work perfectly for what I have tested so far except for PS2 (PCSX2). I’m using 2x USB zero delay encoders (detected as: “DragonRise Inc. I’ve built an arcade machine and have installed Batocera 5.26 for PC (圆4) and it works great in general. That post and the info from the wiki below lead me in the right direction for finding a workaround for PS2. I found a post by below with the same type of issue + workaround for OpenBOR. I’m a new Batocera user and i really like it, the developers has been doing an amazing job so thank you for that! With some luck we might also see PCSX2 v1.6.0 in the next version. via an ini-file setting in 5.27 that makes it possible to use an existing configuration file (instead of overwriting that file, with auto-generated mappings and settings, each time a game is started via Emulationstation). Hopefully the developers will implement an option e.g. It did however become clear to me that the issue with incorrect auto-mappings for the control sticks appears to be an issue for several people (for systems like Wii/GC, PS2, OpenBor). Before finding the workaround I searched the forum for a solution but did not find any for PS2.

I have since then found a workaround (listed under “Workaround” below) and I’m therefore posting this info in the forums also in order to hopefully help others that may have the same issue. Yesterday I reported the issue below via the contact form.

Pcsx2 mac keyboard controls