C64 READY.

Docs / Known Issues

Known Issues

The honest list of what's still rough, approximate, or out of scope in C64 READY. Nearly everything else runs faithfully; this page covers the exceptions worth knowing about. For what does work, see the Features overview.


Open demo bugs

Demos & games in general

Most demos and games run faithfully, but:

Found something broken? Please note the demo and where it breaks — bug reports help push the emulation closer to real hardware.

Hardware not emulated

Unmodelled hardware quirks

Deliberate simplifications inside otherwise-emulated chips. These are model-specific glitches or corner cases with negligible impact on practical software:

Unsupported file formats

The supported set is .prg, .d64, .crt, and .tap (see the Features overview). Two adjacent formats are out of scope:

D64 disk images

The .d64 parser (src/d64.js) covers the standard directory, file types (including DEL/scratched entries), BAM free-block totals, and the 35-/40-track and error-info image-size variants. A few format details are recognised but not fully handled:

  1. 40-track free-block count — the "blocks free" tally sums only tracks 1–35; tracks 36–40 live in a DOS-variant-specific BAM extension (DolphinDOS $AC / SpeedDOS $C0 / PrologicDOS $90), so counting them reliably needs variant detection. Undercounts on 40-track disks only.
  2. REL files — the side-sector track/sector (+$15/$16) and record length (+$17) aren't parsed.
  3. GEOS files — the GEOS info bytes (+$18–$1D) aren't parsed.
  4. Error-info bytes — their presence is detected, but the per-sector error codes (21/23/27…) aren't surfaced or emulated as read errors.

Audio

Performance


Bug reports are welcome on GitHub. See also the Getting Started guide and the Features overview.