# Check your setup before you convert

A build checklist and a runtime checklist answer different questions. First decide whether you are using a published build or compiling the project yourself.

Canonical: https://anyps5.fun/requirements/
Documentation reviewed: 2026-10-14

## Runtime preparation

The reviewed usage document selects a Vulkan 1.1 device with graphics, compute and presentation support. That is a documented selection rule, not a guarantee that every game or driver will work.

| Record | Why it matters |
| --- | --- |
| CPU model and architecture | Identifies the host, rather than a vague “gaming PC” |
| GPU and driver version | Makes graphics-related reports comparable |
| OS version | Separates host-specific failures |
| AnyPS5 release or commit | Connects a result to an exact implementation |

Keep this information beside your logs. If you try another machine, record its details separately instead of overwriting the first result.

## Building is a separate task

The full-build document lists an x86-64 host, Git, CMake 3.22.1 or newer, Ninja and a C++20 toolchain. Platform-specific dependencies also apply. Use the build guide to choose the correct mode.

Installing a compiler is useful only if you intend to compile. For a published build, begin by identifying the available assets and their target platform.

## Investigate the actual memory error

Upstream explains that Windows direct-memory allocation can charge the system commit limit. Read the exact allocation failure and inspect commit usage; installed RAM alone does not describe that situation.

Our recommendation: record current usage and the failing allocation before changing system settings. Keep the value in its original unit. Do not turn one title’s report into a universal RAM requirement.

## Plan a small first test

- Use a specific input and build you can identify.
- Pick an observable endpoint, such as reaching a particular screen.
- Allow time to collect logs, rather than assuming a one-click setup.
- For Steam Deck, laptops or another platform, seek a report for that exact environment.

We do not publish a minimum GPU model, recommended FPS or universal RAM figure because this guide has not established those measurements.

## Common questions

### Can I use a generic PC specification as proof of compatibility?

No. A useful report identifies the title, build, driver and stage reached on that particular setup.

## Sources

- [Relinker usage](https://github.com/boykopovar/AnyPS5/blob/main/docs/user/USAGE.md) — reviewed 2026-10-14
- [Build instructions](https://github.com/boykopovar/AnyPS5/blob/main/docs/dev/BUILD.md) — reviewed 2026-10-14
- [Technical debt](https://github.com/boykopovar/AnyPS5/blob/main/docs/dev/TechnicalDebt.md) — reviewed 2026-10-14