libretro / libretro/RetroArch

BSV recordings from netplay don't record properly

Open
#12,683 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

In general, I have found the bsv recording feature to be pretty useful, and I have been able to use it with multiple cores, but when it comes to netplay, I haven't been able to get it working normally. I have found two problems using the files after hosting a game.

First, to play back the input that I recorded while hosting, I need to use the command -H, as if I'm still hosting a game. The input is completely messed up if I don't do that. That said, I have found that I can successfully use bsv files recorded while hosting as long as I'm not connected to anyone.

If someone connects to me while I'm hosting, it seems that the input from the second player is not picked up at all in my bsv file. I found that if both the host and client play their own bsv files while connected in netplay, it is possible to see the inputs from both players, but this isn't too useful, since there is no way to properly synchronize the two input files.

I have only really tested this particular problem with the Mesen core so far.

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 BSV recording and playback with the Mesen core in host-only and connected netplay sessions. Compare playback with and without -H, and verify whether the host recording contains both players' inputs. Done means recordings replay correctly without host-only mode and preserve synchronized inputs from both players.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
game-dev, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.