In this guide
01 / FIELD NOTES
Upstream and forks are different builds
shadPS4 is the original emulator project. Forks can add fixes and change defaults independently. Keep the repository name beside every compatibility claim so you can tell which software was actually tested.
The inFAMOUS Second Son shadPS4 guides below cover two game-focused forks. HayatoG’s runtime is a separate route covered in our PC port guide; its launcher instructions should not be pasted into an emulator configuration.
| Build | Documented game match | Scope |
|---|---|---|
| AYOUB1080p | Bundled EU patches: CUSA00004, APP_VER 01.00 | Patch compatibility is narrower than the automatic game profile. |
| AxylPup v1.0.2 | Tested: CUSA00004, update 1.07 | Follow this release’s bundled instructions. |
02 / FIELD NOTES
A profile is not a patch match
AYOUB1080p documents automatic game settings for CUSA00004 and CUSA00223, while its bundled European patch file targets APP_VER 01.00. These are separate statements: recognizing a title does not establish that every patch applies to every update.
For an inFAMOUS Second Son shadPS4 configuration, retain the original patch file and change one setting at a time. Check the log for applied or skipped patches before interpreting the image on screen.
Write down the exact setting name and previous value. If you change resolution, memory options and patches together, an improvement or regression becomes difficult to trace. Reproduce the same scene after each change.
A patch instruction for one fork can be irrelevant to another. Stop when the documented title ID or update differs from your files; a matching game name alone is insufficient.
03 / FIELD NOTES
Separate startup work from a crash
First-launch behavior can differ between releases. Read the selected build’s notes before concluding that a progress screen has frozen. Preserve the original log before restarting so the last completed operation remains available.
AxylPup’s v1.0.2 notes address a misleading startup progress display and a save-loading memory issue. That is a version-specific change, not a guarantee that any later freeze has the same cause.
Use the current inFAMOUS Second Son shadPS4 instructions as your baseline. If the game reaches a menu but fails while loading a save, report that distinction instead of describing everything as a startup failure.
04 / FIELD NOTES
Make a useful issue report
A repeatable report is more useful than a long list of settings copied from unrelated tutorials. Prepare these details before opening an issue in the repository that produced your build.
Identify the executable
Include the fork owner, release tag and operating system. State whether the problem started after an update or also occurs in your previous build.
Describe the failing scene
Record the game title ID, update, mission or menu, expected behavior and actual result. Mention whether a fresh launch and an existing save behave differently.
Attach focused evidence
Provide the relevant log, GPU, driver and CPU details. Review logs for personal paths before sharing. Avoid posting game files or someone else’s save as a substitute for a description.
QUESTIONS / ANSWERS
Before you go further
Can I use any patch with the same game name?
No. Match its title ID, update and documented build. A patch may be skipped or behave incorrectly outside its intended target; retain a working baseline before experimenting.
Does an upstream update include every fork fix?
Do not assume that it does. Check the release notes or merged changes for the specific fix. Similar version names do not establish identical behavior.
Is a shared shader cache a universal fix?
Treat caches as build-specific data and follow the project’s instructions. A cache does not resolve a wrong game version, missing file or unrelated graphics error.
SOURCES / NEXT STEPS
Follow the original evidence
Sources reviewed October 20, 2026. Project documentation can change; check the release you intend to use. We have not independently tested game performance.