Starting the TimeDemo

As explained on the previous page, timedemo is run via the command line (and through Windows shortcuts). The following are some example Timedemo commands used to run the benchmark on Neoseeker's Nvidia FX5950 Review:

"C:\Program Files\Microsoft Games\Halo\halo.exe" ?use20 -width1024 ?nosound

"C:\Program Files\Microsoft Games\Halo\halo.exe" ?use20 -width1600 ?nosound

"C:\Program Files\Microsoft Games\Halo\halo.exe" ?use14 -width1024 ?nosound

"C:\Program Files\Microsoft Games\Halo\halo.exe" ?use14 -width1600 ?nosound

The above will run timedemo in 1024x768 and 1600x1200 resolutions using Pixel 2.0 and Pixel 1.1 - You can set up batch files to loop through multiple timedemos (ie testing 3 resolutions) because the results are all appended to a file after the benchmark is run.

Unlike the traditional timedemos of Quake, the Halo timedemo is not a recorded path of the player?s movements. Instead it renders four of the game?s cutscenes; upon the completion, Halo will exit to Windows.

Interpreting the Results

Timedemo information is saved in timedemo.txt located in the Halo directory. New entries are appended to the end of the file so previous timedemo data will not be overwritten.

A sample of a timedemo run follows ?

Date / Time: 31/10/2003 1:57:51 PM (230435921ms)
2200MHz, 512MB, 64M nVidia GeForce3 Ti200 (DeviceID="0x0201)" Driver="6.14.10.4523"
Shader="1.1"
D:\games\halo\halo.exe -timedemo (Version="1.0.2.581)"
Frames="4700"
Total Time="125.41s"
Average frame rate="37.48fps"
Below 5fps= 11% (time) 0% (frames) (14.414s spent in 14 frames)
Below 10fps= 11% (time) 0% (frames)
Below 15fps= 12% (time) 0% (frames)
Below 20fps= 13% (time) 0% (frames)
Below 25fps= 20% (time) 5% (frames)
Below 30fps= 36% (time) 16% (frames)
Below 40fps= 58% (time) 37% (frames)
Below 50fps= 75% (time) 58% (frames)
Below 60fps= 90% (time) 78% (frames)
###Sound Options###
Hardware Acceleration= Yes
Sound Quality= High
Environmental Sound= EAX
Sound Variety= High
###Video Options###
Resolution= 640 x 480
Refresh rate= 150 Hz
Framerate throttle= No Vsync
Specular= Yes
Shadows= Yes
Decals= Yes
Particles= Off
Texture Quality= High

There is a lot of information to be gleaned from this. The second line shows the hardware Halo is being run on, in this case a 2200 MHz CPU with 512 MB of system memory and a 64 MB GF3 Ti200. The third line shows the driver revision and the rendering path. That is the 45.23 series from nVidia running PS 1.1 The number of frames rendered is always 4700 in Halo but the time it takes varies. Something unique about Halo benchmarks is the inclusion of histogram data, a feature that will hopefully make it into all games. From the sample here, the framerates are fairly evenly distributed as far as highs and lows go. Being mainly between 30 and 40 fps shows some stability in framerates as fluctuations are distracting in games. However the occasional dips may be unacceptable to those who play multiplayer seriously so a change to a lower quality rendering path or toning done some of the visuals may be needed.