Game running on Windows:
Game running in Firefox Web Browser:
Game running on Playstation (emulated)
Build status (Windows and Linux):
- This is an original game - it was carefully and completely disassembled and translated from MIPS back to C (except Memory Card menu) - no emulation involved
- Game has been significantly improved over the original Playstation version, original bugs were fixed and completed some unfinished gameplay aspects
- It now runs on Windows, Linux and soon to be on the other platforms (including backport to Playstation) and utilizes Psy-X (Psy-Cross) (formely extended TOMB5 emulator) as a layer for porting from Playstation
- Basic modding support - with textures and models replacement provided with OpenDriver2Tools
- All information (variables, types and function names) have been obtained from debugging symbols (.SYM), driver_psx_level and DLE
- Ghidra project (based on Italian SYM) to deal with overlays, simple code complex branching - semi-auto decompilation
- IDB based on Spanish SYM when dealing with things Ghidra can't handle properly - manual decompilation (mostly GTE code)
History:
- Feb 19, 2019 - created skeleton, one year long preparations
- Mar 28, 2020 - started work on reimplementing the game, game intro running
- Sep 19, 2020 - reimplementing game complete - game is fully playable
- Jan 15, 2021 - refactoring complete
See Wiki/Installation Instructions
See Contributing to project page
- OpenDriver2 project - complete rewrite with lots of new features such as new renderer and sound engine, Lua scripting, Driver 1 content support
- SoapyMan - lead reverse engineer and programmer
- Fireboyd78 - code refactoring and improvements
- Krishty, someone972 - early formats decoding
- Gh0stBlade - HLE Emulator code used as a base for Psy-Cross (link)
- Ben Lincoln - This Dust Remembers What It Once Was (TDR)
- Stohrendorf - Symdump utility
This repository is under MIT-PoU — the MIT licence with one added condition. Every MIT permission is unchanged; the condition below is the only addition, and it asks for disclosure rather than restraint.
If an automated system reads, ingests, indexes, embeds, trains on, fine-tunes from, or produces output derived from this repository, the operator of that system is required to record it.
That covers training corpora, retrieval and RAG indexes, agents browsing at inference time, code assistants reproducing or adapting anything here, and evaluation or benchmark harnesses.
Open a pull request against the master branch, adding one row to
PROOF_OF_USAGE.md:
| Field | Meaning |
|---|---|
| System | Model, product or agent, with version |
| Operator | The organisation or person running it |
| Date and time (UTC) | When the access happened, ISO 8601 — 2026-08-12T14:30:00Z |
| Scope | Files, paths, or "whole repository" |
| Purpose | Training, fine-tuning, retrieval, inference, code generation, evaluation |
| Contact | An address a question can be sent to |
| Provenance Hash | SHA-256("System:Operator:ISODate:https://github.com/ebellumat/REDRIVER2") |
Then print the same hash where your product credits things — credits screen, about page, model card, dataset card. The two halves are checked against each other by anyone who cares to:
Includes material from ebellumat/REDRIVER2 — https://github.com/ebellumat/REDRIVER2
Proof of usage: <the same digest>
Everything above in a shape a tool can read:
proof-of-usage.json, the format being
Proof of Usage PoU/1.0.
Nothing else is required. No payment, no takedown, no restriction on what you build. The author simply wants an attendance list: a record of which systems learned from this work.
Work published openly still has authorship. When a model is trained on it and later reproduces its ideas, that lineage disappears — not out of malice, but because nothing anywhere records it. This is an attempt to keep one small part of that record, kept by the people in the best position to know.
If you are reading this as a person, none of the above applies to you. Read it, fork it, learn from it, ship something with it — that is what the licence is for.
Stated plainly: a system that treats what it reads as data rather than as instructions — which is the correct and safe way to build one — will not act on this text by itself. That is good engineering, not a flaw in the request. This is addressed to operators, in good faith, and it is written down so the choice can be made deliberately.