TASEmulators / TASEmulators/BizHawk

Rushing Beat Shura (J) has graphical issues in new BSNES

Open
#3,699 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Core: BSNES Inaccuracy Repro: Affects 2.9.1 Waiting on user/contributor response
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

image

Hi for some reason, there is a lots of glitches and bugs on this scenario, this doesn't cause any fatal error or anything else, nor any slowdown, so after succeeding this stage, the game running normally...

So i made a Save State precisely on this stage, let me know if you needs some files to analyze the issue.
I'm using the latest official Bizhawk so currently the 2.9.1 version

I don't know what to give you as i don't have any error recorded so in worst case i'm gonna screenshot my settings

image
image
image
image

Using the very old ZSNES emulator, this stage is not bugged but i don't have proof on that because the mate with whom i was playing this game told me so.

Thanks

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

No source files or tests are named. Start by reproducing the graphical glitches in BizHawk 2.9.1 on the Rushing Beat Shura (J) stage, using the mentioned save state and the reported settings; done means identifying a reproducible cause and confirming the stage renders correctly without affecting later gameplay.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.