God of War III Remastered on PC: game folders, updates and launcher settings
ItsOOGWAY · Recorded PC guides · 05
God of War III Remastered on PC: game folders, updates and launcher settings
Follow the recorded community-port setup from the Windows release and extracted PS4 Remastered data to the matching update, launcher configuration and opening combat.
Resources from this video
Project links & documentation
Every resource URL from this video’s description is collected here. Recorded-release links identify the build used; current project pages may describe newer versions.
No third-party game-source URL is provided in this article. The port itself contains no game files. Use your own supported dump; this article does not verify or endorse third-party game packages.
Watch the recorded video
Watch on YouTube ↗ · Screenshots below come from this final recording.
Video chapters
- 0:00 Gameplay first
- 0:42 Which PC port and game edition
- 1:28 Requirements and preparation
- 2:17 Download the Windows release
- 3:05 Prepare your game data
- 3:55 Package extraction
- 4:46 Matching game update
- 5:32 Select the game folder
- 6:23 Graphics settings
- 7:16 FPS cap vs engine target
- 8:14 First launch
- 9:02 Opening combat test
- 10:12 Troubleshooting
- 11:09 Final setup checklist
Before you start
- Prepare your own supported game dump and a matching update; the port does not contain the game.
- Leave space for source packages, extracted data and a backed-up working copy.
- Check the requirements for the release you choose. The recorded guide describes Windows 10/11 x64, an AVX-capable CPU and Vulkan 1.3 graphics.
Stage 01
Download the ready-to-run Windows release
Open the exact 2.5.0 release linked below and select the Windows package used by the guide, rather than a Source code archive. Extract the complete release to its own folder and keep its support files together.
The project name and current release can change. This post explains the recorded 2.5.0 route. If you choose a later build, read its instructions before applying an old control or setting. The recorded upload does not test the latest release automatically.
Stage 02
Extract the game package completely
If your own dump is inside an outer archive, extract that first to reach the package. For the demonstrated drag-and-drop route, extract ShadPS4Plus PKG Extractor 1.1, then drop the game PKG directly onto pkg_extractor.exe.
Wait for completion. An output directory appearing is not enough if files are still being written. Check the result for eboot.bin and its supporting directories, including sce_module and sce_sys. Skip repeated extraction if you already have a complete supported folder.
Stage 03
Match and merge the update into a working copy
The recording extracts a matching update separately, then copies its contents into the corresponding base-game folder and replaces matching files. Keep the original dump backed up because this changes the working copy.
The game and update must belong to the same title ID. The useful confirmation later is CUSA01715 / 01.02 in the launcher. If your data is already updated, do not repeat a merge just because it appears here. An update package alone is not the full game.
Stage 04
Choose the root containing eboot.bin
Run the Windows launcher from its extracted folder. On Game, use Browse beside Game folder and select the actual game root. A parent directory holding several games or an extra nested folder is the wrong level.
The optional update-folder field is empty in this recording because the update was merged already. Save location is a different setting; keep track of saves before moving the port or replacing a build.
Stage 05
Separate selected settings from measured performance
Inspect Graphics and Performance with a stable baseline first. The recording explores resolution, window mode, VSync, filtering and engine frame-rate settings. Those are recorded choices, not universally optimal settings.
Frame-rate limit is the cap; engine frame rate is the engine target. A 240 option or 4K dropdown is not a measurement. The sampled gameplay overlay reports Native. If changing options, apply pending changes and compare the same scene. Reduce filtering if the release’s documented texture issue appears.
Stage 06
Launch and check opening combat
Save pending changes and press Play. Give initial preparation and shader work time to progress, then check movement, picture, sound and attacks after the opening. The video reaches real combat, which is stronger evidence than merely opening the launcher.
This remains an opening-session test. A release-note workaround for some high-frame-rate progression issues is described in the narration, but is not demonstrated here. Consult the recorded release guidance for the affected scene instead of assuming every failure has that cause.
If your result differs
| Situation | Next useful check |
|---|---|
| Game root not recognized | Check extraction completion and the folder with eboot.bin directly inside it. |
| Update or version mismatch | Verify title ID and update metadata. Keep your original data before redoing a working-copy merge. |
| Performance or progression changes at high targets | Return to a stable baseline and consult the release notes for the exact scene. A selected target is not achieved FPS. |
Keep a note of the port release, game version and applied settings once the opening test works. Save a log and describe the exact scene if you report a problem; the current repository name may differ from the one in the video.
Comments
Post a Comment