01At a glance
- Method
- x86-64 translation + Vulkan 1.3 renderer
- CPU floor
- AVX2 required, no fallback
- GPU floor
- Vulkan 1.3 with current drivers
- Cache
- Per-title pipeline cache, first run warms
02What lives here
Reference explains the machinery behind the ratings. Start with How it works for the translation model, then the three acceptance gates: Vulkan check, CPU and AVX2, and Shader cache.
Every Library rating assumes these gates pass. A title that misbehaves on a machine failing any gate is not a counterexample — it is an untested configuration.
The free build at Download Meridian runs the same checks the lab runs; there is no separate lab binary.
03How to use this shelf
- Read How it works once for vocabulary: translation, PUP, SPIR-V, pipeline.
- Run the Vulkan and CPU checks before reporting any defect.
- Learn the shader-cache warm-up pattern so first-run hitches are not misreported as bugs.
04Questions
Q.01Is Meridian an interpreter?
No. It translates PS5 x86-64 code and renders through Vulkan 1.3 — see How it works.
Q.02Why is AVX2 mandatory?
The translation layer emits AVX2 throughout hot paths. Without it there is no fallback — see CPU and AVX2.
Q.03Do I need to understand SPIR-V?
Only the RDNA2-to-SPIR-V mapping at a high level. Details are in RDNA2 and SPIR-V.