Reading the TFX investigation
For a guided introduction, begin with TFX Traced. This archive is the workbench: formats, extracted definitions, native-code experiments and inspection viewers, including the qualifications behind each result.
To play, choose TFX C++ for the faithful reconstruction, or TFX Redux for higher resolutions, adjustable views and arming-screen improvements.
Start with the world
The map explorer assembles terrain and scenery, plots routes and connects missions to their briefings. The model browser exposes drawing programs and animation controls. Scenery definitions show how parts, anchors and event streams combine into larger objects.
Read terrain and scenery, model programs and world versus lighting selection for the underlying rules.
Follow a mission
Campaign flow and compiled actors and waypoints separate presentation choices, authored routes and flight objectives. The weapon records and entity profiles connect those programs to flight loads and AI actors.
The game-logic overview is a map of the executable, not a current feature checklist for the later reconstruction. Historical notes may describe an unanswered question that subsequent C++ comparisons resolved. For current reconstruction coverage, use TFX C++'s verification matrix.
Images, instruments and sound
Cockpits, textures, images and presentations retain different drawing paths. In particular, static pictures on the original virtual cockpit's screens are separate from live screen-space instruments.
The font browser brings together all fourteen lettering sets, with complete byte maps, glyph sheets and modern font exports. Format notes explain their storage, custom encodings and native checks.
The Jurassic Park TFX preview collects 47 promotional pictures, including earlier virtual cockpit layouts. Its notes record the slideshow player, source dates and soundtrack comparison.
The audio catalogue groups native music by launcher selection and hardware, with timing records from the emulator renders. Full recordings stay local; the TFX Traced sound page has short hardware comparisons. Audio notes explain the timing, device identities and distinction between native event checks and physical-card recordings. CD comparison covers the two retained audio transfers.
Versions and development evidence
Versions, patch lineage and engine builds establish which executable and resources a finding applies to. The PC Plus demo contains an especially useful disagreement between its instructions and its actual menu graph.
Development notes distinguish retained diagnostics and authoring machinery from confirmed player-facing secrets. The code browser uses reference executable offsets; recovered descriptive names are not original source symbols.
What a check establishes
Some checks execute isolated original routines with supplied inputs. Others run connected native loops or compare real C++ flight sessions. Inspection viewers use modern drawing and supplied state. Read each report's boundary before treating a successful comparison as proof of a larger behaviour.
The archive keeps Markdown alongside rendered reports, viewer data and selected comparison records. Original media, installations, extracted archives, manuals, full recordings and working scripts are not hosted on this website. References to those files open their GitHub pages; private repository access is required where applicable. Links into the did-unpack submodule open its own repository.