Crash Team Racing Nitro-Fueled on PC: separate base and update, preparation and a finished race
ItsOOGWAY · PC guides & recorded tests
Crash Team Racing Nitro-Fueled on PC: separate base and update, preparation and a finished race
How to play Crash Team Racing Nitro-Fueled on PC: a complete Windows setup walkthrough, from the portable launcher download to a finished Crash Cove race. I show base-game and update extraction, selecting both folders, preparing version 1.21, the recorded launch settings, and normal-speed gameplay with game sound.
The key checkpoint: Select the extracted base and matching 1.21 update in their separate launcher fields. Wait for Ready to play before checking the launch summary and racing.
Before you start
- Use the recorded versions and the supported inputs listed in the original notes below.
- Compare the last successful checkpoint before choosing a fix.
- Keep original files, relevant logs and a known working setup when testing changes.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Prepare the launcher, extractor and compatible files
There are three things to prepare: the Windows portable launcher, the standalone package extractor, and your game files. The project lists a Vulkan 1.3 capable graphics card with current drivers as a requirement. Also leave enough free space for the packages, the extracted files, and the prepared game folder. Do not judge the space needed by the small launcher download alone. Start with the project page linked in the resources section. Open Releases, then open the version shown here.
Under Assets, choose the portable Windows ZIP. The name starts with C T R Nitro-Fueled P C and ends with portable Windows. Choose that ready-made download rather than either of the source-code archives. You do not need to build the program from source for this method. Next, open the linked Shad P S Four Plus package extractor release. I am using extractor version one point one, and the download we want is its Windows ZIP.
This is a separate extraction tool. We are using it to unpack the game packages before adding the resulting folders to the launcher.
Walkthrough 02
Keep the packages and output folders distinct
Before we start extracting, keep the different files straight. The launcher ZIP contains the Windows program. A game package contains the game data. Extracting the launcher does not install the game, and extracting only the update will not give you the complete game either. We will prepare the base game first, then its matching update, and only then combine them through the launcher. Go to your download folder and extract the Windows launcher ZIP into its own folder.
Extract the package-extractor ZIP into another folder. If your own game dump is inside a ZIP or RAR archive, unpack that outer archive as well. If it is already a package file, you can use it directly in the next step.
Walkthrough 03
Extract the base and matching update
Open the extracted tool folder and find the application named package extractor, with the filename shown on screen. Keep its supporting files beside it. Now open the location containing your base-game package in a second Explorer window. Having both windows visible makes it easier to see exactly which file is being dropped onto which program. Drag the base-game package onto the extractor application and release it there. A console window opens and starts listing the files it is extracting.
This is progress, so let it finish. In this recording, the tool creates the base-game folder beside the original package. The folder name starts with the game identifier shown on screen. Wait until the extractor reaches its completion message. In my recording, it says The End and asks me to press Enter to exit. Only close that console after the extraction has finished. I am shortening the waiting here, but you should let the process run for as long as your own system needs.
We need a complete folder before continuing. Now repeat the same process with the matching update package. Drag the update onto the same extractor application and wait for it to finish. This produces a separate update folder. At this stage, you should have two different folders: the base game and the update. Leave them separate for now. The launcher has a preparation button that handles the next stage.
Walkthrough 04
Select both folders in the portable launcher
With both extractions complete, open the extracted portable launcher folder. There may be another folder inside it, so continue until you can see the Windows application shown here, C T R Nitro-Fueled P C. Keep the rest of the portable folder together and launch that application. If Windows asks you about an unfamiliar download, check that you are opening the file from the project release you intended to download before choosing whether to continue. On the Play tab, the first-launch screen asks for a base game and an update.
This is the step to follow carefully. Beside Base game, click Choose. Browse to the extracted base-game folder, select that folder, and confirm. You are choosing the extracted game directory, not the original package and not the folder containing the launcher. Next, click Choose beside Update one point two one. Select the separate folder created from the matching update package. Check the two entries before moving on. The first should identify the base game, while the second should identify the update.
If one is missing or rejected, go back and check that package and its extraction before trying to launch anything.
Walkthrough 05
Wait for Ready to play and review the launch summary
Once both folders are accepted, click Prepare the game, base plus one point two one. Let the launcher finish preparing them. There is also an option for an already merged game, but that is not the route I am demonstrating. Here, I am starting with separate base and update folders and letting the launcher prepare the playable result. Here is the checkpoint we were looking for: the launcher now says Ready to play, and the game information shows version one point two one.
The prepared folder is also listed underneath. That confirms that we have moved beyond simply extracting files. The launcher has recognized the prepared game, and the Play button is available. Before launching, look at the summary called It will start with. My recording shows ten eighty p internal resolution, a sixteen-by-nine output at nineteen twenty by ten eighty, A M D FSR one, frame generation off, and a sixty frames-per-second limit. These are the settings displayed for this run.
A sixty F P S limit is a target setting; it is not a measurement proving every moment runs at sixty. The launcher also provides Settings and Controls buttons, including a Controllers and keyboard shortcut below the summary. Use those if you need to check your input setup before starting. I am keeping this walkthrough focused on the configuration shown here, rather than changing several graphics features at once. We want to confirm a working first launch before experimenting further.
Walkthrough 06
Launch and test through a race result
Now press Play and give the game time to start. The project notes that the first launch compiles shaders, so it can take longer than later launches. I am shortening the startup wait in the edit. Once the game window appears, follow the on-screen start prompt. On the first run, review the license and privacy screens, then continue if you accept them. We have reached the main menu. In this recording, I start Adventure, choose the setup shown on screen, and continue with Crash.
After the loading screen, the game reaches the opening area. That is already a useful first test: we can control the kart in the world instead of stopping at a title screen. But the better check is a race. I enter Crash Cove, let the track introduction finish, and drive through all three laps. You can see the other racers, item effects, the track, and the changing race positions. I will leave this race running at its recorded speed with the game sound, so you can judge the actual result instead of a sped-up demonstration.
The race reaches the results screen, and I finish in third place. That gives us a complete example from setup through a finished event. It shows that this configuration worked for the recorded session. It does not mean every track, every graphics option, or online play has been tested, and I am not presenting this recording as a frame-rate benchmark. If your setup stops before this point, work back through the checkpoints: a fully extracted base game, a matching one point two one update, both correct folders selected, and a successful preparation result.
If preparation succeeds but launching fails, keep the exact error and the launch log for troubleshooting. Those details are much more useful than changing unrelated settings at random.
If your result differs
| Situation | Next useful check |
|---|---|
| The process stops at a different checkpoint | Record the exact message, current build and last successful stage. Compare that stage with the matching video section. |
| A setting is selected but the result differs | Repeat the same scene and change one option at a time. A menu target does not establish measured performance. |
| A newer release changes the interface | Check the linked release notes and instructions. This companion preserves the recorded route and its limitations. |
Comments
Post a Comment