Broken Sword - Shadow of the Templars: Reforged (PPSA21480)

[JJenkx]

Existing thread

• Searched PPSA21480 and Broken Sword; no existing Game bring-up thread found.

Title

Broken Sword - Shadow of the Templars: Reforged (PPSA21480)

Content version tested

01.110.461 from sce_sys/param.json (menu displays Version 1.1.10).

AnyPS5 commit

Production main 73f4f7e06e4f210a8c6570e335fd654dc0a86134; actual compiled SDK bank 59fbec354b5c886294a043268be63f4724e04919 adds only a GuestMemory test fixture, no optional production change. Current main 474030e58424fefdb65e5df9f3820810fbb4553c differs from that production base only in test infrastructure. Both source deltas and the binary manifest are attached. No PR6321 production change or game-byte patch is used.

System tested

Arch Linux x86_64, kernel 7.2.11-arch1-1; GCC 16.2.1, Release; AMD Radeon RX 6650 XT (RADV NAVI23), Mesa 26.2.6-1; X11, 974×548 renderer window.

Furthest point

In game, limited to the initial café exterior.

What is shown

• Readable main menu; New Game → Story selection → seven tutorial pages → opening movie renders. I skipped the movie after checking its beginning.
• The café exterior renders with protagonist/subtitles. Cursor movement responds to the gamepad injection file.
• The game writes BS1R_AutoSave_1.sav. A second run used an independent copy of the first run's inactive savedata: Continue loads directly into the same scene.
• In that resumed scene, cursor movement and character movement toward the foreground were visually confirmed. The help overlay opens and closes.
• The window counter stays about 59.94 FPS in the observed scene. This is not a performance benchmark or a gain from a change.
• First native run: planned close at ~232 s, exit 0 after 233.9 s. Reload/control run: planned close at ~140 s, exit 0 after 142.2 s. No unimplemented-export stop or native crash in these two runs.

Limits: no later puzzles/scene transitions, complete playthrough, audio validation or PS5 fidelity comparison. One AMD system only; no general stability claim. The window captures and before/after movement images are attached.

Current blocker

None observed in this short initial-scene check. No required open PR or local production change identified. Later progress remains untested.

How it was run

Reuse the existing extraction, unwrap eboot.bin and shipped sce_module/libc.prx, and relink with the matching SDK:

relinker --registry --no-patches --linux-fixed-base 0x400000 \
  --rpath /absolute/sdk/core/libs/libs \
  normalized/eboot.elf private-runtime/app.elf

The normalized sce_module/libc.prx is beside the executable's input directory; output module directories and all writable state are private. Runtime app0 uses individual immutable asset links, not shared writable module directories.

LD_LIBRARY_PATH=/absolute/sdk/core/libs/libs \
VK_DRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.json \
ANYPS5_GPU='AMD Radeon RX 6650 XT' \
APS5_HOST_IMPORT_MIB=16384 ANYPS5_NO_SHADER_CACHE=1 \
MESA_SHADER_CACHE_DISABLE=true ANYPS5_HOST_REPORT=1 \
APS5_PAD_INPUT_FILE=/absolute/private-runtime/pad-input.txt \
./app.elf

The local harness temporarily uses udmabuf size limit 16384 MiB and restores 64 afterward. Each whole native harness takes the Linux GPU FIFO. The recorded executable/module/param input hashes remain unchanged, and no private native process remains after either close. Saves from each run are retained privately.

These were interactive bring-up runs: the raw report's scheduled-input list is empty; manual-inputs.jsonl records the actual controls. A tutorial OCR mismatch stopped that controller before sending an unverified input; recorded checked inputs then completed the pages. The reload harness also had a log-name collision before any game launch; that preparation attempt is excluded from the two native results.

Raw logs, timestamped inputs/reports, screenshots, source deltas, binary manifest and qualified per-run reviews. Downloaded archive verified SHA-256 ff7c3d5ba4a0a602c72db39ce4cbe636282624e990a9114e017a5f7210235147. No game binaries, assets, savedata or memory dumps included.

AI-assisted: yes, Codex.