a) vid_soft is disqualified at ultra and above for lack of support of: offsetmapping, reliefmapping, postprocessing
b) the OpenGL 1.x renderer is disqualified at normal and above for lack of support of: deluxemapping, gloss, offsetmapping, reliefmapping, postprocessing
Benchmark results :
How to run the benchmark
First turn off any screen savers you may be running.
Then, in misc/tools/the-big-benchmark/, run the-big-benchmark.sh or the-big-benchmark.bat depending on OS. Wait for about 1 hour, then - if it’s not done yet - you are allowed to quit the process by entering “quit” on the game console. The results will be saved in data/the-big-benchmark.log. Upload this file, and analyze it and enter the values here!
The lists are sorted by the “normal” column in descending order, where a - (test not been done due to taking too long) is still better than a disqualification. In case of equality, further sort criteria are chosen to the left.
The fields have the following meanings and are extracted as follows:
The user name on the tracker here.
A host identifier (e.g. host name)
The CPU in the system. On Linux, get this from /proc/cpuinfo.
The CPU clock frequency.
The number of CPU cores in the system. On Linux, get this from /proc/cpuinfo.
The total physical memory of the system. On Linux, get this from free.
The vendor string (typically graphics card vendor). Get this from the-big-benchmark.log, as in:
GL_VENDOR: NVIDIA Corporation
The renderer string (typically graphics card name). Get this from the-big-benchmark.log, as in:
GL_RENDERER: GeForce GTS 250/PCI/SSE2
Sometimes this just lists the series of the chipset, and not the exact chipset number. In that case, please write the proper chipset number in the Notes column!
The version string (typically driver version). Get this from the-big-benchmark.log, as in:
GL_VERSION: 3.3.0 NVIDIA 290.10
The operating system. One of Windows XP, Vista, Windows 7, Linux, OS X 10.5, OS X 10.6, OS X 10.7.
The operating system architecture. Typically one of x86, x64.
Special notes for the run.
omg, low, med, normal, high, ultra, ultimate
In this order, the integer part (part before the . - yes, we round downwards) from the fps number from the MED: lines of the-big-benchmark.log. For example, the following lines:
If a run was not made (you then have less MED: lines), or if a run was incomplete for some reason (then the corresponding MIN: line does not show the same frame count as MAX:), a dash (“-”) is to be entered.
Differences to normal test environment (e.g. different resolution than the intended resolution of the test, which is 1024x768), or problems that happened during the test.