Readiness methodology & data standards

Relative model v1.0.0

This model assigns broad component classes by editorial judgment. It uses no GTA VI benchmarks and predicts no frame rate. Confidence stays low until official PC specifications and independent tests exist.

Version 1.0.0 introduces the editorial class model on October 2, 2026. It does not use measured comparable-game performance. It gives rough relative planning context, not purchasing advice or a compatibility test.

Score formula

Each known CPU and GPU class runs from 1 to 4. Multiplying a class by 25 gives a component index. Unknown hardware produces no overall score. The selected build must have a known CPU, GPU and storage type plus a positive free-capacity value.

score = clamp(round(0.30 × CPU + 0.45 × GPU + 0.15 × memory + 0.10 × storage − target penalties), 0, 100)

The 200 GB threshold is arbitrary free-space planning headroom. It predicts no download or install size. Target penalties express increasing demand in this model; they are not measured scaling factors.

Readiness bands

0–39: upgrade may be needed. 40–59: likely demanding. 60–79: some relative headroom. 80–100: strong relative class. Scores are ordinal planning context and are not probabilities, percentage compatibility or predicted FPS.

Component class assignments

These groupings are editorial assumptions. Models sharing a class are not exact equivalents; VRAM, CPU cache, power limits and actual game workloads can change rankings. Unlisted hardware remains unknown.

Catalog revision 1.1.0 has 35 desktop CPUs and 43 desktop GPUs, plus ten RAM capacities. Every classification is labeled editorial; all Phase 1 IDs, class assignments, weights, penalties and score boundaries remain unchanged. Mobile GPUs, integrated graphics and unlisted parts remain unknown.

Classes 1–4 are broad editorial bins for entry / older, mainstream, higher mainstream and upper relative hardware. They do not measure GTA VI performance or establish precise cross-brand equivalents. Product names can be checked in the AMD processor catalog, AMD graphics catalog, Intel Core catalog, Intel Arc hardware guide and NVIDIA comparison catalog. These sources establish product identity; OpenWorldKit assigns the classes.

Advisor, comparison and storage planning

Both new PC tools reuse the same scoring engine. Upgrade priority orders unknown components first, then known components by their weighted gap to index 100. Ties use GPU, CPU, memory, then storage. The strongest component uses the highest known component index. When all indices are maximum, no component constraint is identified. Category advantages compare component indices before target penalties; choose equal goals to compare hardware fairly.

The storage planner subtracts the existing 200 GB planning budget and a user-selected buffer from current free capacity. Its suggested safety headroom is the greater of 20 GB or 10% of drive capacity, rounded up. Both rules are editorial assumptions and predict no official install size or patch requirement.

Phase 1.5 changes catalog coverage and utility outputs only. Scoring remains v1.0.0; the original versioned PC record needs no migration. Named-build storage accepts raw records and v0/v1 envelopes, including legacy pc fields, then writes the v1 shape on explicit save. Invalid or future-version records return safely to defaults.

Confidence & future revisions

Confidence is low for every pre-benchmark result. Official requirements can inform a future model version; real PC benchmarks would be needed for measured performance claims. Versioned assumptions make changes inspectable. We do not imply any published forecast is Rockstar-approved.

Evidence standards

Official requires a publisher or platform source. Verified requires primary evidence; repeated fan claims do not suffice. Community data keeps its status until reviewed. Estimates stay estimates. Unknown means the registry has no supported value.

Future measurements should record the source, platform, edition, date and method. A concept map uses percentages of a neutral drawing, not game coordinates; routes connect selected markers in order without optimization claims.

Review or report an assumption

Use the checker · Inspect the source registry · Prepare a correction report