Find the failure stage.
The first useful clue is when the error appears.
Conversion
No usable output yet
Library loading
Output exists, startup fails
Runtime
Loads, then encounters a failure
Conversion fails
Compare your arguments and input layout with the conversion guide. Confirm the input is a clean ELF and the module directories are arranged as the upstream specifies. Conversion exit code 1 means invalid arguments; 2 means conversion failed. Read stderr for the specific reason.
Windows error 126 or 193
The upstream associates error 126 with missing dependencies for self-built libraries, including the matching MinGW runtime DLLs. Error 193 can occur when an original PS5 module is put in libs/. Compare each file’s role and location with the documented runtime layout before replacing anything.
A function is missing or throws
The upstream import audit distinguishes implemented functions, throwing stubs, absent exports, and title modules. An audit that finds no loading blocker is not a playability test. Unsupported runtime states may still terminate the application.
Prepare a useful upstream report
- Record the upstream commit and how you built or obtained the tool.
- Include your OS, CPU, GPU, driver, and title ID.
- Quote the first relevant error and identify the failure stage.
- Remove personal paths and private data from logs. Do not attach copyrighted game files.
Search existing reports before opening a new issue. Search upstream issues .