TASEmulators / TASEmulators/BizHawk

[N64] Ocarina of Time Glitched Subscreen / Inventory

Open
#1,372 24 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Core: Mupen64Plus Repro: Affects 2.3/2.3.1/2.3.2
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

What we know:

  • This bug affects unmodded roms and not romhacks simply because they have different SHA1 checksums. There's nothing special about the roms' contents.
  • Normally, game-specific emulation hacks are enabled by flags in the gamedb, but there are some baked into the copy of Mupen64Plus' core distributed with BizHawk.
  • We can't recompile the core right now.
  • @steventylerseanherr has (unwittingly?) provided a workaround: change the rom slightly with a hex editor.

Original bug report follows.


The inventory screen is glitched for OOT such that when using GlideN64, the inventory screen is always white and when using Glide64mk2 it looks very broken. I suspect it has something to do with some sort of hard-coded Subscreen Delay Fix conflicting with the graphics plugins' framebuffer emulation since the inventory works fine in OOT Randomizer which isn't recognized as OOT and thus the delay fix isn't applied to it.

GlideN64 OOT
oot gliden64

Glide64mk2 OOT
oot glidemk2

GlideN64 OOT Randomizer
oot rando gliden64

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 unmodded Ocarina of Time inventory-screen failure with GlideN64 and Glide64mk2, then inspect the Mupen64Plus core, gamedb flags, and built-in Subscreen Delay Fix described in the report. The workaround and OOT Randomizer comparison provide reference cases; done means the inventory renders correctly without changing the ROM.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
computer-graphics, game-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.