Wolverine on PC with KytyPS5 Frank: game-root path and Play.bat setup
ItsOOGWAY · PC guides & recorded tests
Wolverine on PC with KytyPS5 Frank: game-root path and Play.bat setup
Marvel's Wolverine on PC: a step-by-step Windows setup guide using KytyPS5-Frank v0.3, followed by gameplay from the project. This walkthrough covers the Windows download, game-folder setup, Play.bat configuration, first launch, logs and the in-game Performance mode option.
The key checkpoint: Locate the directory that directly contains eboot.bin, set that folder in Play.bat, and keep the supplied tuned defaults as your starting point.
Before you start
- Recorded fork: KytyPS5 Frank 0.3; game PPSA03671, 01.001.005.
- Use the complete Windows archive and your own compatible dump.
- Keep kyty_log.txt from a failed attempt.
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
Check the fork and recorded requirements
This is the Kyty PS5 Frank fork. It is an experimental emulator build, rather than an official Windows release of Wolverine. The version shown here is version zero point three. If a newer version is available when you watch this, check its release notes before following the same steps. The game's tested identifier is P P S A zero three six seven one, with version zero one, zero zero one, zero zero five. Those details matter because a different game version is not automatically covered by the same test results.
You'll need your own compatible game files. The emulator download does not include the game. For Windows, the project lists a sixty-four-bit installation of Windows ten or eleven, a processor with AVX2 support, and a graphics card supporting Vulkan 1.3 with a recent driver. These are requirements for trying the build, not a promise that every supported machine will get the same performance.
Walkthrough 02
Extract the ready-made Windows package
Let's get the correct download first. Open the repository linked in the resources section, go to Releases, and expand the assets for the Windows release. Download the file ending in win sixty-four dot zip. The source-code archives are separate files, so make sure you're taking the ready-made Windows package. Once that finishes, extract the entire ZIP into its own folder. Keep the files and folders together. We want the emulator, its libraries, and the launch files in the structure supplied by the release.
Don't pull just the executable out onto the desktop.
Walkthrough 03
Locate the actual game root
Next, prepare the game folder. In this recording, the game files are inside an archive, so I extract them first. If yours are already extracted, you can skip that waiting step. Make sure the destination has enough free space for the extracted files as well as any archive you are keeping. When extraction finishes, open the folders until you can actually see eboot.bin. This is the checkpoint to remember. The folder containing that file is the game folder we need.
A folder one level above it may look correct because it has the game's name, but it is not necessarily the folder the launcher expects. Here, the files are nested inside an app folder. Your drive letter or folder names may be different. Follow the file, rather than copying my path exactly. Once eboot.bin is visible, click the address bar and copy the full folder path.
Walkthrough 04
Set the folder in Play.bat
Now return to the extracted emulator folder. Find Play.bat and open it in a text editor. In the recording, I use Notepad. Near the top, there is a line beginning with set GAME, followed by an example location. Replace that example location with the full path to your game folder. We are pointing to the folder, not to eboot.bin itself. Keep the rest of the batch file as supplied, and save your change. Also make sure the file stays a dot bat file instead of becoming a new text document.
That is the main launch setup. The project also includes launcher dot exe if you prefer its game library. In the recording, I open its settings and add the folder to the game directories, then the Wolverine tile appears. That is the launcher route; you don't need to keep switching between both interfaces for every attempt. For the launch we're following here, I return to the configured Play.bat and run it. Before editing it, this file simply asked me to set the game folder.
If you see that message, go back to the path and check for eboot.bin in that exact location. Waiting longer at that message will not load the game.
Walkthrough 05
Separate first-launch waits from a failure
After the path is set, the emulator starts and the opening logos appear. There are stretches of black screen between the logos and the first setup prompts, so I've shortened those waits in the video. Don't use the edited waiting time as a stopwatch for your own first launch. This is also where it helps to separate a loading delay from a crash. A blank window on its own does not tell you the cause.
In my recording, some early attempts did not reach the menu, and a later launch reached the setup screens. That doesn't mean the batch file fixes every crash; it gives us a clear launch command and a place to check the log. The batch file writes kyty_log.txt beside itself. If your game closes or repeatedly stops at the same point, keep that log and note the build and game version you're using. Those details are much more useful for troubleshooting than changing several settings and losing track of what happened.
Once the first setup prompts appear, work through the accessibility and initial options, then continue to the menu. At this point, we have passed the folder setup and reached the game itself. You can now start the opening and check how the build behaves in an actual scene.
Walkthrough 06
Inspect gameplay and the remaining limitations
There is one in-game option worth showing clearly. From the pause menu, open Settings and go to Visuals. The recording shows Graphics Mode set to Performance. That is the game's mode selection. It is not a guarantee of sixty frames per second, and selecting it does not remove the emulator's current limitations. The fork already includes settings tuned for Wolverine, so I would start with those release defaults and change one thing at a time.
The motion blur and other screen-effect options are personal preferences. I'm not presenting them as a tested performance fix. Now let's look at the result: movement, traversal, and combat running in this build. I'll leave a section playing without narration so you can see how it behaves, rather than only showing a few quick flashes between setup steps. This is meaningful progress, but it is still an early project. The repository lists occasional crashes or freezes, flickering textures, and a missing scent-trail effect in one area.
Reaching gameplay is not the same as confirming the complete game can be finished. If you try it, keep that expectation and save your troubleshooting details when something goes wrong. The full path through the setup is straightforward: get the Windows release, extract the package, locate the folder with eboot.bin, set that folder in Play.bat, and launch. If your result differs, the build version, game version, and log are the first things to collect.
If your result differs
| Situation | Next useful check |
|---|---|
| Play.bat asks for the game folder | Set GAME to the folder containing eboot.bin, not the file itself. |
| A blank window closes | Preserve the run log and version information; a black window alone does not identify a cause. |
| Performance mode is selected | That in-game choice does not guarantee 60 FPS or complete-game stability. |
Comments
Post a Comment