TASEmulators / TASEmulators/BizHawk
I can't record past specific frame after it was in read and write mode
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
I was playing Kirby Mass Attack at that time when it happened. The movie stopped unexpectedly at 62,898, but I can't load the game as far as 69,000 frames when the movie was restarted. When I load the game using the same movie, I made the movie read and write and load the save state, but it doesn't record the game.
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 issue in BizHawk with the Kirby Mass Attack movie, focusing on the transition to read-and-write mode and loading the save state around frames 62,898 and 69,000. Compare recording behavior before and after the movie restart; done means the game records correctly after loading the save state in read-and-write mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100