[Critical Error] The Nightly version is failing to connect via netplay using the fbneo core and relay server;
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
[Critical Error] The Nightly version is failing to connect via netplay using the fbneo core and relay server;
The Nightly version fails to establish a netplay connection; the session drops immediately upon joining. The core tested was fbneo with the game Street Fighter II: Champion Edition.
I tried connecting the Windows version of RetroArch with another Windows instance of RetroArch;
I tried connecting the Windows version of RetroArch with a Linux instance; the connection drops immediately upon joining;
Expected behavior
Prevent the netplay session connection from dropping.
Steps to reproduce the bug
Open the game SF2CE using the FBNeo core;
Start a netplay session;
Ask another player to join the room;
The connection drops for the player trying to join;
This error does not occur in the stable version;
Version/Commit
1.22 nightly linux and windowns
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
linux and windowns
Affected Cores
fbneo_libretro
Environment information
No response
Relevant log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, bisect result, or log output is provided. First reproduce the drop with the fbneo_libretro core, SF2CE, and the 1.22 nightly on the reported Windows and Linux setups, then compare against stable while collecting logs. Done means a joining player's netplay session remains connected in the reported scenarios.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100