# nfs4-recomp brings PlayStation's Need for Speed: High Stakes to Windows and Linux

> A static recomp of the 1999 PS1 racer, built from your own US disc image. v0.1.2 is out, but its release notes are empty.

- Published: 2026-10-22T06:35:11Z
- Score: 9/10
- Tags: recomp, ps1, pc
- Port / platforms: PS1 -> PC (Windows), Linux / Steam Deck (Recompilation)
- Web page: https://emu-radar.customfw.xyz/news/nfs4-recomp-need-for-speed-high-stakes-pc/
- Sources: https://github.com/mayhemdotcpp/nfs4-recomp

The nfs4-recomp project turns the 1999 PlayStation racer Need for Speed: High Stakes into a native program for Windows and Linux. The repo marks v0.1.0 as latest, but a v0.1.2 release dated 21 October is also listed, with no notes. Which build is current is unclear from the page.

This is a static recompilation. The game's MIPS code, the instruction set the PlayStation's CPU runs, gets translated into C# ahead of time. The project forks RecompOne, which supplies the PlayStation hardware layer plus the window, sound and input. The result runs as a regular Windows or Linux program. The repo contains no game data, so you bring your own disc.

The port adds a few things to the original. It widens the game's own camera to 16:9, so the picture isn't stretched. PGXP is on by default for steadier polygons and textures. There are two unlock mods (all cars, all tracks), a P2P multiplayer mod, and texture replacement packs.

What you need: a US disc image (SLUS-00826) as .cue and .bin, the .NET 10 SDK, Python 3, git, and on Linux PowerShell 7 (pwsh), because the build script is PowerShell. The build expects a .bin with SHA-1 hash 72E5FC9254903797A08D56BABBEF689E30514FB8.

How to try it:

1. Clone with submodules: `git clone --recurse-submodules <repo url>`
2. Check your image: `Get-FileHash -Algorithm SHA1 disc\*.bin` on Windows, or `sha1sum disc/*.bin` on Linux.
3. Put the .cue and .bin in the `disc\` folder. File names don't matter.
4. Build with `.\build.ps1` on Windows, or `pwsh ./build.ps1 -Runtime linux-x64` on Linux. The output lands in `build\win-x64\` or `build/linux-x64/`.
5. Start `nfs4.exe` (or `nfs4` on Linux) from the build folder. F1 shows the menu bar, F11 toggles fullscreen.

On Windows, `csc.cmd` points at a specific .NET SDK path. If your `dotnet --version` differs, edit the version in that path. To keep the original 4:3 picture, set `NFS4_WIDE=0`. Settings and memory cards are saved in the folder you launch from.
