AnyPS5 Workbench: build a source snapshot and test a Windows conversion
ItsOOGWAY · Recorded PC guides · 03
AnyPS5 Workbench: build a source snapshot and test a Windows conversion
Select an official AnyPS5 source snapshot, convert a supported game dump into a separate Windows package, and check the result with a real launch. The recorded example is Hollow Knight: Silksong.
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.
Watch the recorded video
Watch on YouTube ↗ · Screenshots below come from this final recording.
Video chapters
- 0:00 Silksong running on Windows
- 0:46 What AnyPS5 Workbench does
- 1:36 Requirements and supported game dumps
- 2:26 Open the portable app
- 3:16 Choose official source or download latest
- 4:08 Find and select your game
- 4:56 Output folder and build options
- 5:47 Build and convert to Windows
- 6:41 Understand the converted package
- 7:34 Launch and check the game
- 8:32 Test another source safely
- 9:25 Result and next steps
Before you start
- Have your own compatible, already-decrypted game dump ready; Workbench does not obtain or decrypt games.
- Leave room for the original game, a separate conversion output, portable build tools and caches. First-time setup needs internet access.
- Check the graphics requirements and Vulkan driver. A loader being detected is a basic check, not a promise that a game will run.
Stage 01
Open the complete portable Workbench package
Extract the whole Workbench ZIP before opening the application. Keep the executable and its supporting internal folder together. The portable interface can open without manually installing a complete development environment; its first build still needs to prepare the tools and dependencies required by the selected source.
This recording was made on a development PC with existing caches. Its shortened waits are not a clean-PC installation benchmark. If setup is downloading or compiling, read the progress rather than repeatedly starting the same action.
Stage 02
Choose the official source snapshot
In Source snapshot, use Browse ZIP for an official archive you already have. Download latest source is a separate option for fetching the official main snapshot available at that time. An unmerged pull request is not automatically part of main.
The demonstration uses the already-selected archive. Keep the exact source commit from the conversion report so later results can be compared. “Latest” is not a reproducible version identifier, and an older frontend may need updating when upstream build requirements change.
Stage 03
Find the game and confirm the selected title
Choose Folder for extracted input or ZIP for a supported archive, then click Find games. Check the discovered title and title ID in the list. Entering a path alone does not establish that the intended game was selected.
Keep the input structure intact: metadata, modules, executable and assets belong together. The recording selects Silksong. A random executable, incomplete extraction or encrypted package is not interchangeable with the supported input shown here.
Stage 04
Keep the conversion output separate
Choose a short Windows output path outside the original game folder. Leave Build jobs on Auto for the baseline. On the recorded Ryzen system, Intel CPU compatibility is off. That option belongs to the upstream Intel rewriting route where applicable; it is not a general FPS improvement.
Do not enter a random fixed-base address. Convert with ordinary supported options first, preserve the original input, and keep the full error message if verification or a build stops.
Stage 05
Convert and keep the complete Windows package
Click Convert to Windows. Workbench verifies inputs, prepares or reuses the matching engine build, then converts and packages the game. A cached build of the same source can finish much sooner than a fresh build, so elapsed times from different runs are not directly comparable.
After the Windows executable is created, open the output directory. Keep Play.exe, assets, libraries, fonts, support files and the conversion report together. Copying only the executable can break its dependencies. Conversion success is the package-creation milestone; playability is the next test.
Stage 06
Launch and describe the furthest point reached
The recording opens Play.exe directly, reaches the menu, and continues into early gameplay. This establishes a short successful launch and movement test for this snapshot and game, not a complete playthrough.
For saved runtime evidence, use Run converted game or the output folder’s Launch with logs.cmd. A visible terminal during a direct launch does not automatically create a captured Workbench session. When comparing another source, create a separate output and repeat the same scene with the same settings.
If your result differs
| Situation | Next useful check |
|---|---|
| Build requirements changed | Use an appropriate current Workbench build and check the selected upstream snapshot. Keep the earlier working conversion. |
| A Windows executable exists but gameplay fails | Report the exact point reached: launch, menu, loading or gameplay. These are different milestones. |
| You need useful community evidence | Keep the source commit, game version, hardware and settings; launch through the logging route for runtime logs. |
Keep the successful package and original input until another snapshot has passed the same short test. A reproducible result is more useful than assuming every newer source must be better.
Comments
Post a Comment