Tech-Hounds.com

Because gamers play games, not benchmarks




NVIDIA Forceware Revisited

Graphics card drivers
PCI Express x16 graphics cards
Graphics card NVIDIA GeForce 6600GT

After doing our round up of GeForce 6600GT, we came to the conclusion that there's a lot of homework to be done by NVIDIA's driver developers. Since then, NVIDIA has release the latest Forceware version, the 78.01. We recently received the Gigabyte GeForce 6600GT Silent Pipe (which you can read the review here), but we used Forceware 77.72 for evaluation purposes in that review. Of course, we're aching to see whether or not NVIDIA fixed the many problems we encountered in Forceware 78.01. What better way to test it but by using additional games? We spent some time with everyone's favorite these past months - Battlefield 2.



We only spent a short time with Battlefield 2, so we won't be using it in testing (for now). This is more of a quick and dirty test, we choose the above settings since it's still very playable on the GeForce 6600GT. You'll also notice that the 100 fps cap is still active. We really like the custom quality options, since it allows us to troubleshoot graphical glitches and problems. Unlike Battlefield 1942 and Battlefield: Vietnam, Battlefield 2 uses shaders extensively and each time we change video settings, the game will automatically 'optimize' the shaders for best performance. Even with fixed settings, the game will optimize the shaders if you change graphics card drivers. We ran test with three drivers - Forceware 66.93, 77.72 and 78.01. There are some graphical differences as you can see below.





While the images are not exactly the same frame, you can clearly see quality differences. We didn't use a Battle Record, opting for a screenshot in game, that's why they don't exactly match up. With Forceware 66.93, the (dynamic) shadows will render incorrectly, resulting in the artifact you can see clearly on the first image. You can however, turn off the lighting (although not completely) to avoid this bug. Forceware 77.72 and 78.01 renders the shadows correctly.





However, Forceware 77.72 has a graphical bug that renders some parts (the sandbags) a little 'funky'. It's even more annoying to look at if you're moving the camera. This artifact is not present on Forceware 66.93 and 78.01. So, at least compatibility wise, the latest Forceware 78.01 is the best one to use with Battlefield 2. How about performance?


Forceware 66.93
Forceware 77.72 Forceware 78.01
Minimum fps
52.25
50.85
57
Average fps 69.18
70.39
72.30
Maximum fps
82.25
84.57
85

These are average results from five runs, with 5 to 10 % variance between each run. As you can see, the maximum fps never reach the 100 fps with the settings we used on the GeForce 6600GT. However, long extensive gameplay does indicate we can see much lower fps than these (especially with lots of smokes and explosions), down to the 25 to 30 fps range. It's clear that upping the settings will tax the graphics card beyond its capability. You really have to use at least a GeForce 6800GT if you want to use the 'High' settings.

Our incursion with Battlefield 2 shows that again you need newer drivers if you want to play newer games on NVIDIA hardware. Sadly, with past driver versions, this mean sacrificing some performance and quality with older games. But it looks like things are getting better with Forceware 78.01. Let's see whether or not that's true for all games, new and old. Forceware 66.93 is very similar to 66.81 and you can look at the quality differences in our past article (which you can read here and here). There's no need to post the 78.01 screenshots, since they're basically the same as with 77.72, so let's discuss performance.

Performance

Performance testing are done with either the built-in tools in the game or by playing a replay or a cut scene that's close to actual gameplay and measuring the frame rate per second with FRAPS. Just like Battlefield 2, in Brothers in Arms we actually played a level in a certain, repeatable way, so there are some variances with the results. We ran the game three times and average the results, for each setting and resolution. Even without averaging, the raw scores are very close to one another, usually within 5 %. We haven't done extensive testing with Battlefield 2 yet, so no Battlefield 2 scores (for now).

Our test setup
AMD Athlon 64 3000+ socket 939
2 x 256 MB Kingston KVR 3-3-3 PC3200 DDR-SDRAM
MSI K8N SLI Platinum Socket 939 PCI Express motherboard
Gigabyte GeForce 6600GT Silent Pipe graphics card
Maxtor DiamondMaxPlus9 80 GBs Serial ATA 8 MB buffer
ASUS E-616 DVD-ROM
450 watts ATX power supply

Windows XP Professional with Service Pack 2 installed
NVIDIA NForce 4 6.66 reference driver
Creative SoundBlaster Live! 24 bit 5.12.1.512 driver.
DirectX 9.0c
all respected games used for benchmarks have been updated to their latest, final builds

The results:

Call of Duty - Dawnville
Forceware 66.93
Forceware 77.72
Forceware 78.01
146.56
141.36
126.53
132.3 (4xAA 16x AF)
106.96 (4xAA 16x AF)
81.86 (4xAA 16x AF)
.
149.73
142.56
127.96
132.96 (4xAA 16x AF)
107.13 (4xAA 16x AF)
74.05 (4xAA 16x AF)
.
150.03
142.1
127
132.7 (4xAA 16x AF)
107.1 (4xAA 16x AF)
78.96 (4xAA 16x AF)

Looks like we're off to a good start. Performance with the latest Forceware 78.01 is basically the same as with Forceware 77.72. Forceware 66.93 is slightly faster (particularly on 1600 x 1200 with AA and AF), but for all intent and purposes, the three drivers offer the same level of performance.

Splinter Cell - Caspian Oil Refinery. 1024 x 768
Forceware 66.93
Forceware 77.72
Forceware 78.01
36.03
55.22
100.02
33.98 (16x AF)
53.28 (16x AF)
104.57 (16x AF)
.
39.69
67.69
107.02
38.9 (16x AF)
65.72 (16x AF)
120.6 (16x AF)
.
39.84
67.63
118.1
38.89 (16x AF)
65.64 (16x AF)
116.02 (16x AF)
Splinter Cell - Caspian Oil Refinery, 1280 x 1024
Forceware 66.93
Forceware 77.72
Forceware 78.01
24.73
41.88
63.54
24 (16x AF)
40.5 (16x AF)
66.83 (16x AF)
.
26.41
48.41
66.25
25.82 (16x AF)
47.13 (16x AF)
65.36 (16x AF)
.
26.38
48.35
77.4
25.84 (16x AF)
47.1 (16x AF)
66.19 (16x AF)
Splinter Cell - Caspian Oil Refinery, 1600 x 1200
Forceware 66.93
Forceware 77.72
Forceware 78.01
18.9
35.82
51
18.36 (16x AF)
34.48 (16x AF)
49.76 (16x AF)
.
19.79
40.13
56.85
19.37 (16x AF)
39.01 (16x AF)
55.48 (16x AF)
.
19.8
40.11
57.37
19.39 (16x AF)
38.98 (16x AF)
64.36 (16x AF)

Looks like the shader 'bug' we've seen on the Forceware 71.22 up to 77.72 is still present in the newest drivers. Unlike previous test results, we now see quite a significant difference between the 66.93 and 77.72 / 78.01. Instead of 1 or 2 fps, it's now 4 to 12 fps. Mind you, these results came from the Gigabyte GeForce 6600GT Silent Pipe which has a slightly higher clock than the reference specification. This might explain the performance difference between these and previous results, but it doesn't explain why we're seeing this much performance difference by using a different drivers (particularly since the image output is not the same).

F1 Career Challenge - Custom Replay. 1024 x 768
Forceware 66.93
Forceware 77.72
Forceware 78.01
54
82.46
103
51 (4x AA 16x AF)
76.59 (4x AA 16x AF)
94 (4x AA 16x AF)
.
56
80.81
97
28 (4x AA 16x AF)
34.59 (4x AA 16x AF)
38 (4x AA 16x AF)
.
56
83.02
101
30 (4x AA 16x AF)
36.3 (4x AA 16x AF)
40 (4x AA 16x AF)
F1 Career Challenge - Custom Replay. 1280 x 1024
Forceware 66.93
Forceware 77.72
Forceware 78.01
54
82.43
103
35 (4x AA 16x AF)
55.65 (4x AA 16x AF)
71 (4x AA 16x AF)
.
44
58.77
68
18 (4x AA 16x AF)
22.32 (4x AA 16x AF)
25 (4x AA 16x AF)
.
46
62.08
71
19 (4x AA 16x AF)
23.41 (4x AA 16x AF)
26 (4x AA 16x AF)
F1 Career Challenge - Custom Replay. 1600 x 1200
Forceware 66.93
Forceware 77.72
Forceware 78.01
48
77.86
99
22 (4x AA 16x AF)
32.95 (4x AA 16x AF)
40 (4x AA 16x AF)
.
32
43.11
50
12 (4x AA 16x AF)
14.3 (4x AA 16x AF)
16 (4x AA 16x AF)
.
34
45.85
52
12 (4x AA 16x AF)
14.98 (4x AA 16x AF)
16 (4x AA 16x AF)

Looks like NVIDIA still have no fix for the shadow rendering bug in this game. With shadows set to 'Full', we're still seeing very low performance. So, it looks like you still have to sacrifice the shadows in this game if you want a fluid, entertaining gameplay.

Nascar Season 2003 - Custom Replay, 1024 x 768
Forceware 66.93
Forceware 77.72
Forceware 78.01
42
60.79
104
42 (4x AA 16x AF)
60.61 (4x AA 16x AF)
104 (4x AA 16x AF)
.
41
58.87
103
41 (4x AA 16x AF)
58.55 (4x AA 16x AF)
103 (4x AA 16x AF)
.
40
58.25
102
40 (4x AA 16x AF)
57.89 (4x AA 16x AF)
102 (4x AA 16x AF)
Nascar Season 2003 - Custom Replay, 1280 x 1024
Forceware 66.93
Forceware 77.72
Forceware 78.01
40
58.17
104
40 (4x AA 16x AF)
56.15 (4x AA 16x AF)
80 (4x AA 16x AF)
.
39
56.51
102
39 (4x AA 16x AF)
55.41 (4x AA 16x AF)
88 (4x AA 16x AF)
.
38
55.49
102
38 (4x AA 16x AF)
55 (4x AA 16x AF)
93 (4x AA 16x AF)
Nascar Season 2003 - Custom Replay, 1600 x 1200
Forceware 66.93
Forceware 77.72
Forceware 78.01
39
55.65
102
31 (4x AA 16x AF)
36.42 (4x AA 16x AF)
43 (4x AA 16x AF)
.
37
53.89
101
33 (4x AA 16x AF)
39.03 (4x AA 16x AF)
46 (4x AA 16x AF)
.
36
53.16
101
35 (4x AA 16x AF)
40.83 (4x AA 16x AF)
48 (4x AA 16x AF)

Thankfully, nothing's wrong in Nascar 2003. We're still seeing 2 to 3 fps difference, with the newer drivers being slower. But you don't have to worry, the difference is not noticeable. Of course, there are some image quality compromises, but everything should clear up when AA and AF are enabled.

Brothers in Arms - Chapter 1, 1024 x 768
Forceware 66.93
Forceware 77.72
Forceware 78.01
24
54.6
88
21.33 (4x AA 16x AF)
44.34 (4x AA 16x AF)
81 (4x AA 16x AF)
.
28.33
65.14
104.67
23.67 (4x AA 16x AF)
51.98 (4x AA 16x AF)
99 (4x AA 16x AF)
.
28.33
69.49
108.33
29.33 (4x AA 16x AF)
55.77 (4x AA 16x AF)
Brothers in Arms - Chapter 1, 1280 x 1024
Forceware 66.93
Forceware 77.72
Forceware 78.01
17
38.36
67.67
15 (4x AA 16x AF)
30.71 (4x AA 16x AF)
61.67 (4x AA 16x AF)
.
16.67
44.03
82
12.67 (4x AA 16x AF)
35.05 (4x AA 16x AF)
74 (4x AA 16x AF)
.
19
48.33
83
18 (4x AA 16x AF)
40.03 (4x AA 16x AF)
73.66 (4x AA 16x AF)
Brothers in Arms - Chapter 1, 1600 x 1200
Forceware 66.93
Forceware 77.72
Forceware 78.01
12
28.61
53.67
9 (4x AA 16x AF)
21.34 (4x AA 16x AF)
44 (4x AA 16x AF)
.
10.5
32.98
67
9 (4x AA 16x AF)
24.19 (4x AA 16x AF)
50.5 (4x AA 16x AF)
.
14.5
35.48
64
8.5 (4x AA 16x AF)
26.71 (4x AA 16x AF)
51 (4x AA 16x AF)

Like we said before, newer drivers targets newer games. While we're not seeing the same increase going from 77.72 to 78.01 as going from 66.93 to 77.72, we're still seeing a little performance boost (around 2 to 3 fps) across the board. Of course, you'd be more happy to know that the 78.01 also will not crash you system when you quit the game (or alt-tabbing).

Homeworld 2 - Vaygr Bomber Attack, 1024 x 768
Forceware 66.93
Forceware 77.72
Forceware 78.01
31
153.23
352
27 (4x AA 16x AF)
120.15 (4x AA 16x AF)
355 (4x AA 16x AF)
.
33
165.16
364
21 (4x AA 16x AF)
89.06 (4x AA 16x AF)
168 (4x AA 16x AF)
.
33
164.09
363
21 (4x AA 16x AF)
88.64 (4x AA 16x AF)
168 (4x AA 16x AF)
Homeworld 2 - Vaygr Bomber Attack, 1280 x 960
Forceware 66.93
Forceware 77.72
Forceware 78.01
33
136.26
352
20 (4x AA 16x AF)
92.61 (4x AA 16x AF)
259 (4x AA 16x AF)
.
32
133.21
333
14 (4x AA 16x AF)
60.56 (4x AA 16x AF)
105 (4x AA 16x AF)
.
32
133.46
333
14 (4x AA 16x AF)
60.38 (4x AA 16x AF)
105 (4x AA 16x AF)
Homeworld 2 - Vaygr Bomber Attack, 1600 x 1200
Forceware 66.93
Forceware 77.72
Forceware 78.01
25
111.51
346
14 (4x AA 16x AF)
65.5 (4x AA 16x AF)
167 (4x AA 16x AF)
.
20
94.36
215
9 (4x AA 16x AF)
41.16 (4x AA 16x AF)
68 (4x AA 16x AF)
.
21
95.35
215
9 (4x AA 16x AF)
41.2 (4x AA 16x AF)
68 (4x AA 16x AF)

Performance in Homeworld 2 are identical between Forceware 77.72 and 78.01. While that might seem good, it's actually not. Forceware 66.93 is still the fastest driver. Quite surprising, since Homeworld 2 is an OpenGL game, where NVIDIA should excel. Thankfully, patching the game to the latest version now gives you real anti aliasing and anisotropic filtering with the game (regardless of driver versions).

SW: KOTOR - Endar Spire, 1024 x 768
Forceware 66.93
Forceware 77.72
Forceware 78.01
19.67
61.12
76.33
12.67 (4x AA 16x AF)
41.23 (4x AA 16x AF)
60.67 (4x AA 16x AF)
.
22
56.34
81
13.67 (4x AA 16x AF)
40.25 (4x AA 16x AF)
54.33 (4x AA 16x AF)
.
22
55.66
84.33
13.33 (4x AA 16x AF)
38.62 (4x AA 16x AF)
54.67 (4x AA 16x AF)
SW: KOTOR - Endar Spire, 1280 x 1024
Forceware 66.93
Forceware 77.72
Forceware 78.01
16
45.7
68.67
9.67 (4x AA 16x AF)
30.59 (4x AA 16x AF)
44 (4x AA 16x AF)
.
14
47.44
71
12 (4x AA 16x AF)
26.81 (4x AA 16x AF)
36.67 (4x AA 16x AF)
.
15.33
48.48
70.33
13.33 (4x AA 16x AF)
28.17 (4x AA 16x AF)
36.33 (4x AA 16x AF)
SW: KOTOR - Endar Spire, 1600 x 1200
Forceware 66.93
Forceware 77.72
Forceware 78.01
8.67
34.05
50.67
10 (4x AA 16x AF)
22.34 (4x AA 16x AF)
31.67 (4x AA 16x AF)
.
10.3
34.89
51.67
9 (4x AA 16x AF)
19.84 (4x AA 16x AF)
26.33 (4x AA 16x AF)
.
8.33
34.52
52
9 (4x AA 16x AF)
19.5 (4x AA 16x AF)
26 (4x AA 16x AF)

Just like Nascar 2003 and Homeworld 2, SW: KOTOR doesn't get any noticeable performance improvement with newer drivers. You're getting the same level of performance with both Forceware 77.72 and 78.01.

Conclusion:

Driver bugs can be very annoying, both for developers and users alike. Squashing them out takes a lot of time and effort. With the number of games out there, it just get harder It's perfectly understandable driver developers target the newest, popular games first - Battlefield 2 is a perfect example of this. However, this does not excuse the (re)introduction of old or new bugs on old games. Just like with Forceware 77.72, we're still seeing quality image problems and significant performance slowdown with Forceware 78.01 compared to Forceware 66.93.

For the time being, NVIDIA users must still make some compromises on a game to game basis. We'll be updating our driver choice of testing to Forceware 78.01, however for testing with F1 Career Challenge and Splinter Cel, we'll fall back to Forceware 66.93. Again, the reason for this is that this should give us a clearer view, sans driver bugs (and shader replacement), of what the GeForce series can do. Hopefully, within the next week or so, we will have another graphics card round up, this time with more new games (at least Battlefield 2).

Go to top
Disclaimer and Privacy policy.