HWBOT 3DMark03 Benchmark Validation Regulations

  • Uncategorized
  • 0

HWBOT 3DMark03 Benchmark Validation Regulations

HWBOT 3DMark03 Benchmark Validation Regulations

Allowed versionsAll versions
Allowed operating systems
Default benchmark settingsAs defined by benchmark
Allowed optimisations
  • Disable subtests

  • Driver settings finetuning
Disallowed tweaks/cheats
  • Mipmap

  • Lucid Virtu
  • Any software or human interaction altering the perceived speed of the benchmark program, tricking it to believe it ran faster
  • Wireframe hacks: any software or driver causing a benchmark program not (properly) render the textures
  • Rendered image differs too much from the original due to other software tweaking
Verification screenshot requirements
  • 3Dmark03 benchmark settings

  • 3DMark03 overall score
  • 3DMark03 subtest scores
  • CPU-Z CPU tab
  • CPU-Z Memory tab
  • CPU-Z Mainboard tab, if IGP has been used
  • GPU-Z Graphics Card tab (Rivatuner may be used if GPU-Z fails to correctly report the GPU)
Verification linkN/A
Verification datafileN/A
Example screenshot

Additional notes

This page contains the benchmark result regulation specifications for a specific benchmark. The rules as described in our General Rules section are still applicable even if they are not specifically mentioned on this page.

It is your responsibility, and the responsibility of your team captain(s) that these rules are followed properly. Your submission may be blocked by hwbot crew without notice if your submission is in violation of one of these rules. Multiple infractions may lead to a warning, and eventually an account ban.

  • May 15, 2008: Initial draw