Asterigos: Curse of the Stars (PPSA08194)

[JJenkx]

Existing thread

• I searched this category for PPSA08194 and "Asterigos"; no thread exists.

Title

Asterigos: Curse of the Stars (PPSA08194)

Content version tested

The extraction's eboot.bin, with PlayGo files present.

AnyPS5 commit

main 474030e584, and the same main with #6959 merged in locally (head 327addf79e, merge 19acd6685d).

System tested

Linux 7.2.11 (Arch), Ryzen 9 7950X, Radeon RX 6650 XT, RADV Mesa 26.2.6, GCC, Release.

Furthest point

In-game: Outerrim, with the HUD and the first objective.

What is shown

300 s, Cross every 12 s from 30 s, left stick forward from 210 s.

Build	Result
main	The menus run at about 60 FPS, including "Select A Difficulty" (Story / Adventure / Challenge). In-game, the HUD shows health, mana 100/100, a potion count and the objective "Outerrim: Check surroundings for anything unusual". The 3D scene is almost black: only the outline of Hilda and of the plants is visible. About 11 FPS, exit 0 at 293 s.
+ #6959	The same area renders correctly: a misty, sunlit forest clearing with Hilda, bushes and glowing flowers. Same HUD, about 11 to 13 FPS, exit 0 at 294 s.

Current blocker

None in 300 s with #6959. Without it the 3D scene is dark: the UE4 case #6959 fixes, also seen today on Spirit of the North (#14019), Insomnis (#14054) and Override 2 (#6933).

How it was run

relinker --registry --rpath <build>/core/libs/libs eboot.elf app.elf
APS5_PLAYGO_UNLISTED_CHUNKS=installed ./app.elf

AI-assisted testing and report: yes.

[JJenkx]

Where the frame time goes in the first area, Outerrim, on main 0836dfdf4f. One run with APS5_PROFILE_GPU=1 APS5_TRACE_DRAW_CACHE=1 APS5_TRACE_SECONDS=200:20. The renderer is at 1920x1080.

Frame: p50 68 ms, p99 120 ms. The GPU is busy about 44 ms per present, so the CPU is the larger part.

CPU per frame:

Phase	Time
Driver.Packet	139 ms
Driver.Packet.memory_wait	66 ms
Driver.Draw	37 ms
Driver.Draw.shader_compile_and_link	22.5 ms
Shader.DrawStage	20.5 ms

Draw cache, per 10 s:

• 110,598 lookups with 4,968 hits (4.5%).
• 105,464 of the misses are "user words/pointers only".
• The data-only path reuses 17,981 stages and compiles 192,679.

That is the same pattern as Thymesia (#14031): 0% hits there, 364k stages compiled per 10 s. In both UE4 titles each draw's user data, its per-draw constant pointers, differs, so most draws re-materialize their stages, and that CPU work is a large share of the frame. This is profiling data, not a change or a performance claim.

AI-assisted analysis: yes.