whatisgithub

What is loopydoom?

throatymumbo/loopydoom — explained in plain English

Analysis updated 2026-05-18

37C++Audience · developerComplexity · 5/5LicenseSetup · hard

In one sentence

An unfinished, unofficial port of the classic game DOOM to the obscure 1995 Casio Loopy console, built on top of the GBADoom engine.

Mindmap

mindmap
  root((LoopyDOOM))
    What it does
      Ports DOOM engine
      Targets Casio Loopy
      Unfinished tech demo
    Tech stack
      C plus plus
      SH-1 toolchain
      Python bakers
    Use cases
      Play on real hardware
      Run in emulator
      Study retro porting
    Audience
      Developers
      Retro hardware fans
    Setup
      Cross compiler needed
      Requires WAD files
      Flashcart or BIOS dump

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run a classic DOOM port on real Casio Loopy hardware using a flashcart accessory.

USE CASE 2

Play the port inside a software emulator built specifically for this obscure console.

USE CASE 3

Study how an old game engine gets adapted to unusual, resource limited retro hardware.

What is it built with?

C++SH-1 assemblyPythonGCC cross-compiler

How does it compare?

throatymumbo/loopydoommolaorg/rosbag_timing_inspectorpower-pill/ascii-aquarium
Stars373737
LanguageC++C++C++
Setup difficultyhardhardeasy
Complexity5/54/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Needs a specialized big-endian cross-compiler, original DOOM WAD files, and either a BIOS dump or a flashcart to run.

Licensed under GPL v2 or later, meaning any modified version you distribute must also be open source under the same license.

So what is it?

LoopyDOOM is a port of the classic video game DOOM to the Casio Loopy, an obscure 1995 Japanese console with limited hardware, about 512 kilobytes of memory and a built in thermal sticker printer. The author describes it as unpolished and closer to a tech demo than a finished product. It is a real port of id Software's original DOOM engine, passed down through two earlier community projects called PrBoom and GBADoom, with new code added to handle the Loopy's specific video chip, timers, controller, and sound hardware. Right now the game includes the first six levels of the shareware episode, using as much content as fits in the console's 4 megabyte cartridge limit. Video runs as a double buffered bitmap, music plays through the console's built in synth chip across all six included levels, and sound effects require an added companion circuit board with its own firmware and a small speaker chip. On real hardware the game runs slowly, somewhere around 8 to 15 frames per second, though it runs much faster inside a software emulator built for this console. There is even a feature that lets a player print the current game frame on the console's built in thermal printer. Building the project from source requires a specific big endian compiler toolchain built for this console's unusual processor, along with the original shareware DOOM data file and a data file from the earlier GBADoom project, neither of which is included in this repository for legal reasons. A Python 3 based build step then bakes those files into the game binary. Running the finished build works either in a software emulator, which needs a BIOS dump the user must supply from their own hardware, or on real hardware using a special flashcart accessory that connects to the console. Because it inherits code all the way back from the original DOOM engine, LoopyDOOM is released under the GPL version 2 or later license, with individual file copyright notices kept in place from each earlier project in its lineage.

Copy-paste prompts

Prompt 1
Help me set up the SH-1 big endian cross-compiler toolchain needed to build LoopyDOOM.
Prompt 2
Explain how LoopyDOOM's build process bakes the DOOM WAD file and music into the final ROM.
Prompt 3
Walk me through the differences between running LoopyDOOM in LoopyMSE versus on real Floopy Drive hardware.
Prompt 4
Explain the sound effect pipeline in LoopyDOOM that uses a companion RP2040 chip.

Frequently asked questions

What is loopydoom?

An unfinished, unofficial port of the classic game DOOM to the obscure 1995 Casio Loopy console, built on top of the GBADoom engine.

What language is loopydoom written in?

Mainly C++. The stack also includes C++, SH-1 assembly, Python.

What license does loopydoom use?

Licensed under GPL v2 or later, meaning any modified version you distribute must also be open source under the same license.

How hard is loopydoom to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is loopydoom for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.