Multitap for psx broke in latest update
-
Hi all,
This has been driving me mad since yesterday but I can confirm it's something to do with the latest update either retroarch or pcsx rearmed core I think.
I use a raspberry pi3b with the official 4.4 image.
4 ps3 controllers over bluetooth all bios files in place etc etc.
So here is the deal, all I really play is 4 player games with friends and family, many of hours on hogs of war, team buddies, crash team racing etc.
Until yesterday, I powered everything on went to play and unfortunately player 3 and 4 doesn't work only on psx games though, arcade I can use all 4 players, mega drive micro machines 4 players fine but not psx 4 player title works.
So I check my settings that I usually setup to see if anything wrong.
Game specific options=true
Then I go to options whilst game is loaded, set multitap 1 to enable, save game specific options, then I reload the game.
After that it usually always works fine.
It will detect a multitap as it lets me pick 4 players in games that don't normally show 4 players, but when it gets to character selection screen player 3 and 4 do not work at all.So what I have done is pulled out a spare sd card, installed fresh image configured like I normally do, everything works fine.
Then I update all installed packages with retropie script, reboot and then the psx multitap no longer works.Another thing to mention is I also tried lakka, the latest version of lakka also doesn't work with player 3 and 4.
But it's worth mentioning that earlier versions of lakka have also worked as I tried it a while back for a couple of month on a spare sd card.Hope some one can help :(
Thanks in advance -
@robmcc83 I suppose you can always manually checkout and compile an older version of the emulator. If you end up finding out that it is, in fact, an emulator problem, do submit the issue to the actual emulator git repository.
-
I wouldn't know where to start compiling a older version lol.
Suppose I'll just have to submit problem to repository and wait until a update is applied :(
Would it be pcsx rearmed git that I have to report the problem.Thanks
-
It would be here:
https://github.com/libretro/pcsx_rearmed
I'm not on my laptop and pi at the moment otherwise I would be glad to try and share some pointers on how to checkout an older version and compile it. Are you per chance somewhat comfortable with the unix command line?
-
Yeah I would say I'm comfortable with command line, used it many of times on other projects :)
Thanks -
@robmcc83 sounds good!
In my case, I’d create a new folder and checkout the lr-pcsx-rearmed code to that folder.
cd ~/ mkdir pcsx cd pcsx git clone https://github.com/libretro/pcsx_rearmed.git cmake . ./configure --platform=libretro --disable-neon
The cmake command might not be needed, it’s been a while.
Then, it’s just a matter of checking out an older commit from the project, which you can see the hgashes from in the commit history:
https://github.com/libretro/pcsx_rearmed/commits/master
It’s the 7-character hash in each commit line.
28ea3e2 is the latest one. You may start with 40c380a and see if it works.
git checkout 40c380a
and then build it
make clean make
and then copy it to the right folder at
sudo cp libretro.so /opt/retropie/libretrocores/lr-pcsx-rearmed/
and run it. See if it works. If not, try another commit (likely an older one).
You can always restore it to the original one by updating via the RetroPie-Setup script.
In fact, if you want to go about it and make it easier to fix for the folks over at the actual project repository, you may consider helping bisect it to the right commit. If that’s something you’d be interested in investigating, let me know and I can share instructions.
There’s the odd chance that it’s not an emulator issue but rather a libretro/RetroArch issue. That I’d not be as comfortable with, but I’m sure others can help track it down.
Let me know if it helps, and best of luck. If something doesn’t quite work, just let me know, as I didn’t test this, just wrote it from memory and checking the source for the install script at:
Happy new year!
-
Hi and happy new year to you too :)
only just had chance to look at this as I've had a sore head due to, to much beer last night lol.
I'll have a play around tomorrow and let you know the outcome.
On my spare 8gb sd card I'm going to start with a fresh image, check everything works fine.
Then I'm going to update via retropie script (That's when multitap stops working)
I'll then work my way through compiling the core as you suggest, if one version work I'll work my way through them until I find which version it has stopped working in.
Many thanks
Rob -
@robmcc83 If you really want to test it, I'd also do the following test
- install from the 4.4 image
- update from binary
- (after the update) set up Multitap options in
pcsx_rearmed
.
Also, could you post your
/opt/retropie/configs/retroarch-core-options.cfg
file ? -
Hi all,
So just tried this and I have 2 errors
The first is the cmake command it tells me the source directory doesn't contain any cmakelists.txtSo as you said it might not be needed I went onto the next command and that gives me error bash ./configure : no such directory.
Many thanks
-
Ignore that last reply.
I had to change directory to /pcsx/pcsx_rearmed as it seems to of created another directory during the process.
Seems to be going ahead now :) -
Right so doing the above seems to have broke alot within pcsx.
I'm not quite sure it has worked but it has done something.
It says it pcsx r22 within retroarch but doing the above has added shaders that were not on there before and it has broke graphics as I just have multi coloured line on everything 3d but 2d stuff appears to be showing correctly.
Thanks -
@mitu
How do I post the /opt/retropie/configs/retroarch-core-options.cfg
So it looks neat like other people do on here. Thanks
To -
To post a code formatted block, surround the lines quoted in backticks (
```
) on separate lines at the beginning and end. -
Ok so I think I may have solved my issue which maybe a silly error on my behalf or something has still changed in later versions of retropie because I don't think I've ever had to change controller types.
But even though I've solved one problem it appears to have created an new problem.
Firstly I'll start with saying with default settings I usually have just turned on game specific options, started game, enabled multitap 1 in retroarch and all has worked. But it hasn't this time that's why I've had problems.
But what I have just done is changed player 1-4 controller type from default to standard and micro machines v3 has just worked with all 4 controllers.
I've then launched hogs of war and that has worked making sure controller type is analog.So firstly i would like to know why player 1 and 2 controller would work with them all being on default but controllers 3 and 4 wouldn't.
Now onto my new problem.
When setting multitap and controller type in options and saving game specific options, a yellow notification pops up saying core options saved.
And it appears to be saving it across all games as a core option rather the game specific option.
I have double checked and game specific options are set to true.Thank you all for your help I'm almost there :)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.