Shadow of the Colossus on PC: prepare the game, restore sound and test the first colossus
ItsOOGWAY · PC guides & recorded tests
Shadow of the Colossus on PC: prepare the game, restore sound and test the first colossus
Shadow of the Colossus on PC: a complete setup walkthrough for the community PC port of the PS4 remake, including the missing-sound fix and first-colossus gameplay.
The key checkpoint: Complete extraction and the matching update before selecting the game root. If the game is silent, compare the two audio-module fields with the recorded configuration.
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
Shadow of the Colossus on PC
This is Shadow of the Colossus running on my PC right through the first Colossus fight, but my first launch had a problem. The game worked and there was no sound. I'll show you the complete setup including the update and the two missing sound files so you can follow the successful steps without repeating my folder searching mistakes. We're using the PC port of the PlayStation 4 remake. In this recording the port is version 0.60.3.
The game [music] it recognizes as the European release CUSA08809 with game version 1.01. Keep those two version numbers separate. One belongs to the PC port, the other belongs to the game files. Updating the launcher doesn't automatically update your game. Before we start, have your own game dump and its matching update ready.
Walkthrough 02
Files and requirements
We'll also need the Windows port download, a separate package extractor, and the two decrypted sound modules from your console or an existing shared PS4 setup. I'll show where those modules are selected when we reach the sound fix. First, open the port's GitHub page and go to releases.
Walkthrough 03
Download the tools
Download the ready-made Windows package shown here called SOCPC.zip. Choose the release download rather than one of the source code archives. We're running the package application so we don't need to compile it. Next, download the Windows version of the standalone shared PS4 plus package extractor. The version shown here is 1.1. This tool has one job in our setup, extracting the game packages into folders the port can use. We're not installing the full emulator as part of this process.
Once those downloads are ready, put your game files somewhere easy to find. Keep the base game and its matching update clearly separated. The update must belong to the same game release. Don't choose it just because the name looks similar. Here's the first distinction that will save you some confusion. Unpacking a downloaded archive and extracting a game package are two different steps. The archive gives us the package file. The package extractor then gives us the actual game folder.
My game archive is split into several parts.
Walkthrough 04
Unpack the game archive
Keep all those parts together in the same directory. Start extraction from the first part and let the archive tool read the remaining parts automatically. You don't need to extract each part individually. I'm speeding up the waiting here. Once extraction finishes, open the resulting folders until you reach the base game's PKG file. Your wrapper folders might have different names from mine. What matters at this stage is finding the base package with the update package kept separate.
Now, extract the Windows package extractor zip. Keep the files inside it together, including the support libraries next to the executable. Place that folder beside your game package so both are visible.
Walkthrough 05
Extract the base PKG
Take the base game's PKG file and drag it directly onto the package extractor executable as shown here. A terminal window opens and starts extracting the contents. Let it finish. The scrolling file names are progress messages. They aren't a list of things you need to click or change. The important result is the folder created when extraction completes. Here, it's called CUSA08809. Inside it, we can see the game files, including eboot.bin and the folders named SA_MODULE and SA_SYS.
Keep track of this folder. We'll come back to it for the update and for the launcher. The original PKG is the input. This extracted folder is what we're preparing to run. Now, we need to apply the update.
Walkthrough 06
Apply the matching update
This is the part where a small folder mistake can make the rest of the setup confusing. So, watch both the source and the destination. Drag the matching update package onto the same extractor. This time, the output is a separate folder with patch at the end of its name. Open that patch folder and select everything inside it. Copy those contents, then open the extracted base game folder we just created and paste them there.
We're copying the contents into the game folder. We're not putting the entire patch folder inside another patch folder or leaving its contents somewhere unrelated. When Windows asks about matching file names, choose replace the files in the destination as shown here. Let that operation finish before moving on. That completes the merge used in this recording. In a moment, we'll check the version the launcher detects rather than guessing from a zip or folder name.
Next, extract the PC port zip and open the application called SSOC.exe.
Walkthrough 07
Set up the PC port
On the first run, it asks where the game is. Use the folder picker to navigate to your extracted game. This launcher can search for the game within a selected location. The result we're looking for is the recognized CUSA game folder containing EBOOT.BIN, CSE_MODULE, and CSE_SYS. Don't select the original archive or the PKG as though it were the extracted game. Follow the folder navigation on screen, then check the detection result. Here, the launcher identifies CUSA08809 and game version 1.01.
That's the confirmation to look for before continuing. You can also see a warning about missing sound modules. That warning matters, even though the game can still launch. We'll address it directly after this first startup. Click play and allow the game to load.
Walkthrough 08
First launch
The first shader preparation can take some time. So, an initial wait doesn't automatically mean installation has failed. I have shortened the loading here while keeping the actual setup choices visible. Choose your language. In my recording, I use English and leave HDR off. Then continue into the game. We've reached gameplay, but this is why launching successfully isn't the end of the check. The picture is working while the game is silent. Back in the launcher, the missing module warning explains what we still need to supply.
Walkthrough 09
Fix missing game audio
The sound fix uses the two SPRX files highlighted on screen, the NGS2 module and the ULT module. Keep their exact file names as shown. These are separate system modules, and they aren't bundled with the PC port. Use your own decrypted console modules or the files from your existing shared PS4 system modules that Keep both files available together in a folder you can find again. Now, here's the step that actually cleared the warning in my recording.
Simply moving a folder around wasn't enough. I had to tell the launcher which sound module folder to use. Open game and saves. Under sound, find sound modules and click browse. This is a separate selection from the game folder field above it. Navigate to the module folder and select it. The folder selected in my recording is named 11.00 sys modules. You don't need to copy that name. What's important is that the selected location contains the two required decrypted files.
After making that selection, return to the play page. The warning has changed to sound modules found. Keep that confirmation in mind. It tells us the launcher has detected the modules rather than just accepting an arbitrary folder path. Now, launch the game again.
Walkthrough 10
Relaunch and verify sound
I use continue here because I already started a save during the earlier attempt. The recording uses a 1080p output with frame generation off. You'll also see unlimited selected for the frame rate setting. Those are the settings shown on this machine, not a promise that every PC will perform the same way. Once we're back in the game, let's leave the narration and background music out for a few seconds so you can hear the result directly.
With the setup complete, we can move beyond the launcher and see it in actual gameplay. Here's the ride out followed by the first Colossus encounter. >> This is the first boss of this game. >> I'm keeping a longer section of the fight here so you can see movement, climbing, and attacks in one continuous passage.
Walkthrough 11
First-colossus gameplay
This is the part we wanted to reach, playing the game with the sound working rather than only showing a successful menu screen. I also get through the first Colossus in this session. That's what this recording demonstrates. It isn't a full game completion test or a controlled performance benchmark. >> This is the end of the first boss. The key checks are straightforward, the matching game and update, the correctly extracted game folder, and the two sound modules selected in the launcher.
Walkthrough 12
Checks and troubleshooting
If yours launches silently, check that sound modules field and its detection message first. If it fails to launch, include your port version, game version, graphics card, and the session log when reporting the problem to the project. That gives people something useful to investigate. That's the complete setup shown here, including the missing sound fix and the first Colossus test. The project and extractor links are in the description, so you can follow the same tools and check for later updates.
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