TASEmulators / TASEmulators/BizHawk

BattleTanx.rom not able to run on BizHawk

Open
#1,105 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

update 2022-02: emulated correctly by Ares64 core, which unfortunately is too slow for casual play

Hello, I'm having a little problem with the BizHawk emulator. Overall, it's a very amazing emulator, but I do have one problem with it. And that problem is that I cannot open up my BattleTanx emulator on BizHawk. It has the .rom ending, while the other N64 game I do have uses the .z64 ending. Is it simply a faulty file or is .rom not supported by BizHawk?

EDIT: Alright, I figured that I was a dumb and downloaded a BattleTanx rom that ended with the .n64 file. However, I'm still just stuck at a black screen, with nothing to load into. Even with BattleZone and Goldeneye, which both are .n64 files, they may be laggy, but they can load in quite easily.

edit: Don't link ROMs

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 the BattleTanx loading failure in BizHawk with the reported .rom and .n64 files, then inspect the N64 ROM-loading path and the Ares64 core noted in the issue. Done means identifying whether the failure is caused by file support or emulation and documenting or fixing the behavior so BattleTanx loads correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.