OpenTIE Compatibility Checker — Can Your PC Run It?

There is almost no arithmetic here. The checker is a rule engine over the upstream support matrix, and every rule is traceable to a line in the OpenTIE README or to the published v0.0.6 release assets. It runs entirely in your browser and makes no network calls, so nothing you enter leaves the page.

Step 1 — the platform matrix

The README publishes three supported targets, and the graphics backend is decided by the target rather than by your GPU model:

Anything outside those 4 rows — 32-bit, Windows on ARM, Linux on arm64 — is a hard stop, and building from source does not rescue it.

Step 2 — the OS floors

macOS below 13 is out. On Linux the floor is a glibc version rather than a distribution name, so the checker resolves the distribution you pick to the glibc it ships — Ubuntu 22.04 to 2.35, Debian 12 to 2.36, RHEL 9 to 2.34 — and compares major and minor numbers separately. That last row is the one that catches people: RHEL 9 misses the floor by a single minor version. If your distribution is not listed, type the number that ldd --version prints and the same comparison runs against it.

Step 3 — is there a package for you?

This is the step worth reading twice. The checker derives the filename your platform would have from the upstream naming convention opentie-<version>-<os>-<arch>-release.<ext>, then compares that prediction against the assets v0.0.6 actually publishes. Two independent paths to one answer. They agree on three platforms and disagree on exactly one: macOS x86-64 is in the support matrix and the convention predicts a file for it, but no such asset exists. An Intel Mac owner is therefore supported and still has to build from source — which is the single most useful thing this page can tell anyone, and the reason the release asset list is cited separately from the README.

Steps 4 to 7 — content, features and audio

OpenTIE ships no game data, so owning neither edition downgrades the verdict no matter how good the hardware is. Which edition you own then gates features: TIE95 carries the 1995 presentation and the adaptive iMUSE soundtrack, TIE98 carries the 1998 flight model, 3D assets and prerecorded score, and both together enable the mix upstream recommends. Audio resolves last, with fallbacks rather than errors: SC-55 emulation without ROMs falls back to built-in OPL3, FluidSynth without a SoundFont falls back to OPL3, and asking for the prerecorded score without TIE98 falls back to iMUSE.

Steps 8 and 9 — timing and the build path

The only real calculation is the flight rate: simRate = min(displayHz, 240). The ceiling is inclusive, so a 240 Hz panel is matched exactly and only a faster one is reported as capped. Finally, when a local build is the remedy — or when you tick the box because you want to build it anyway — the dependency checklist appears: 6items, taken from the README's build section.

Published 2026-09-12. Filenames and byte sizes read from the GitHub Releases API. Note the missing row — there is no macOS x86-64 package.

Download from the upstream Releases page only. This site hosts no binaries.

OpenTIE will not start without game data, and the only supported way to get it is a copy you own. STAR WARS: TIE Fighter Special Editionbundles the 1995 Collector's CD-ROM and the 1998 Windows release in one purchase, which is exactly the pair the recommended configuration needs — so one purchase covers both halves rather than two.

Both GOG and Steam accept Sri Lankan Visa and Mastercard, within whatever foreign-transaction limit your bank applies to the card. Regional pricing and your issuer's FX markup both apply, so the rupee amount on your statement lands above the listed price. It is a digital download either way, so there is no import duty and nothing to ship. The engine itself is a 4–15 MB download depending on platform; your game installation is the part that will actually use your data allowance.

If you want to read the code rather than fly it, the write-up on why OpenTIE is a good C codebase to learn from covers that side, and you can try the C you read in the browser with the online C compiler.

• OpenTIE — upstream repository and README (support matrix, editions, audio, graphics, flight timing, build dependencies)
• OpenTIE v0.0.6 release — published asset filenames and sizes
• GitHub repository metadata — GPL-3.0 licence detection
• GOG — STAR WARS: TIE Fighter Special Edition
• Steam — STAR WARS: TIE Fighter Special Edition
• Ubuntu package archive — libc6 version per release
• Debian package archive — libc6 version per release
• Red Hat — RHEL component versions (glibc per major release)
• OpenXWA — the sibling X-Wing Alliance project

Every rule on this page was cross-checked against these sources on 2026-09-23. OpenTIE ships releases frequently, so the version, the asset list and the platform matrix are re-checked whenever a new tag appears upstream.

Correction: an earlier post on this site said OpenTIE had no licence file. The repository is licensed GPL-3.0 as of 2026-09-23.