---
title: Compatibility methodology — how ratings are earned | Meridian
description: Meridian's normative rating procedure: reference rig, cache warm-up, session scope, evidence, and promotion thresholds.
canonical: https://ps5emulatorwindows.com/log/compatibility-methodology
updated: 2026-10-13
---

# Compatibility methodology

Reference rig, warmed cache, full sessions, recorded evidence. Promotions need repeats.

## Facts (2026-10-13)

- **Rig:** Reference hardware per /hardware
- **Warm-up:** Same route twice; second is measured
- **Evidence:** Build + firmware + driver recorded
- **Promotion:** Repeated clean runs, never one

## Promotion thresholds

| From | To | Requires |
| --- | --- | --- |
| Test | Beta | Repeated end-to-end runs with documented workarounds |
| Beta | Stable | Repeated full sessions at defaults, no blockers |
| Any | Drop | One confirmed regression on re-verification |

## Normative procedure

1. Fix the rig: reference hardware per [Minimum and recommended](/hardware/minimum-recommended), current drivers, passing [Vulkan check](/reference/vulkan-check) and AVX2 probe.

2. Fix the software: build from [Download Meridian](/download), official PS5UPDATE.PUP via File then Install Firmware, owned dump indexed per [Index your library](/protocol/index-your-library).

3. Warm the cache: run the same route, lap, or sortie twice. The second pass is the measurement — see [Shader cache](/reference/shader-cache).

4. Run the session: full sessions for Stable candidacy, end-to-end with notes for Beta, menus plus early gameplay for Test — per [Status definitions](/compat/status-definitions).

5. Record evidence: build number, firmware version, GPU driver, settings, and observed defects. Without evidence the run did not happen.

## Promotion and regression rules

- Promotion requires repeated clean runs across sessions, not one good evening. Single runs promote nothing.

- Regression on re-verification drops the rating immediately and is recorded with the causing build.

- Ratings never transfer across builds silently. Each build re-verifies the [Stable titles](/compat/stable-titles) leaders first.

- Own your library: method runs use owned dumps only. 400+ titles indexed; each earns its rating separately.

## FAQ

### How many runs promote a title?

Multiple clean sessions under identical conditions. One clean run is a candidate, never a promotion.

### What evidence must a report include?

Build number, firmware version, GPU driver, settings, and warmed-cache runs. Missing any, unactionable.

### Do faster rigs earn faster promotions?

No. Ratings follow the reference rig so results compare across users and builds.

## Related

- [Log](https://ps5emulatorwindows.com/log)
- [Status definitions](https://ps5emulatorwindows.com/compat/status-definitions)
- [Stable titles](https://ps5emulatorwindows.com/compat/stable-titles)
- [Shader cache](https://ps5emulatorwindows.com/reference/shader-cache)
- [Minimum and recommended](https://ps5emulatorwindows.com/hardware/minimum-recommended)

## Download

Free Windows app: [Download Meridian](https://ps5emulatorwindows.com/download)

Markdown mirror: https://ps5emulatorwindows.com/log/compatibility-methodology.md