TASEmulators / TASEmulators/BizHawk
3DO (Opera): Crash 'n Burn timing flag
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Crash ‘n Burn (3DO) does not start correctly in BizHawk’s Opera core. Instead of proceeding to the title or gameplay, the game loops its promotional video continuously. The same game runs correctly in RetroArch when a specific timing flag is enabled in its 3DO core settings.
Repro
- Launch BizHawk 2.11.
- Load the U.S. version of Crash ‘n Burn for 3DO.
- The game begins with a promotional video for Total Eclipse.
- When the video ends, it loops indefinitely and never reaches the title screen.
Expected Behavior
The game should continue from the promotional video to the title screen and allow normal gameplay to begin.
Notes
In RetroArch, this issue is resolved by enabling a special timing option in the 3DO (Opera) core — the “Crash ‘n Burn timing flag.” This flag was originally needed because the U.S. pack-in version of Crash ‘n Burn relied on unique timing behavior linked to the Total Eclipse advertisement. Without that flag, the game becomes stuck looping the ad sequence.
It appears that BizHawk’s Opera core may not currently expose or enable this timing flag, causing the game to fail to start properly.
Host env.
- BizHawk 2.11
- Windows 11
- Opera (3DO) core
- Crash ‘n Burn (U.S.) ISO
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 inspecting the Opera (3DO) core's timing configuration and how it handles the Crash 'n Burn timing flag described in the issue. Compare the behavior with RetroArch's corresponding option, then reproduce using the U.S. Crash 'n Burn ISO and confirm that the promotional video proceeds to the title screen.
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
- Mostly clear
- Newbie friendliness
- 35/100