# AnyPS5 progress explained: shaders, libraries and playable games

Author: DecompHub
Updated: 2026-10-12
Language: en
Canonical: https://decomphub.com/guides/anyps5-progress-explained

AnyPS5 has several kinds of progress. A single completion percentage would hide the difference between recognizing an instruction, implementing a library function and running a game correctly.

The [official repository](https://github.com/boykopovar/AnyPS5) links to its [progress report](https://boykopovar.github.io/AnyPS5/) and [game compatibility documentation](https://github.com/boykopovar/AnyPS5/blob/main/docs/user/COMPATIBILITY.md). Those sources answer different questions and should be read together.

## System libraries

The library report counts functions already declared in the project. Its denominator is not every system function available on a PS5. The published counting rules explain how shared sources are counted and how a function leaves the unimplemented category.

That is an implementation indicator. A function with a body is not automatically a correct implementation under every game's calling pattern. A changing denominator can also reduce the percentage without erasing completed work.

## Shader instructions

The shader report uses a defined AMD RDNA instruction list. Under the publisher's counting rule, an instruction counts when the decoder recognizes it. Recognition is one stage of the graphics pipeline.

Translation into SPIR-V, correct behavior, rendering and game-specific requirements still need their own evidence. Reaching the end of a decoder progress bar does not establish that every shader renders correctly.

## What should a player check?

Use the compatibility documentation for the specific game, version and environment. A title reaching a menu, rendering a first scene and remaining playable through a session are distinct milestones. Check the report date and reproduction conditions before relying on a demonstration.

DecompHub's adapter reads the publisher's [structured report](https://boykopovar.github.io/AnyPS5/progress.json) and keeps library coverage and shader decoding on separate lines. It does not average them into “PS5 completion” or imply maintainer endorsement.

The same approach works for other projects with several subsystems. [Create a progress badge](/progress), or read [decompilation versus reimplementation](/guides/decompilation-reimplementation-recompilation) to understand the different project goals.