libretro / libretro/RetroArch

Netplay is not working with SameBoy/TGBDual cores

Open
#13,188 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

SameBoy core will just fail to initialize lobby while the TGBDual just outright crashes after joining the game.
The tested game I tried was Tetris.
I don't know if its a core issue or a Retroarch issue but I am reporting here anyway.

Expected behavior

They should not crash or cause issues.

Actual behavior

Like I said they either crash RetroArch or gives out an error.

Steps to reproduce the bug
  1. Use Sameboy/TGBDual cores and use subsystem for hosting a game
  2. Player 2 joins the game
  3. if its TGBDual it crashes RetroArch and if its SameBoy it fails to initalize the lobby.
Bisect Results

No clue but will edit if I found out with which version it first started.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.9.12
Environment information
  • OS: Linux/Windows

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

The issue names RetroArch netplay with the SameBoy and TGBDual cores, using a subsystem and Tetris on RetroArch 1.9.12 across Linux and Windows, but provides no files or tests. Start by reproducing the listed hosting and joining steps and determine whether the failure is in RetroArch or a core. Done means SameBoy initializes the lobby and TGBDual no longer crashes after joining.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
networking
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.