OpenPhantom is a PC fix and modding project for Star Wars Episode I: The Phantom Menace (1999). It gets the original PC game running on Windows 10 and Windows 11, and on Linux and Steam Deck through Proton, with a modern installer that works from your original CD, widescreen and ultrawide resolutions, uncapped FPS, a corrected field of view, mouse look, and working music and video. Alongside the fixes, OpenPhantom is building a new open source engine for the game, with tools for modding, editing and extending it.

Download the latest release · Installation guide · Multiplayer guide · Discord · Website

The project has two parts. The legacy patches are useful today: they modify the retail executable in memory so the game you already own runs with modern fixes. The new engine is the long-term work: a modern engine of our own that plays the game from your own copy, built for deeper modding and new features.

Ultrawide support with OpenPhantom.

4K rendering with expanded draw distance.

Free camera, no clip and photo mode.

Multiplayer Mode

Want to play? Download the latest release and run the OpenPhantom installer. It installs the original game from your own disc and applies the available patches and fixes for modern Windows PCs. You don't need to build anything from source.

The patch and the installer have two separate version numbers. They always did, apart from one release.

The installer's first number is always one higher than the patch's, and the other two are the same. The DLLs carry the patch number, so a DLL's properties and the first line of engine_fixes.log say 1.0.1 while the installer that delivered them says 2.0.1. Before 1.0.0, which brought the multiplayer, the patch ran from v0.2.0 to v0.4.3 and the installer from i1.0 to i1.4.3.

One release merged the two into a single number, published as v1.5.0 and i1.5.0. That's been undone. On GitHub that release is now v0.4.1 and i1.4.1, and the one after it is v0.4.2 and i1.4.2.

Only the release name changed; nothing was rebuilt. The installer in that release still reports 1.5.0 in its properties and in Add and Remove Programs, because it's the same file. If you have it installed, that's why the number doesn't match the release name.

The installer doesn't compare version numbers. It finds an existing installation by its application id and asks what you want to do with it.

Full guides for installation, usage and configuration are in the wiki:

• Installation Guide
• Multiplayer Guide
• Currently working on, with spoilers
• Known Issues
• Reporting Issues with the OpenPhantom Patches

• Build a new, open source engine of our own that plays The Phantom Menace from your own copy of the game. It ships no game data.
• Keep the original gameplay. If the 1999 look or feel was intended, it stays.
• Run natively on Windows and Linux, with the Steam Deck as a first-class target: 64-bit, Direct3D 11, Direct3D 12 and Vulkan, and every kind of controller.
• Use modern hardware properly, several cores included, so large levels and long draw distances run smoothly.
• Build an editor for maps, models, dialogue and the game's content, from a single pickup to a whole level.
• Support community modding, and stay open to contributions.
• Keep the legacy patches working for the game as it is today, until the new engine replaces them.

This is a community project. Code, documentation, tests, tooling, research notes and good bug reports are all welcome, and you don't need to know the engine to start.

CONTRIBUTING.md has how we work: how to report something usefully, what a pull request needs, and the ground rules for working against a binary you do not have the source to. Each component adds its own rules on top: legacy/CONTRIBUTING.md for the engine fixes and installer/CONTRIBUTING.md for the installer.

The most useful thing right now is testing. Every fix has been played in a full installation, and each one's README says what was checked. But a couple of machines isn't everywhere, so a report of what happened on yours, with engine_fixes.log attached, helps a lot. The log names the build each fix came from, which is usually the first thing we need to know.

The Phantom Discord is where the community talks: players, modders and developers sharing videos, mods and ideas. As OpenPhantom grows it is also where development updates, custom content and tools land.

https://discord.gg/73UbZN2y7x

OpenPhantom ships no game data. No assets, no executables, no extracted files, nothing proprietary, in the repository or in a release. Everything here operates on files you already own, and you need a legally obtained copy of Star Wars Episode I: The Phantom Menace for PC to use any of it.

An independent fan project. Not affiliated with, endorsed by or sponsored by LucasArts, Lucasfilm Ltd or Disney. All trademarks, game titles and related intellectual property belong to their respective owners. OpenPhantom claims no ownership of any original game content and redistributes none of it.

MIT. The source here is free to use, modify and distribute under those terms, provided the licence notice travels with it. See LICENSE.

The licence covers this source code only. It grants nothing regarding the original game, its assets, or anything else its rights holders own, and it does not cover the third-party code the project carries: the HACL* sources in legacy/src/third_party/hacl/, which are MIT, with KaRaMeL headers under Apache 2.0 and MIT; Mbed TLS, which the build downloads and links into multiplayer.dll under Apache 2.0; and the third-party binaries the installer carries in installer/dist/, which are each under their own terms and include GPL and proprietary components. legacy/dist/THIRD-PARTY-NOTICES.txt names what the patch carries, and installer/THIRD-PARTY-NOTICES.md names the rest and records what a release has to ship alongside the installer to satisfy them.

General enquiries and feedback: [email protected]

For anything technical, open an issue here; more people will see it and it stays searchable.