libretro / libretro/RetroArch

Playstation 2 (Play!) core - 2nd controller not functional

Open
#11,407 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

I have two PS3 bluetooth controllers that are automatically configured by retroarch and they work in other cores. However, with PS2 Play! core only one of the controllers is functional. When starting a game, it flashes the info messages for finding both controllers. I am attaching photos of the controller config within the core (F1) and from retroarch itself. I tested this configuration separately with PCSX2 and both controllers work there.

Expected behavior

Both controllers should work.

Actual behavior

Only one of the controllers work.

Steps to reproduce the bug
  1. Start any game with two player support and two controllers .
  2. Only one controllers works.
Bisect Results

I am new to retroarch, so this is my first installation. Can't really tell when this problem appeared.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: Aug 10, 2020, GIT revision 5e551dd (Debian Linux x64 installed from flathub).
Environment information
  • OS: Debian 10
  • Compiler: GCC 9.3.0
    retroarch-controller2
    retroarch-controller1
    in-game-controller2
    in-game-controller1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Play! core with two PS3 Bluetooth controllers on Debian 10, using the controller configuration and in-game behavior described in the report. Compare the result with PCSX2; the work is done when both controllers are detected and functional in a two-player game.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.