Skip to content

Cloud play fixes for HU region (and possibly other non-US regions) - #43

Open
nyakaspeter wants to merge 6 commits into
ForWard-Technologies-LLC:masterfrom
nyakaspeter:fix/cloud-play
Open

Cloud play fixes for HU region (and possibly other non-US regions)#43
nyakaspeter wants to merge 6 commits into
ForWard-Technologies-LLC:masterfrom
nyakaspeter:fix/cloud-play

Conversation

@nyakaspeter

Copy link
Copy Markdown
Contributor

Hi I reapplied some of my earlier fixes, now in the shared C library. Other regions should still be tested to make sure they are not regressed. These are the games I confirmed working:

Game Platform Coverage / entitlement case
God of War (2018) PS4 Canonical owned PS4 entitlement
God of War: Ascension PS3 PS3 Classic catalog route
Bloodborne PS4 Owned PS4 entitlement
Assassin’s Creed Unity PS4 Owned PS4 entitlement
Trials of the Blood Dragon PS4 Owned PS4 entitlement
Ratchet & Clank: A Crack in Time PS3 PS3 Classic catalog route
Trine 4 PS4 PS4 catalog/entitlement route
Uncharted: The Nathan Drake Collection PS4 PS4 bundle entitlement
Uncharted: Legacy of Thieves Collection PS5 PS5 collection/upgrade entitlement
Death Stranding PS4 PS4 edition
Syphon Filter Classic Classic/cross-platform entitlement
Ratchet & Clank: Rift Apart PS5 Standard owned PS5 entitlement
Marvel’s Spider-Man Remastered PS5 PS5 wrapper/cross-buy entitlement
Fortnite PS5 Free-to-play/cross-generation entitlement
Death Stranding Director’s Cut PS5 Separate PS5 edition
Horizon Forbidden West PS5 Disc-upgrade rescue using replacement product ID
Horizon Zero Dawn Remastered PS5 Supplement-only owned entitlement

nyakaspeter and others added 6 commits July 21, 2026 20:56
Five workflow_dispatch workflows, one per platform, each building that platform
(build-only — no store deploy, no Dropbox, no signing/deploy secrets) and
uploading the result as a workflow artifact. Versions come from CMakeLists.txt
via the extract-version action.

- build-artifact-linux.yml    Pylux-Linux-<ver>.AppImage + Pylux-Linux-<ver>.zip
- build-artifact-android.yml  Pylux-Android-<ver>.apk (debug-signed)
- build-artifact-macos.yml    Pylux-macOS-<ver>.zip (ad-hoc .app, arm64)
- build-artifact-ios.yml      Pylux-iOS-<ver>.ipa (UNSIGNED, sideload only)
- build-artifact-windows.yml  Pylux-Windows-<ver>.exe + Pylux-Windows-<ver>.zip

Reuses the deploy/build workflows' build + toolchain steps; drops the
signing/deploy tails.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@forward-technologies

Copy link
Copy Markdown
Collaborator

Awesome thanks! I will test this out this weekend, appreciate the help! :)

@forward-technologies

forward-technologies commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

Hi @nyakaspeter — thank you for #43, this was excellent work. All four of your fixes were verified with live API testing and have landed in release/beta (#49), with the full technical write-up in #50.

We made one significant extension: the fallback catalog now walks all of APOLLOROOT's children instead of just the APOLLOPS3* container. That child turned out to be ~95% PS3, while the PS4 streaming catalog lives in the other children — the walk grows the GB-family catalog from 264 to 786 titles, and we verified your full PS3 set is included. Was there a reason you scoped the fix to the PS3 container? If you had already tried the other children and hit problems, we'd love to know before we ship.

We also added some hardening around store routing and the $0 acquire, but we swept all 786 catalog containers to confirm entitlement resolution is identical to your branch everywhere, Bloodborne included — your HU behavior is unchanged.

If you have a moment, could you retest with this build: Bloodborne, a PS3 classic, one or two non-owned PS4 titles from the newly-added catalog, and an owned PS5 title?

APK (2.11.4): https://github.com/ForWard-Technologies-LLC/Pylux/actions/runs/30736325642/artifacts/8829780766
Changes: https://github.com/ForWard-Technologies-LLC/Pylux/pull/49/files

Thanks again — once your retest confirms, this ships in 2.11.4.

forward-technologies added a commit that referenced this pull request Aug 2, 2026
They came along with PR #43's branch but are unrelated to the cloud fixes;
they can land separately if wanted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dneill2007-ux pushed a commit to dneill2007-ux/Pylux-beta that referenced this pull request Aug 4, 2026
The public fallback paginated a single container expecting product rows, but
Sony restructured APOLLOROOT into one level of category containers, so
region-unsupported accounts got an empty PS Now catalog. Walking only the PS3
child (as PR ForWard-Technologies-LLC#43 proposed) restores 264-330 classics but misses the ~535-title
PS4 streamable catalog that lives in the genre/alphabetical children.

Walk every child of the regional root once instead, deduped by product id, with
per-container completeness so a failed child still blocks caching a partial
list. Live-verified against an independent walk of both store families:
US 853 titles (537 PS4 + 316 legacy), GB/HU 786 (536 PS4 + 250 legacy),
identical id sets, zero duplicates; native-account fetch is byte-identical
before/after. Adds apollo-fallback-test, a region harness that runs the
anonymous walk as any account country.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@nyakaspeter

Copy link
Copy Markdown
Contributor Author

Hi @forward-technologies I retested all of the above games with your build and all streamed fine for me. The only issue I found is that some games show extra cards in the game list, probably because I own multiple SKUs of them, and only one of them can actually start a stream. But I don't think it's a big deal.

@forward-technologies

Copy link
Copy Markdown
Collaborator

Hi @forward-technologies I retested all of the above games with your build and all streamed fine for me. The only issue I found is that some games show extra cards in the game list, probably because I own multiple SKUs of them, and only one of them can actually start a stream. But I don't think it's a big deal.

Thanks for checking, I'll try to get this merged in tonight :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants