Repository navigation
Development build e5fbb9cc
Pre-release
Built from e5fbb9cc - fix(greenzone): a restore through a background anchor is the machine again - miniBox 109bcaa, and the check that sees it (ToolAssisted-run#190)
| what | file |
|---|---|
| Windows x64 | chimera-win-x64-e5fbb9cc.zip |
| Linux x64 | chimera-linux-x64-e5fbb9cc.tar.gz |
Both carry the frontend and its natives. They carry no cores, and
Chimera downloads none: get a core's .chimeraCore package from the
project that builds it and put it in the Cores folder beside Chimera.
BUILD.txt names the exact commit this was built from and
LICENSES.md states its terms.
Each core brings its own licence with it, and some (Genesis Plus GX,
Opera, Snes9x) forbid commercial use - which binds whatever they are
installed into. Chimera shows a core's terms once it is in the folder.
Windows will warn that the executable is unsigned and from an unknown
publisher; it is not signed, and there is no way around that warning
short of buying a certificate.
Not for submissions. A development build is replaced on every
change, so it may stop being downloadable - which means a movie made
on it can stop being replayable. Do not use a dev build to
produce a TAS for submission to toolAssisted.run; use a
nightly,
which is dated and kept forever.