TASEmulators / TASEmulators/BizHawk

Gambatte crash/instability with FF Adventure

Open
#4,841 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

When playing back this Final Fantasy Adventure movie (WARNING: loud), BizHawk becomes incredibly crash-prone.

Specifically, BizHawk will spontaneously freeze, then close.

There doesn't seem to be any consistent way to reproduce, but it's decently easy to trigger a crash by advancing forward a few hundred frames, turning on auto-restore and tweaking inputs (for example, adding and removing Right presses). It can take anywhere from a few seconds to a few minutes. Technically, if you get lucky, you can reproduce just by unpausing: example video.

A few other notes:

  • The above movie is a small savestate-anchored segment of a longer .tasproj to make reproducibility easier.
  • There's an in-game sound bug that happens in this movie (Gambatte bug?) -- it's decently possible it's related.
  • This isn't TAStudio-specific; it can be reproduced without it (though savestates possibly have some role).
Host env.
  • BizHawk 2.11.1; Win11

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 running the attached FF Adventure movie in BizHawk 2.11.1 on Windows 11, advancing frames with auto-restore and changing inputs as described. Compare reproduction with and without TAStudio, and investigate the Gambatte, savestate, and sound paths; done means the freeze/close is prevented or reliably explained and the movie no longer triggers the crash.

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
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.