HWBOT Unigine Heaven Basic Benchmark Validation Regulations

  • Benchmark Rules
  • 2
  • HWBOT

HWBOT Unigine Heaven Basic Benchmark Validation Regulations

Allowed benchmark versions
Allowed operating systems
Default benchmark settingsBasic Preset: DX9, 1280×1024,
ScoreThe score is obtained after running the Basic preset.
Allowed optimisations
  • LOD
Disallowed tweaks/cheats
  • Altering benchmark files or the rendering
  • Any software or human interaction altering the perceived speed of the benchmark program, tricking it to believe it ran faster
  • Lucid Virtu MVP
  • Mipmap
  • Change benchmark settings
Verification screenshot requirementsThe screenshot must be obtained using the integrated screenshot functionality

Verification datafileVerification datafile is mandatory
Example screenshot

Red: Mandatory Green: Optional

Additional notesThis page contains the benchmark result regulation specifications for Unigine Heaven – Basic. 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 moderators 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.

Changelog

Christian Ney says:

Reserved for tweaks and tips

 

- If you get the time format error, set the format to "English (UK)" in Windows' Region and Language

- Audio must be enabled

- There are a couple of "FPS drops" when you run it for the first time.

Poland ADVenturePO says:

If You have encountered @Luumi wrote on ROGs page: "Thanks to Dartmaul I sorted out the problem with HWBOT Unigine. So for all you who are getting run-time errors try this: Open Region and Language format (Control panel > Clock language and region > Region and Language > Format > Additional settings) and set "Decimal symbol" to "." (dot)." I'm from Poland and there was a coma "," in the setting. It solved my problem with this Benchmark. Cheers.

Please log in or register to comment.