Resonance: A Plague Tale Legacy PC Benchmark Methodology
Evidence note: launch-dependent details remain marked Retail verification required.
Updated: August 24, 2026
Status: Pre-release methodology — Retail verification required
Short answer
A trustworthy Resonance: A Plague Tale Legacy PC benchmark must report more than an average FPS number. It should identify the retail build, hardware, resolution, preset, upscaling, display features, test scene, repeat count, frame-time behavior, and meaningful lows.
The official Steam targets—1080p/30 on Low for minimum hardware and 1080p/60 on Ultra for recommended hardware—are useful reference points, but they are not a substitute for reproducible testing. Retail verification required.
Record the complete test system
Every result should list:
- CPU model and power settings;
- GPU model and VRAM;
- System RAM;
- Storage drive and free space;
- Operating system;
- Driver version;
- Game build and patch;
- Cooling or fan profile;
- Display resolution and refresh rate.
For a handheld, also record the device model, TDP or power profile, battery level, operating system, screen refresh rate, and whether the test is plugged in. Retail verification required for the final telemetry tools and acceptable reporting thresholds.
Keep graphics variables controlled
A useful comparison changes one major variable at a time. Record:
- Resolution and display mode;
- Low, Medium, High, or Ultra preset as displayed in-game;
- Texture, shadow, lighting, effects, and volumetric options;
- Upscaling and frame-generation mode;
- Ray tracing state;
- HDR and VRR state;
- Frame-rate cap and V-Sync state.
Do not compare one GPU at native 1440p with another GPU using an undisclosed upscaler. The final menu names and feature availability are Retail verification required.
Choose repeatable test scenes
At minimum, test more than one type of workload:
1. A traversal route with new assets loading;
2. A combat encounter with several active enemies;
3. A light-based puzzle or visually complex mechanism;
4. A transition between historical eras or major environments;
5. A dense outdoor or architectural scene.
The exact locations and repeatable benchmark routes must be selected from the retail game. Retail verification required.
Warm up and repeat the run
Run the scene once as a warm-up, then repeat it under the same conditions. Note whether the first run differs because of shader compilation, asset streaming, or caching. Use multiple passes rather than publishing the fastest single result.
If a hitch occurs, record where it happened and whether it repeats. A brief average-FPS result can hide serious frame-time spikes.
Report FPS and frame times together
A useful result should include:
- Average FPS;
- Meaningful low-percentile result, such as a 1% low where the capture method supports it;
- Frame-time graph or stutter notes;
- Resolution and preset;
- Upscaling and frame-generation state;
- Test scene and run duration.
Do not call a result “smooth” from the average FPS alone. Input feel and traversal consistency may differ even when two systems share the same average.
Interpret the bottleneck carefully
Use monitoring data and controlled setting changes to distinguish:
- GPU-bound: lowering resolution or GPU-heavy settings materially improves performance;
- CPU-bound: lowering resolution changes little while CPU activity or simulation pressure remains high;
- Streaming or I/O issue: hitches cluster around new areas or asset transitions and do not behave like a steady GPU limit;
- Frame-pacing issue: average FPS looks acceptable but frame times contain repeated spikes.
These are diagnostic categories, not confirmed Resonance causes. Retail verification required for any game-specific bottleneck conclusion.
Benchmark reporting template
Common benchmark mistakes
- Mixing preview and retail builds;
- Hiding the upscaling mode;
- Comparing different patches;
- Reporting only the best run;
- Calling estimated calculators “benchmarks”;
- Ignoring CPU limits at 1080p;
- Testing only an early quiet area;
- Omitting frame times and stutter;
- Treating official requirements as measured performance.
Retail verification checklist
After release, verify:
- Final PC settings and feature names;
- Repeatable benchmark routes;
- Retail patches and drivers;
- CPU/GPU scaling at 1080p, 1440p, and 4K;
- Upscaling and frame-generation behavior;
- Frame times during traversal, combat, puzzles, and timeline transitions;
- Handheld power, battery, temperature, and stability;
- Known stutter, crash, and display issues.
Every game-specific result is Retail verification required until measured on the retail build.
Bottom line
Measure Resonance with controlled hardware, settings, scenes, and repeat runs, and report frame times alongside FPS. The official 1080p targets provide context, but they cannot answer 1440p, 4K, handheld, or setting-specific questions. Reproducible retail testing is Retail verification required.