On this page
COMMUNITY PC GUIDE

Nitro-Fueled PC port projects

Updated · Checked against GetLostIn v0.4, OCTR v0.5.4, EU fork v0.5-eu.11, Frank D3D11 v0.1, leomoon OCTR v0.5.4, CTRNativePorted (no formal release)

Use GetLostIn v0.4 for the standard Windows setup, or OCTR v0.5.4 for Linux and community online play. The EU fork offers a Linux/Steam Deck launcher that can prepare separate base and update folders. Choose a branch before following the installation guide.

Choose a project

These projects target the PS4 Nitro-Fueled game. CTR Native and Turbocharged target the original PlayStation CTR.

Your situation Project First thing to check
Your situationWindows, ordinary setup ProjectGetLostIn First thing to checkv0.4 portable ZIP and your own 1.21 files
Your situationWindows, community online ProjectRyu7w7 OCTR First thing to checkv0.5.4 ZIP, nickname and Online tab
Your situationLinux/Steam Deck with merged files ProjectRyu7w7 OCTR First thing to checkv0.5.4 AppImage and an accepted Game folder
Your situationLinux/Steam Deck with separate base/update files Projectmartijnhe EU fork First thing to checkv0.5-eu.11 AppImage; use --launcher for preparation

GetLostIn, OCTR and the EU fork all describe support for CUSA13795 or CUSA14876 with 1.21. Check the file requirements for the selected route.

Windows and Linux release paths

The packages below are from releases marked as formal releases on GitHub. OCTR and the other runtimes still contain experimental features; Code 23 remains a known problem.

Project Release / date Package Size (bytes) Checksum file
GetLostIn Windows v0.4, Oct 19, 2026 CTR-NitroFueled-PC-portable-windows.zip 140,293,286 None listed
OCTR Windows v0.5.4, Oct 19, 2026 CTR-NitroFueled-PC-portable-v0.5.4-windows.zip 119,351,657 None listed
OCTR Linux/Deck v0.5.4, Oct 19, 2026 SacredFire-v0.5.4-x86_64.AppImage 450,939,424 None listed
EU Linux/Deck v0.5-eu.11, Oct 19, 2026 CTR-NitroFueled-EU-v0.5-eu.11-SteamDeck-Linux-x86_64.AppImage 452,299,296 SHA256SUMS.txt

Swipe or use the arrow keys to see all columns.

The EU release text mentions an automatically built Windows ZIP, but that asset is absent from this release. Select a published Windows package from the other rows. Return to Windows or Linux installation after selecting a package.

Other released forks

leomoon OCTR v0.5.4 is a secondary release source. Its two packages have the same filenames, sizes and GitHub SHA-256 metadata as Ryu7w7 v0.5.4: the 119,351,657-byte Windows ZIP and 450,939,424-byte AppImage. Use the Ryu7w7 path above for this guide's OCTR steps.

FrankHUN88453 v0.1, released October 14, 2026, is a separate Windows runner using D3D11. Its package is CTR-NitroFueled-PC-0.1.zip (12,120,235 bytes), and its README targets the CUSA13795 base 1.00 executable. It uses a different setup and data layout, so use that project's own release instructions when exploring it.

Prereleases and unavailable projects

CTRNativePorted by guzuold has no formal Release. Its latest build, v0.3.2, is a prerelease with experimental reconstruction and online work. Keep the formal installation paths above for a first setup; use the project's Releases page to follow testing builds.

OCTR's release history also contains v0.5.1 marked as a prerelease. Select current formal v0.5.4 rather than following an old tutorial that stops at that test build.

SacredFire by T3CHNOLOG1C is the original Linux project named by the forks. Its original repository is currently unavailable. Use the available fork releases.

Community online and updates

OCTR connects to the community RyuNET service. On Windows, set your nickname in the Online tab. On Linux, use Settings → Online (RyuNET) and follow the Linux nickname setup. Keep ryunet_online.key private; it preserves control of that nickname. Windows updates can retain user/, bbport.ini, launcher.ini and that key. Linux data stays in ~/.local/share/sacredfire.

In OCTR v0.5.4, corrected 21:9/32:9 layouts run offline; with online enabled the runtime starts at 16:9. Turn online off in the Windows Online tab or Linux Settings → Online (RyuNET) when choosing that ultrawide path. The EU fork has its own feature changes, so check its release notes before transferring settings between forks.

For GPU hangs, copy the current session log before starting again and use Code 23 checks. The current release does not resolve every cause.

Sources

Back to top