Skip to content

Classic Home v1 — front-end, with and without SNAC cores

Choose a tag to compare

@Dino-fly Dino-fly released this 02 Aug 21:50

Classic Home — a game-first front-end for MiSTer, plus the PSX-over-SNAC pad support.

A shelf of your games with cover art, save states you can see, and a menu you can
reach from inside a game. It replaces the menu core's screen only; everything MiSTer
normally does still works, and the classic menu is one choice away under
Options ▸ Advanced Settings.

Which one to download

classic-home-firmware.zip The firmware on its own. This is the one for a normal MiSTer.
classic-home-with-snac-cores.zip The same firmware plus 274 cores rebuilt with the SNAC PlayStation-pad reader. For SuperStation One owners, or anyone with a SNAC adapter.

The firmware is identical in both — the only difference is the cores. It carries the
SNAC support either way, and on a core that was not rebuilt for it the reader simply
reads as "not supported" and nothing changes, so the plain download is not a
cut-down build.

Installing

Both archives unzip to a folder called SD-CARD-ROOT whose contents mirror your
card. Copy that folder's contents onto the root of the card and confirm the merge —
the folders line up with the ones already there.

Back up the two files you are replacing first:

cp /media/fat/MiSTer /media/fat/MiSTer.prev
cp /media/fat/menu.rbf /media/fat/menu.rbf.prev      # cores archive only

Then turn it on in /media/fat/MiSTer.ini:

classicui=1

and reboot. The first boot scans your games/ folders and builds the library, which
takes a moment; after that it is cached. classicui=0 gives you the stock menu back,
and MiSTer.prev is the firmware you were running before.

classicui-guide.md in the archive is the full guide — every screen, every setting
it adds, and what to do when something does not work.

Worth knowing

One core can be hurt by save states. Holding a game still while the menu is open
means asking the core for a state, and the SNES core dies — black picture, no more
states — if asked during a demanding scene. That is a bug in the core, not here, and
it happens equally from MiSTer's own Alt-F1 hotkey. If you hit it, set
classicui_freeze=0: the game then keeps playing behind the menu, which is what
already happens on cores that have no save states at all.

Cores with neither a pause nor save states cannot be stopped, so the game plays
on behind the menu. The front-end says so across the top of the screen rather than
leaving you to notice.

Known open issue: on PSX a state saves but does not reliably load again. Under
investigation; it does not affect other cores.