CTRPCNITRO-FUELED PC GUIDE
On this page
UNOFFICIAL PC SETUP

CTR PC: Nitro-Fueled download and installation

Updated · Checked against GetLostIn v0.4, OCTR v0.5.4, EU fork v0.5-eu.11

Crash Team Racing Nitro-Fueled can run on PC through community runtimes for the PS4 game. These are unofficial projects: the game's x86-64 code runs on your CPU while a compatibility layer handles PS4 services and translates graphics to Vulkan. This guide covers the 2019 Nitro-Fueled game.

Bring your own decrypted base game and matching 1.21 update. Start with GetLostIn v0.4 on Windows; use OCTR v0.5.4 on Linux or for community online play. The projects are still experimental, so keep a copy of your saves before changing builds.

Download from GitHubInstall on WindowsInstall on Linux

Download from GitHub

Choose a named release and the package for your operating system. The archives below contain the runtime; your existing game data stays separate.

Use Release File to choose
UseWindows, standard setup ReleaseGetLostIn v0.4 File to chooseCTR-NitroFueled-PC-portable-windows.zip
UseWindows, community online ReleaseOCTR v0.5.4 File to chooseCTR-NitroFueled-PC-portable-v0.5.4-windows.zip
UseLinux or Steam Deck ReleaseOCTR v0.5.4 File to chooseSacredFire-v0.5.4-x86_64.AppImage
UseLinux or Steam Deck, EU fork ReleaseEU v0.5-eu.11 File to chooseCTR-NitroFueled-EU-v0.5-eu.11-SteamDeck-Linux-x86_64.AppImage

The EU release currently has a Linux package. Use one of the Windows rows for Windows. Compare the projects before changing branches.

Check your PC and game files

Check these requirements before opening the runtime. For region and directory details, use the game-file checklist.

Item Requirement for the GetLostIn/OCTR route
ItemWindows Requirement for the GetLostIn/OCTR routeWindows 10 version 1903 or later, or Windows 11; 64-bit
ItemLinux Requirement for the GetLostIn/OCTR routex86-64; Steam Deck is an upstream-supported target
ItemProcessor Requirement for the GetLostIn/OCTR routeSSE4.2, POPCNT and AVX instructions; the startup check reports missing instructions
ItemGraphics Requirement for the GetLostIn/OCTR routeVulkan 1.3, geometry shaders and current drivers
ItemGame Requirement for the GetLostIn/OCTR routeYour own decrypted CUSA13795 or CUSA14876 base game plus the same region's 1.21 update

GetLostIn v0.4 and OCTR v0.5.4 add Windows handling for missing MOVBE, BMI1 and LZCNT instructions. If the startup check rejects your CPU, keep its exact message for the startup checks.

Install on Windows

These steps use the portable packages, which include Python.

  1. Extract the selected ZIP into its own folder.
  2. Open CTR-NitroFueled-PC.exe for GetLostIn v0.4, or Crash™ Team Racing Nitro-Fueled.exe for OCTR v0.5.4.
  3. Choose your base-game directory.
  4. Choose the matching 1.21 update directory.
  5. Press Prepare the game.
  6. Wait for the launcher to accept the prepared directory.
  7. Press Play.

A green file check and an enabled Play control mean the launcher accepted the selected files. If preparation stops, read its error and follow file-check failures. The launcher can also read the parent folder of an existing Image0 and Sc0 layout.

For OCTR, set your own nickname in the Online tab. To start offline, turn online off there. Keep ryunet_online.key private.

Install on Linux

For OCTR v0.5.4, use an already-merged 1.21 game directory. If your base and update are separate, follow Prepare base and update first.

  1. Put SacredFire-v0.5.4-x86_64.AppImage in a folder where it will stay.
  2. Allow the AppImage to run as a program in your file manager's properties.
  3. Open the AppImage.
  4. Select the merged game folder in the launcher's Game row.
  5. Wait for the game check to enable Play.
  6. Open Settings → Online (RyuNET). For online play, enable Play online, choose a nickname of 3–16 letters, digits, _ or -, and check its server status. Use your own name rather than RyuPC or Player. For offline play, turn Play online off.
  7. Return to Play and start the game.

OCTR stores data and saves in ~/.local/share/sacredfire and launcher settings in ~/.config/sacredfire-launcher. On Steam Deck, close Steam before using Settings → Steam → Add to Steam, then return to game mode to use the shortcut.

The EU v0.5-eu.11 AppImage can prepare separate base and update folders in its launcher. Open it with --launcher, choose the two folders, and let preparation finish. Later starts can open the game directly; use --launcher again to change setup. It accepts US or EU files with the matching 1.21 update.

First launch and exit

Start at 16:9 with ordinary display settings. GetLostIn compiles shaders as it encounters them; OCTR v0.5.4 prepares shader recipes for your GPU first and caches further shaders as needed. Let that work finish before changing several graphics options at once.

  1. Reach the game's menu.
  2. Open the runtime menu with Insert or L3+R3.
  3. Choose Quit game and confirm with Press again to quit on GetLostIn v0.4.
  4. Wait for the game window to close before reopening it.

Use a normal exit so the shader cache can be saved. For a failed start, a black screen or a mid-race crash, use Troubleshooting.

Update without losing your data

Keep the package and game version you used with a working save. Before a Windows update, back up user/, bbport.ini and launcher.ini; for OCTR also keep ryunet_online.key.

  1. Close the game and launcher.
  2. Back up those files and folders.
  3. Extract the new package over the existing runtime folder.
  4. Open the matching launcher and check the selected game path.

GetLostIn keeps existing settings when it supplies a new bbport.default.ini. If you move OCTR into a new folder instead, copy the saved folders and files across. For Linux, retain the data and configuration directories listed above and replace the AppImage at its existing path.

NEXT STEPS

After installation

Game Version

Check your existing edition and required data directory.

Read guide

PC Port Projects

Choose a current project before changing your setup.

Read guide

Controls

Find an input and understand each launcher setting.

Read guide

Troubleshooting

Match a symptom and follow its first useful check.

Read guide

Port vs shadPS4

Compare the dedicated PC ports with the shadPS4 emulator route.

Read guide

FAQ

Is this an official PC release?

No. These are independent community runtimes for the PS4 game. Activision's Nitro-Fueled product page lists PlayStation 4, Xbox One and Nintendo Switch.

Is this the same as CTR Native or Turbocharged?

CTR Native and Turbocharged target the original PlayStation game. Use Nitro-Fueled packages and PS4 file requirements for this guide.

Can I use a keyboard or a controller?

Yes. GetLostIn v0.4 has a Controls tab for keyboard bindings and SDL gamepads. Use the default input tables to identify each PS4 button.

Does it work on Steam Deck?

OCTR and the EU fork publish Linux AppImages for Steam Deck. Follow the Linux setup with your own prepared game files.

Can I use a Mac?

No. The GetLostIn/OCTR Vulkan route targets Windows and Linux x86-64; macOS/MoltenVK lacks the required geometry-shader support. Choose a Windows or Linux x86-64 machine for this route.

Which project should I use for online play?

OCTR provides community RyuNET online play. Its server and nickname are separate from the console service; see PC Port Projects.

Sources

Back to top