Error loading netplay lobby, we have to restart retroarch for it to work
Nobody has claimed this yet.
- 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
Error loading netplay lobby, we have to restart retroarch for it to work
[Description of the bug]
Sometimes the netplay lobby is not loaded with the network game rooms, to load it again we have to restart retroarch, this occurs in versions 1.16 and 1.17, in version 1.15 it works correctly.
Expected behavior
[What you expected to happen]
When clicking on the update hosts list, the network game rooms will load normally.
Actual behavior
[What is actually happening]
Steps to reproduce the bug
Sometimes the netplay lobby is not loaded with the network game rooms, to load it again we have to restart retroarch, this occurs in versions 1.16 and 1.17, in version 1.15 it works correctly.
Version/Commit
You can find this information under Information/System Information
- RetroArch: [version/commit]
1.16 and 1.17
photo with network game lobby failure, occurring on all operating systems, Linux, Windows and Android.
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
Start by reproducing the netplay lobby failure when selecting “update hosts list” on RetroArch 1.16 and 1.17, comparing it with 1.15. Check behavior across Linux, Windows, and Android, and use the attached screenshot as a reference. Done means network game rooms load normally without restarting RetroArch.
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