MiniCDi brings Philips CD-i emulation to Windows, GameCube, Wii U and 3DS
A new experimental emulator called miniCDi runs Philips CD-i games and homebrew across Windows, macOS and several Nintendo consoles, though key chips remain unfinished.
AI-drafted from 1 source. This story was written with AI from the outside reporting listed under Sources, and checked by automated tools before it went up. The originals have the full detail.
An experimental emulator for the Philips CD-i has turned up on GBAtemp, and it runs on rather more than a modern PC. MiniCDi, written by a developer going by CatmanFan, targets Windows, macOS, GameCube, Wii, Wii U and 3DS, according to the GBAtemp thread. That is an unusually wide spread of hardware for a system most people only remember for its terrible Zelda games.
The CD-i, launched by Philips in the early 1990s, was pitched as an interactive multimedia platform rather than a games console, which is part of why it has been so awkward to preserve. Its architecture is built around the SCC68070, a Philips processor derived from the Motorola 68000 family, paired with custom video and audio silicon that varies by board revision, so an emulator that works for one CD-i player will not automatically work for another.
Why the CD-i's hardware is a nightmare to emulate
According to the thread, miniCDi's authors have fully implemented the Mono-I board, the configuration used in machines like the CDI 200 and CDI 220/20, including its SCC68070 processor, the MCD212 video chip, the CDIC disc controller and the SLAVE input controller. That is enough, the developer says, to run both commercial CD-i game discs and homebrew. The later Mono-II and Mono-IV boards are only partially supported: the player's shell menu works, but disc emulation does not, because their audio and video decoding chips, the DRVDSP and CIAP, are still stubbed out rather than properly emulated.
One detail worth flagging for anyone who remembers the format: miniCDi also emulates the fluorescent tube display, the small text panel on the front of a real CD-i player that showed track numbers and status messages. It is a fiddly, cosmetic touch, but the kind of thing that separates a serious preservation project from a quick hack.
The pointer problem
CD-i software was designed around a tablet-style pointing device, one that reports an absolute position on screen rather than relative movement like a mouse or joystick. Modern controllers, whether a GameCube pad, a Wiimote or a 3DS's circle pad, do not work that way, and the GBAtemp post is candid about the result: controller support is “experimental”, works fine for moving through the player shell menus, but translates to “wanky controls” once you are actually inside a CD-i game. Nobody has solved this properly yet, and the thread does not pretend otherwise.
What still doesn't work
Audio is only partially there. MiniCDi can read audio sectors straight off a disc without trouble, but software-driven sound playback through the CPU is not fully accurate. There are also known softlocks in specific titles, including the infamous Link: The Faces of Evil stablemate Zelda: Wand of Gamelon and a homebrew demo called CDi_BadApple, both of which can hang because of how the SLAVE chip constantly polls the D-pad. The developer notes builds may not run at full speed everywhere, and macOS support is credited to a separate contributor rather than the main author.
None of this makes miniCDi a finished emulator, and nobody involved claims it is. But for a platform this obscure, with this little existing tooling, getting Mono-I hardware running convincingly across six platforms, control quirks and all, is a genuine step for CD-i preservation. The project is open source on GitHub, so the gaps in Mono-II support, audio accuracy and controller mapping are, at least in principle, open for anyone to help close.
Sources
- miniCDi - Philips CD-i emulator (GBAtemp.net - The Independent Video Game Community)
Image: Illustration: AI-generated for Gaming World