Windows
No reviewed run report for this platform. The result remains unknown.
Back to gamesSource-reported 
Source-reported Locally modified
PPSA02629 / Action adventure
Trek To Yomi
Trek To Yomi · PPSA02629 on AnyPS5. Windows: No reviewed report; Linux: Startup / Gameplay (Locally modified). Check the PS5 edition, build, patches and original evidence before testing.
PS5 title ID PPSA02629. Match this ID to your edition, then compare the content version, operating system, build and patches in each report. A matching ID alone does not establish compatibility.
Results by platform
An editorial selection of scoped reports, not a guarantee for the latest build. Read the evidence before choosing your setup.
Linux
ReviewedStartup
With unlisted PlayGo chunks installed, allocation fails before a window; marking them absent reaches the opening cutscene. Later non-profiled tests distinguish about 8 FPS cutscene from 2.2 FPS combat tutorial; profiler overhead invalidates earlier speed comparisons.
AnyPS5 buildmain 474030e584
Reports behind this summary · Community reportGameplay · Locally modified
Non-profiled main plus pad-type-only #10935 reaches the combat-movement tutorial at median 2.2 FPS versus 8.3 in cutscene. Later traces identify memory-budget pressure, but cache-policy and staging-switch experiments establish no fix or speed gain.
AnyPS5 buildmain f06d7fdcee + #10935 (scePadOpen types 3/4 only); PlayGo absent
Reports behind this summary · Community reportAbout the game
The combat tutorial exposes different memory and GPU costs from the opening movie; profiler overhead must stay visible in comparisons.
Which edition does this cover?
Official artwork, when available, describes the game and may cover another region or generation. It does not identify the tested PPSA, DLC or AnyPS5 output.
Official game informationEdition and evidence review
This review covers the upstream documentation, public issues, pull requests and discussions, alongside publisher information. It is a source review, not a game test by this site. A missing report does not establish incompatibility.
Sources checked ·
What the sources establish
With unlisted PlayGo chunks installed, allocation fails before a window; marking them absent reaches the opening cutscene. Later non-profiled tests distinguish about 8 FPS cutscene from 2.2 FPS combat tutorial; profiler overhead invalidates earlier speed comparisons. Non-profiled main plus pad-type-only #10935 reaches the combat-movement tutorial at median 2.2 FPS versus 8.3 in cutscene. Later traces identify memory-budget pressure, but cache-policy and staging-switch experiments establish no fix or speed gain.
What a new test needs to establish
Reproduce the exact package/build/patches and scene. Verify controls, audio, reload and longer play independently; missing hardware, driver or test dates stay unknown. A stopped process, a present counter or an import audit is not a complete game test.
Community report · Linux
Startup
With unlisted PlayGo chunks installed, allocation fails before a window; marking them absent reaches the opening cutscene. Later non-profiled tests distinguish about 8 FPS cutscene from 2.2 FPS combat tutorial; profiler overhead invalidates earlier speed comparisons.
- AnyPS5 build
- main 474030e584
- Platform
- Arch Linux 7.2.11 Release
- Game version
- Not specified
- CPU
- AMD Ryzen 9 7950X
- GPU
- AMD Radeon RX 6650 XT
- Driver
- RADV Mesa 26.2.6
- Test date
- Not specified
Performance observations
The source does not provide an FPS measurement tied to specific hardware.
Scope of this result
With unlisted PlayGo chunks installed, allocation fails before a window; marking them absent reaches the opening cutscene. Later non-profiled tests distinguish about 8 FPS cutscene from 2.2 FPS combat tutorial; profiler overhead invalidates earlier speed comparisons.
Results come from the original reports; this site has not reproduced the tests. The stage shown is the furthest point reported, not a guarantee of stable play. Locally modified results may rely on forks, patches or changes to game files.
Open original sourceSource last updated
Community report · Linux
Gameplay
Non-profiled main plus pad-type-only #10935 reaches the combat-movement tutorial at median 2.2 FPS versus 8.3 in cutscene. Later traces identify memory-budget pressure, but cache-policy and staging-switch experiments establish no fix or speed gain.
- AnyPS5 build
- main f06d7fdcee + #10935 (scePadOpen types 3/4 only); PlayGo absent
- Platform
- Arch Linux 7.2.11 Release
- Game version
- Not specified
- CPU
- AMD Ryzen 9 7950X
- GPU
- AMD Radeon RX 6650 XT
- Driver
- RADV Mesa 26.2.6
- Test date
- Not specified
Performance observations
The source does not provide an FPS measurement tied to specific hardware.
Scope of this result
Non-profiled main plus pad-type-only #10935 reaches the combat-movement tutorial at median 2.2 FPS versus 8.3 in cutscene. Later traces identify memory-budget pressure, but cache-policy and staging-switch experiments establish no fix or speed gain.
Results come from the original reports; this site has not reproduced the tests. The stage shown is the furthest point reported, not a guarantee of stable play. Locally modified results may rely on forks, patches or changes to game files.
Open original sourceSource last updated
Game and edition
- Game
- Trek To Yomi
- Title ID
- PPSA02629
- Edition / region
- PS5 · PPSA02629
- Content versions in reports
- Not specified
These versions belong to individual reports, not every edition of the game. An unknown version remains unknown; demos, expansions and other PPSA editions need their own evidence.
Screenshots and video
Official game images
Promotional images from the publisher’s game page. These are not screenshots of the game running in AnyPS5. Images are hosted on this site; rights remain with their owners.
Official game informationResults come from the original reports; this site has not reproduced the tests.
Source policy · Read more
Prepare an AnyPS5 test
Record the PS5 title ID, game version, AnyPS5 commit and operating system. Note any local changes, then test startup, menus, gameplay, audio and saves separately. Attach the first relevant error and a short capture of the same build.