TASEmulators / TASEmulators/BizHawk

[Virtual Jaguar] Old Upstream Issues Potentially Worth Poking At

Open
#3,404 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Core: Virtual Jaguar Inaccuracy Needs unmanaged changes (C++) Repro: Affects 2.9 dev
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

Summary

Virtual Jaguar is great, but there's still some issues left over from when it ceased development (as far as I can tell) in 2017 or so. Since it's unlikely that any upstream fixes are coming, I figured I'd repost compat issues and bugs I've verified are still present in Bizhawk (as of commit 0c6f052) since there's been cleanups and improvements under the hood. Might be worth messing with if you get bored or someone wants to do a TAS.

The List

Wolfenstein 3D: Hangs on black screen at startup with loud, ear-piercing noise. If fast blitter is enabled it'll show the "sphere" screen at startup without any audio before breaking. Virtual Jaguar homepage says "The old DSP core works, but to hear any sound it needs the new pipelined DSP core".
White Men Can't Jump: Hangs on a black screen after the BIOS sequence.
Tempest 2000: Music chugs intensely under accurate blitter, menus and titles run too fast(?) under fast blitter.
Iron Soldier: Hangs on black screen after weapon loadout screen. Does not appear to run in any emulator, so don't sweat this one too much.
Iron Soldier 2: See Iron Soldier 1.

Host env.

BizHawk dev build 0c6f052: Windows 10 Home 21H2, AMD/NVIDIA

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 listed Virtual Jaguar failures in BizHawk dev build 0c6f052 on the stated Windows environment, beginning with one game rather than the whole list. Compare accurate and fast blitter behavior where noted, and use the upstream DSP-core note as context; done means the selected game no longer hangs, breaks audio, or exhibits the reported timing issue.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.