CTRPCNITRO-FUELED PC GUIDE
On this page
COMMUNITY PC GUIDE

Nitro-Fueled game versions and files

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

For GetLostIn v0.4, OCTR v0.5.4 and EU v0.5-eu.11, prepare your own decrypted base game and its matching 1.21 update. Check the title ID and the files inside each directory before asking the launcher to prepare them.

Supported game editions

Use the same title ID for the base game and update. The folder's name alone is not a version check.

Edition Title ID Recommended file set
EditionAmericas Title IDCUSA13795 Recommended file setBase 01.00 plus update 01.21
EditionEurope Title IDCUSA14876 Recommended file setBase plus update 01.21

All three releases above describe this 1.21 path. For another title ID, stop at the launcher check and compare its message with the selected project's release instructions. Choose the project and package before preparing data for a different runtime.

Check your existing directory

In the standard layout, open each selected folder and check the following items.

Item What to check
Itemeboot.bin What to checkPresent and readable as a decrypted PS4 executable
Itemsce_sys/param.sfo What to checkThe title ID and update metadata match the selected edition
Itemsce_module/ What to checkRequired game modules are present, including libc.prx, libSceFios2.prx and libSceNpToolkit2.prx
Itemarchives/ What to checkGame archive data is present and passes the launcher's checks

The alternative Image0 / Sc0 layout is also supported by the current Windows launchers: select the folder containing both. Image0 holds the executable, modules and data; Sc0 holds system metadata. A .pkg file itself is not a base-game or update directory.

Prepare base and update

Keep the original base and update folders so you can repeat preparation if a check fails.

Windows launcher or EU Linux launcher

  1. Select your base-game folder.
  2. Select the same edition's 1.21 update folder.
  3. Run the launcher's preparation action.
  4. Check that the prepared game is accepted before pressing Play.

The Windows Prepare the game operation merges with hard links on the same drive. GetLostIn v0.4 can put the prepared directory beside game files that are on a different drive from the runtime.

Merged directory for OCTR Linux

OCTR's Linux Game row takes a merged directory. You can prepare a working directory from your existing decrypted files:

  1. Make a working copy of the base-game directory.
  2. Copy the matching update's contents over that working copy, merging folders and replacing matching files, including eboot.bin and sce_sys.
  3. Choose the resulting directory in OCTR's Game row.
  4. Wait for the check to accept it.

If your file manager asks whether to combine folders, retain the base files that the update does not replace. A successful check enables Play. Return to Linux installation after preparation.

When the file check fails

Read the specific file or version named by the launcher. The update metadata and executable must belong together.

Message or symptom Next check
Message or symptomMissing update or an older executable Next checkCheck that the update replaced both the executable and system metadata in the working directory
Message or symptomparam.sfo says 1.21 but the executable is rejected Next checkRecheck which base and update folders were selected; use the current formal package
Message or symptomeboot.bin cannot be read as decrypted Next checkStop using that directory as input and check your own prepared files
Message or symptomDamaged archive or zeroed archive name table Next checkRecheck the output of your own file preparation; v0.4/v0.5.4 report this condition
Message or symptomFiles pass but the runtime closes Next checkContinue with startup and crash checks

Keep the validation message intact when reporting a problem. For GetLostIn v0.4, both documented 1.21 executable variants are accepted; an error from an older runtime is a reason to update the runtime before changing more files.

Sources

Back to top