Question 1

First answer

Accepted Answer

These are dated implementation snapshots of declared library functions and recognized decoder instructions — not a playable-game rate. Throwing or newly declared functions can raise the denominator while the implemented count stays flat or rises slower, so the percentage can fall even when more functions are implemented. One missing API, shader, or sync path can still block a title. 100% shaders means every name on the project’s declared RDNA instruction list is recognized by the decoder; it does not mean a given game works. Check the title page, the compatibility snapshot, and live Game bring-up discussions.

Question 2

What the counters measure

Accepted Answer

The library percentage is implemented functions divided by functions declared in core/libs/prx — the set known to the project so far, not every PS5 system function. README states that the total grows as more functions are declared. tools/progress.py counts an APS5_VABI export as implemented when its body does not call the NotImplemented_nid_no_patch stub path, and as pending when it does. The shader percentage is recognized decoder instructions divided by the AMD RDNA 1 + RDNA 2 names in tools/rdna_isa.txt. Official history.html uses that list as the shader total. progress.json can also list extra decoder opcode names outside that ISA set; those extras are not the 1166-name denominator. Neither counter is a title compatibility rate, a Playable verdict, or a finished-game claim. They do not count how many games boot, reach gameplay, or complete. This site’s homepage already states that even 100% is not a playable-game rate, and that the denominator is the upstream declared shader and library set. On the 22 Oct 2026 snapshot, shaders are 1166/1166 (100%). That is decoder coverage of the declared ISA list. It is not a claim that a title’s shaders compile, present, or play on a host.

Question 3

Why a lower percentage can accompany more implemented functions

Accepted Answer

The percentage is implemented divided by declared. Adding throwing declarations raises the denominator without raising the implemented count, so the percentage can fall while more functions exist as real implementations. The mechanism is the growing declared set, not a claim about how often any one title hits a missing export. Official history.html records one UTC-day point from the last commit on main that day, remade with current tools/progress.py rules. On 18 Oct 2026 the library counter was 3683 implemented of 4029 declared (91.41%). On 21 Oct 2026 it was 4670 of 11032 (42.33%). Implemented functions rose; the declared total rose faster. The same series on 22 Oct 2026 records 4834 of 11181 (43.23%). This site’s synced snapshot is libs 4834/11181 (43.23%) and shaders 1166/1166 (100%). Open the live files if you need a later day. Merged declaration-expansion pull requests add throwing stubs without raising the implemented count. PR #8431 (merged 21 Oct 2026) declared 139 PS5 3.20 exports as NotImplemented_nid_no_patch; its progress comment recorded +139 declared functions and a lower percentage, with the implemented count unchanged relative to its base. PR #9003 (merged 21 Oct 2026) declared 150 pending libSceNpManager exports the same way. Those two PRs illustrate the mechanism; they are not the whole 18–21 Oct denominator change.

Question 4

Use a game report for a game question

Accepted Answer

Ask whether a title boots, reaches menus, or plays on the compatibility snapshot and the title page. Per-game stage, open blockers, and host notes live there and in live Game bring-up threads — one thread per title. The FAQ covers what Playable and In-game mean on this site. A high project percentage does not upgrade a title. A window is not Playable. Leave missing host or save fields empty. Do not copy another report’s stage.

What the counters measure — and why the percentage can fall