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.
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.
1% low estimate: -- FPS · Native frame estimate.
- Limiting component
- Calculating…
- Ceiling spread
- --
- Frame path
- Native planning baseline
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.
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.
Installed: -- · Headroom: -- · Utilisation: --
- Recommended texture pool
- --
- Shader cache disk suggestion
- --
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.
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.
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.
Calculating… 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.
Crash log & mod conflict analyzer
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.
How the models think
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.
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.
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.