UT2003 - Flyby

Here we'll look at the Flyby element of the UT2003 benchmark demos on the Parhelia.




FPS 640x480 800x600 1024x768 1280x960 1600x1200
1.0.0.233 143.9 120.6 98.5 66.9 48.6
1.2.0.42 170.6 153.2 111.4 76.1 51.2
 
Difference 640x480 800x600 1024x768 1280x960 1600x1200
FPS 26.8 32.6 13.0 9.2 2.6
% 19% 27% 13% 14% 5%

As with the Botmatch element of the UT2003 benchmark we can see that the gains in performance from the later driver also carries over to the Flyby demo. In this case, though, the effects are mainly noticed at the lower resolutions as the Flyby demo gets fill-rate bound quite quickly.




1.2.0.42 640x480 800x600 1024x768 1280x960 1600x1200
Normal 170.6 153.2 111.4 76.1 51.2
2X Aniso 151.3 114.1 76.4 51.6 34.5
4XFSAA 136.4 99.4 69.8 48.7 33.5
2X Aniso + 16X FAA 111.2 78.1 53.7 37.1 25.4
 
% Difference 640x480 800x600 1024x768 1280x960 1600x1200
2X Aniso -11% -26% -31% -32% -33%
16X FAA -20% -35% -37% -36% -34%
2X Aniso + 16X FAA -35% -49% -52% -51% -50%

Again we can see that the performance hit for both Anisotropic filtering and FAA are quite similar with the Flyby element of the UT2003 benchmark as it is with the Botmatch. Utilising them both at the same time incurs a greater penalty, roughly halving the performance across most of the resolutions.