Games
Pick a game under Games, or choose a disc and press Start.
Dev tools
Start the console to see its state here.
Disc toolkit
Look inside a 3DO disc, archives included, and play what's there: images, sounds, movies and 3D models. Save files as they are or convert them, with movies to MP4, MOV or WebM and sounds to MP3, M4A, Opus or WAV. Arrow keys move through the files, Enter opens one, and Esc comes back.
Extract the whole disc
- Drag
- Look around
- W A S D
- Fly off the road
- Q E
- Down and up
- Shift
- Fly faster
- Space
- Pause
- + −
- Speed, or scroll
- R
- Back to the road
- H
- Hide this
Bytes
Saves
Each game keeps its own 32 KB of save memory in this browser. Clearing browser data removes it, so keep a backup. A backup is a .json file with all games, or a .nvram file with one, which other 3DO emulators can read as a raw NVRAM image.
| Game | Contents | Last saved |
|---|
No saves yet. They appear here once you've started a game.
Recently removed
Setup
Controls
Change the keys and controller buttons, and turn the on-screen controller on or off.
BIOS folder
Optional. Games start without a BIOS. Choose a folder holding your own BIOS and font ROM images, and the ones found there are offered under Console, with a kanji font used automatically. They are read here and never uploaded.
First-run guide
Automatic video
Built-in boot is one boot for every region. Automatic uses PAL for European-only discs and whatever a chosen BIOS is built for otherwise. If a game then refuses the display, the console restarts in PAL and remembers it for that game.
3DOpera is a free, non-commercial 3DO emulator, built to help developers and the 3DO community. BIOS and game images are never hosted or included. No code from the projects below was copied, except the listed libraries.
3DOpera
- Author
- Hackinside
- Version
- Build
YouTube GitHub 3DO Community on Discord
This is an early beta. Expect games that misbehave, and things to change.
FreeDO and Opera
Studying libretro/opera-libretro, derived from FreeDO, informed the comparison of CPU and CEL timing, and CLIO timer, line timing, ROM overlay, SPORT, XBus, CD drive, display, CEL, math engine, DSP and NVRAM behaviour. The DSP's instruction behaviour in particular follows Opera closely. Its notice, as its terms require:
www.freedo.org. The first working 3DO multiplayer emulator.
The FreeDO licensed under modified GNU LGPL, with following notes:
* The owners and original authors of the FreeDO have full right to develop closed source derivative work.
* Any non-commercial uses of the FreeDO sources or any knowledge obtained by studying or reverse engineering of the sources, or any other material published by FreeDO have to be accompanied with full credits.
* Any commercial uses of FreeDO sources or any knowledge obtained by studying or reverse engineering of the sources, or any other material published by FreeDO is strictly forbidden without owners approval.
The above notes are taking precedence over GNU LGPL in conflicting situations.
Project authors: Alexander Troosh, Maxim Grishin, Allen Wright, John Sammons, Felix Lazarev
3DO's development tools
The Construction Set model format, older image chunk names and a check of SDX2 come from studying the development tools and samples of The 3DO Company, and the "chunkifier" file format notes by Laurent Benes and Philippe Tarboureich at Electronic Arts. Nothing from them is shipped.
M2Suite
M2Suite, by Hackinside, is a converter and visualizer for 3DO and M2 file formats. Its format research taught the disc toolkit about animation rates, difference frames, standalone films, cel shading, resource bundles, Alone in the Dark's archives and backdrops, and Gex's bigfile. That research in turn credits vgmstream, AITD-roomviewer and fitd.
Phoenix
Phoenix, by Maxim Grishin (Altmer). Static analysis of Phoenix 2.8.JAG informed the understanding of CPU, CEL and CLIO behaviour, including the default CPU cycle costs. Phoenix is the compatibility benchmark. No code was copied or translated.
3DO devkit and community notes
By trapexit and the 3DO homebrew community. 3do-devkit, portfolio_os and 3DO-information are sources for hardware and file format facts. More at 3dodev.com.
The Need for Speed
Its car and track formats follow the specifications on 3dodev.com by Versus, based on the work of Denis Auroux and OpenNFS1 by Jeff Harris. TailsLab by AndyGura and Michel Buffa's preview page gave background.
Gex and Crystal Dynamics
Compared with Soul Spiral, unLoKable by SalsaGal and DeeDyne, and gexdecomp.
Interface
Laid out following taste-skill and Vercel's web interface guidelines. 3DO artwork drawn by Hackinside.
Video formats
MultimediaWiki's pages on Interplay MVE and ReadySoft scenes, and Kostya's notes on na_game_tool, helped with those formats.
Libraries and data
lamejs (LGPL-3.0) encodes MP3 exports. The chd crate by SnowflakePowered (BSD-3-Clause) reads CHD disc images, a format from the MAME project. Box art is downloaded on request from libretro-thumbnails and kept in your games folder. None is included.
File formats
3DO's cel, stream and file system layouts come from its developer documentation and SDK headers. Cinepak and the SDX2, CBD2 and ADP4 sound formats are decoded from public descriptions, with FFmpeg's documented behaviour as a cross-check. Alone in the Dark's archives use PKZIP's implode method, as described by Mark Adler's public-domain explode. No code from these was copied.
3DO and ARM documentation
The 3DO developer documentation, the ARM60 datasheet and ARM's Software Development Toolkit manuals are sources for hardware facts. 3DO, Panasonic and other names belong to their owners, and this project has no connection with them.