Field tools / locally computed

Tune the machine. Not the mystique.

Three deterministic tools for the questions that pre-roll every upgrade: where is the bottleneck, how much VRAM does the profile really need, and which launch flags are defensible? A fourth reads your crash log and points at the filed fix.

Tool 01 / planning model

Bottleneck & FPS estimator

A quick sanity check before spending money. The model estimates a CPU ceiling and a GPU render load, then shows which one arrives first. Resolution, preset, upscaling, and frame generation are accounted for separately.

CPU ceiling is modelled from a single-threaded game-load index. GPU load is modelled at native 1440p ultra, then adjusted for your selections. It is deliberately conservative: the model does not know your CPU cooler, memory timings, or the game's own scheduler.

Estimated native average MODEL v1.0
-- FPS

1% low estimate: -- FPS · Native frame estimate.

CPU ceiling --
GPU render ceiling --
Limiting component
Calculating…
Ceiling spread
--
Frame path
Native planning baseline
Read this before upgrading Calculating a measured starting point…

Heuristic only. Real bottlenecks move with scene density, driver version, CPU boost behaviour, and the game's own engine limits. Use PresentMon or CapFrameX to verify.

Tool 02 / memory planning

VRAM & shader cache budget

Texture packs, ray tracing, frame generation, and big open worlds all spend the same VRAM. Set the scene profile and check the headroom before enabling a preset that spills into shared memory.

The reserve includes desktop composition and driver overhead. Shader cache is a disk allocation, not VRAM; the two numbers are reported separately because conflating them is how bad “optimisation” packs happen.

Estimated scene demand Calculating…
-- / installed

Installed: -- · Headroom: -- · Utilisation: --

VRAM pressure Keep below 100%
Recommended texture pool
--
Shader cache disk suggestion
--
Budget note Calculating memory headroom…
GENERATED PROFILE / PLAIN TEXT
Calculating…

Estimates assume a 1440p-class texture working set, a modern driver, and no third-party HD texture stack. Actual allocations vary by title and scene. Check GPU memory in PresentMon or the game's own budget meter.

Tool 03 / conservative flags

Engine launch flag generator

Build a short Steam launch-options string with only documented, low-risk flags. No memory-pool incantations, no undocumented DLL tricks, no “magic” flags that quietly break anti-cheat.

Only auto-appended for Source 2. Other engines should use their own limiter.

Use the API selector for one API at a time. If a flag triggers a crash, a launcher integrity check, or an anti-cheat warning, remove it immediately. Borderless flags may reset when a game switches display mode.

Steam launch options
STEAM → GAME → PROPERTIES → LAUNCH OPTIONS
Calculating…
Flag notes Calculating conservative flags…

Anti-cheat safety first. GamePathHub does not recommend bypasses, unsigned DLL injection, or launch flags that disable integrity checks. Verify each flag against the game's own documentation or the engine vendor before use.

Field tool / offline matcher

Crash log & mod conflict analyzer

LOCAL / NO UPLOAD

Paste the last 40 lines of a crash report, launcher error, or mod manager log. The matcher looks for known signatures and links the filed guide that covers the same failure.

No diagnostics yet. Paste a log and run the matcher — all matching happens inside this tab.

Methodology

How the models think

01

CPU ceiling first

CPU load is dominated by simulation, draw-call submission, and game logic. The tool gives the CPU a fixed ceiling and then asks whether the GPU can render faster than that. Resolution changes rarely lift a CPU bottleneck.

02

VRAM is a budget, not a badge

A 16 GB card can still spill when textures, RT structures, and frame generation compete. The calculator starts with a desktop reserve, then adds cost for resolution, texture class, ray tracing, scene profile, and frame generation.

03

Launch flags are a scalpel

Each flag must earn its place. The builder restricts output to flags with a clear, documented purpose and tells you when a selected engine ignores or rejects one. If in doubt, leave Steam's field empty.

Need a fix rather than a forecast? Start with the game directory or read the test bench methodology.

Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.