libretro / libretro/blastem

Some bugs found in current BlastEm core build, Retroarch, Sept 9th 2026

Open
#69 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
77
Forks
38
Avg merge
36m
Merged PRs (30d)
6

Description

Image

Hey, hi there Retroarch developers.

Some small bug reports that found around in quick tests.

  1. This "garbage pixels" area or CRAM dots area was completely removed. I remember an older BlastEm core build in Retroarch that had it no problem, the same as Standalone. In picture can be seen. All borders cropping was set to 0, yet still cannot see the garbage pixels.

  2. An user, close to developer named Sik, made an awesome NTSC - Rainbow banding feature for BlastEm standalone. I didnt see it available here, in case could please be added.

  3. I do not know if BIOS message can be set up in current BlastEm build, just like in Genesis plus gx. It's an awesome feature as well.

  4. In blastem options, it's set: MegaDrive model (default Gen/MD 1 VA3) then I switch to Gen/MD 2 VA1, then Manage Core options -> Save game options -> then close the core.

Re-open the core and nothing happens, just get back to menu, in case it was not reported.

Thank you once again for all the awesome work, both in RetroArch & BlastEm, for so many years.

Contributor guide

No contributing guide indexed for this repository

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

The issue names the BlastEm core in RetroArch but does not identify files, tests, or entry points. Start by reproducing each of the four reports and compare the core with BlastEm standalone, especially garbage pixels, NTSC rainbow banding, BIOS messaging, and saved model options. Done is not defined because the report combines several behaviors without expected results or acceptance criteria.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.