ASTRO BOT (PPSA21567) - In-Game (Playable, Passes Tutorial, Heavy Queue Lag)

[TheEzio5]

Existing thread

• I searched this category for the title ID and no thread exists for this title on any platform.

Title

ASTRO BOT (PPSA21567)

Content version tested

01.019.000 (target content version 01.018.000, PPSA21567_00 EU dump)[cite: 1]

AnyPS5 commit

Built from main branch commit eb8dcfe using MinGW-w64 GCC 15.2.0, CMake, and Ninja. Contains PR #5596 (fix(libc): track writes to singly mapped direct memory without faults on Windows) and commit e56a7c2 (handling Texture.cpp storage image result bounds).

System tested

• OS: Windows 11 Home / Pro 64-bit
• CPU: Intel Core i7-13700HX
• GPU: NVIDIA GeForce RTX 4050 Laptop GPU (6GB VRAM, Driver v565.90)
• RAM: 64 GB DDR5
• Compiler: MinGW-w64 GCC 15.2.0 (built with Ninja libs step)

Furthest point

In game

What is shown

• Booted past title screen, completed the initial tutorial stage, and verified the game autosaves state into the first hub/world phase.
• FPS: ~15–16 FPS at title screen; drops to sub-1 FPS (~0.26–0.41 FPS) during heavy texture swizzling/upload passes.
• Graphics: 3D rendering and gameplay visuals function correctly with complete asset loading.
• Audio: Functional, but audio drifts out of sync over time because video renders at roughly 1/4 real-time speed while audio streams normally.
• Input: Keyboard and controller inputs respond correctly.

Current blocker

• Vulkan Queue-Drain / Draw-Committer Overhead: Profiling via NVIDIA Nsight Systems & Nsight Graphics reveals the GPU spends 28.1% of execution time in "miscellaneous" stalls, sitting idle between ~72 small Vulkan submissions per frame.
• Forced Queue Drains: Nearly every compute job forces a full draw-queue drain (~9,600 drains / 10s) inside DrawPipeline.cpp:185.
• Issue link: Related to write-watch / memory page-fault tracking overhead on Windows (Windows: resuming a write fault overwrites the guest red zone when AVX state is live #361 / Astro Bot (PPSA21564) #357).

How it was run

Required Directory Structure & Config Links

To force Product Mode and prevent the engine from falling back to developer build paths (/host/%ASOBI_ROOT%/...), the root runtime folder requires links/junctions to the dump metadata:

mklink app0\args.txt "D:\ps5 game\astro\PPSA21567-app\args.txt"
mklink app0\debuginfo.txt "D:\ps5 game\astro\PPSA21567-app\debuginfo.txt"
mklink app0\param.sfx "D:\ps5 game\astro\PPSA21567-app\param.sfx"

 Project Launch & Relinker Guide

Welcome! Follow this quick step-by-step guide to run the relinker and launch the application seamlessly.

Configuration Arguments (args.txt)

Save the following flags into your args.txt configuration file:

-package -sequence product -mode product -odxBinary -perfDisplay false -debugDisplay false -debugInput false


 Getting Started

Run the following commands in PowerShell:

Step 1: Relink the Source

First, execute the relinker with your source paths:

.\relinker.exe --windows --registry --sce-module-path "D:/AnyPS5/_source_AstroBot" "D:/AnyPS5/_source_AstroBot/input_unwrapped.elf" app.exe


Step 2: Launch the App

Run a clean baseline launch of the application:

# Clean baseline launch
.\app.exe