Editorial methodology

1. Physical testing

Nexus Gaming does not currently operate a hardware lab. No page may claim hands-on testing unless it names the tester, hardware, game version, scene, settings, measurement tool, run count and date. The current PC assistant contains no Nexus Gaming physical benchmark.

2. Data comparisons

We compare publisher requirements, manufacturer specifications and clearly attributed published measurements. A requirements match is a compatibility-oriented recommendation, not proof of a frame rate.

3. Specification sources

GPU memory, architecture and product capabilities come from official NVIDIA or AMD pages. Game requirements come from the publisher or its official store listing. A source URL and access date are stored with the data.

4. Benchmark sources

A performance result is displayed only when game, GPU, CPU, resolution, settings, ray tracing, upscaling, date, method and source are known. Manufacturer measurements are labelled as such and are not presented as independent Nexus Gaming tests.

5. FPS ranges and confidence

We do not derive a range from a compatibility requirement. Published averages remain labelled as single published averages. A future range will require several documented runs or compatible sources; confidence depends on protocol completeness, recency and applicability to the selected hardware.

6. Ratings

No opaque expert, press or consumer score enters the PC recommendation. A retailer rating is allowed only with its retailer source, retrieval date and genuine count supplied by that source. No review count is inferred.

7. Prices

Component amounts in builds are editorial budget allocations. A retailer price is shown only with merchant, nature, retrieval timestamp and availability when known. The retailer price at click time remains authoritative.

8. Update frequency

Sources and transactional pages are reviewed after a material game, driver or product change and at least once per quarter. Timestamped retailer data follows the cache duration shown by the interface.

9. Use of AI

AI may assist code, translation checks, inventory and draft structuring. It may not create a benchmark, source, author identity, review count or price. Editorially significant claims must remain traceable to stored data and named sources.

10. Corrections and affiliation

Readers can report an error by email. Material corrections are dated on the relevant page and central log. Affiliate availability and commission rates never affect technical eligibility or ordering.