Demon’s Souls Remake on PC: select app0, prepare shaders and test Boletaria
ItsOOGWAY · PC guides & recorded tests
Demon’s Souls Remake on PC: select app0, prepare shaders and test Boletaria
How to play Demon's Souls Remake on PC: a complete Windows setup walkthrough using the Demon's Souls-focused KytyPS5 fork. I show the correct Windows download, archive extraction, the game-folder error and fix, shader preparation, first boot, and actual combat on an RTX 4070 SUPER.
The key checkpoint: Select the inner game root containing eboot.bin and sce_sys, not the outer archive folder. Missing param.json and shader-preparation prompts are different issues.
Before you start
- Recorded Windows build: 22 October 2026; game PPSA01341, version 1.07.
- Keep multipart archive pieces together and finish extraction.
- Allow substantial first-time shader preparation without treating its estimate as universal.
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
Choose the recorded Windows package
Start with the GitHub page linked in the resources section. We're using this community fork of Kitty P S Five, which is specifically tuned for Demon's Souls. Open Releases. The Windows build I recorded is dated October twenty-second, twenty twenty-six. This is the repository and release used throughout this guide. Under Assets, download the packaged Windows archive shown here. The Linux package is a separate download, and the source-code archives are for a different workflow.
For these steps, we want the ready-made Windows build with its launcher and supporting files. You don't need to compile the source yourself. Before going further, check your game version. This guide uses the PS Five remake, version 1.07. The exact title ID is on screen: P P S A, zero one three four one. Keep that version in mind when comparing your setup with mine. This is an unofficial community project, and compatibility can change between builds.
You'll need your own decrypted game dump as well. The emulator package doesn't contain Demon's Souls. I already have the game files here, so we're going straight into preparing them. There are two separate things to extract: the game archive and the Windows program archive. We'll start with the game.
Walkthrough 02
Complete game and application extraction
My game files are split across several archive parts. Keep all those parts together in the same folder, with their original names and numbering. Start extraction from the first part; the archive program will read the others as it needs them. If your game is already fully extracted, you can move straight to the launcher setup. Choose a location with enough free space for the extracted files. I'm using my games drive here. If your archive asks for a password, enter the one belonging to that archive.
I did get an incorrect-password message during this recording. That happens before the emulator is involved, so resolve the extraction error before continuing. Now let extraction finish. I'm speeding up the waiting, but notice the completed result before we move on. Seeing a new folder appear isn't the same as having every file ready. Once extraction finishes without errors, open that folder. In a moment, choosing the right level inside it will make the difference between an error and a recognised game.
Extract the Windows program archive into its own folder next. Open the extracted directories until you see Kitty Launcher dot EXE, along with the other executables, scripts, and DLL files. Keep those together and double-click the launcher. That brings us to the Play page, where we choose the game location.
Walkthrough 03
Correct the missing-param.json folder mistake
Here's the mistake worth catching before you repeat it. I used the Folder button and selected an outer directory that contained my game. That looked reasonable, but the launcher reported that it couldn't find the game's param.json file. The game was extracted; I had simply pointed the program at the wrong level. To correct it, open the folders inside that location until you reach the app-zero directory shown here. Mine ends with P P S A zero one three four one, dash app zero.
Open that directory and choose Select Folder. You want the directory containing the actual game files, rather than the wrapper folders around it. Check the contents if you're unsure. The correct game root directly contains eboot.bin and the sce_sys folder. Inside that system folder is param.json. Select the root that holds both of them. Don't select the system folder on its own, and don't select an archive that still needs extracting. With the inner folder selected, the startup console identifies Demon's Souls and version 1.07.
That's our confirmation. Keep this check in mind if you get stuck: an error about the selected location doesn't automatically mean you need another copy of the game. First make sure the launcher can actually see its metadata.
Walkthrough 04
Review the baseline before first launch
Before we start, here are the settings used in this recording. The summary shows a twenty-five-sixty by fourteen-forty window, sixteen-by-nine, fourteen-forty-p three-D rendering with the game's own anti-aliasing, the Standard graphics preset, and frame generation off. This gives you a specific setup to compare against when we reach the gameplay test. There are also notices about optional DLSS and FSR components. I'm leaving those out of this walkthrough. The configuration shown here uses the game's own rendering path.
An optional graphics component being unavailable is a different message from the missing-game-folder error, so read what the launcher is actually reporting before trying to fix it. The game is now recognised, but there's one more first-time step before we judge its smoothness. When I tried to launch, the program warned that scenes and effects could stutter because their shaders weren't precompiled. This is where it's easy to think something is broken, even though the program is asking for preparation time.
Shader preparation gets work ready for the graphics card before you encounter those scenes and effects in play. It can reduce interruptions from that work happening for the first time during gameplay. It doesn't guarantee a fixed frame rate, and it won't remove every slowdown. We'll check the actual result once the character is moving and fighting.
Walkthrough 05
Allow shader preparation to finish
Use Precompile shaders in the launcher, or choose Precompile first when the startup prompt appears. The prompt here estimated about eighty minutes on my PC. That's an estimate for this machine, rather than a waiting time everyone will get. This first preparation can take much longer than the small program download might suggest. Watch the console for progress. In my recording it reports batches of work, including completed, running, and waiting tasks. Updates don't appear every second, so a quiet-looking window between updates isn't enough on its own to call the process frozen.
Start one job and give it time instead of repeatedly pressing Play or opening several copies. I'm shortening that wait in the edit and moving forward to the next recording, where the game has booted. The useful parts are the preparation prompt, the progress, and what happens next. We can now check that this setup gets past the console and into the actual game. At first boot, choose your language and confirm the display calibration.
Set the brightness for your own screen. These menus let you check that the game has started and responds to input, so I'll keep the selections clear. Once they're confirmed, continue through the opening screens to character creation.
Walkthrough 06
Check combat, the Nexus and Boletaria
Choose your appearance, class, and starting gift. I select a Knight in this recording, then finalise the character. You can make your own choices here; they aren't required fixes for the emulator. We'll shorten the introductory cinematics and move into the opening passage, where we can test movement and combat. Now we're controlling the character. The footage continues through several fights, reaches the Nexus, and then goes into the Gates of Boletaria. That's the next useful test: does it still perform well when we're out of the menus and moving through another area?
I'll show both the combat and the frame counter. For context, this recording is on my Ryzen seven fifty-eight hundred X, RTX forty seventy Super with twelve gigabytes of video memory, and thirty-two gigabytes of RAM. Those details are visible in the launcher and game window. Use them as context for this footage, rather than expecting the same result from a different PC. The counter reaches sixty in parts of the recording, and several other samples are in the fifties.
But a later Boletaria sample drops into the thirties. So this is running well enough for me to move through the areas and fight, with performance that varies. I wouldn't label it locked sixty F P S, or claim the whole game has been tested from this session. Here's a continuous section at normal speed with the game sound. Watch the movement, attacks, and camera turns, as well as the counter. The extraction and preparation waits were shortened; this part is left at its recorded speed so you can judge the result for yourself.
If you're following along and haven't reached this point, use the stage where it stopped to narrow things down. An archive error belongs to extraction. A missing param.json message means checking the selected game folder. A shader-preparation warning asks for a different step again. In my recording, correcting the folder was what got the game recognised; changing graphics settings wasn't the answer to that error.
If your result differs
| Situation | Next useful check |
|---|---|
| param.json cannot be found | Choose the app0 root holding eboot.bin and sce_sys/param.json. |
| Shader preparation takes a long time | Watch its work counters and avoid repeatedly launching more jobs. |
| FPS drops later | The footage reaches 60 in places and later drops into the thirties; it is not a locked-60 test. |
Comments
Post a Comment