C1 v1.2.0 brings Crash Bandicoot to PC with widescreen and debug inspectors

First public release of C1 ports PS1 Crash Bandicoot to PC with 60/120 FPS, widescreen, and in-game inspectors, requiring disc audio/stream files.

PS1 → PC (Windows), Linux / Steam Deck · Decompilation

olya_nro20 Nov 2026, 15:31· awesome-decomp

The C1 project by wurlyfox has published its first public build, v1.2.0, turning the Crash Bandicoot PS1 decompilation into a native PC port. The release reports 100% ported code and 95% functionality, with the game mostly playable and a small number of issues remaining. Building for Windows requires LLVM Clang-CL rather than MSVC, and the PS1 target build is currently non-functional.

PC builds add fullscreen and 16:9 widescreen support along with frame rate options for 60 FPS, 120 FPS, or uncapped play. The port also has optional native perspective transformation, an updated in-game GUI, camera controls, and extra camera modes. In-game inspectors cover world geometry, zones, and objects with mouse selection and dragging, plus a world geometry editor. The codebase is written to target both PS1 and PC, though only PC-specific code works at the moment.

Releases ship 32-bit binaries for Windows and Linux, and the engine relies on 32-bit pointer layouts and arithmetic, so only 32-bit (x86 / i686 / Win32) targets are supported. You supply your own .NSD and .NSF asset files from a Crash Bandicoot PS1 game disc.

  1. Download the release package for your platform, or build from source with CMake 3.20+ and a 32-bit toolchain (multilib on 64-bit Linux, or LLVM clang-cl.exe in Visual Studio).
  2. Copy .NSD and .NSF files from the /S0, /S1, /S2, and /S3 directories on your disc into the local streams/ directory.
  3. Rename those copied files from uppercase to lowercase (s00000%%.ns[f,d]), then run ./c1 on Linux (with compatible 32-bit runtime libraries) or c1.exe on Windows.

A native PC build with geometry and object inspectors lets tinkerers inspect the game directly without waiting on an emulator. Check the remaining issue list first if you want a smooth playthrough.

Sources: github.com