iXBT Labs - Computer Hardware in Detail






NVIDIA GeForce4 Ti 4400
and GeForce4 Ti 4600 (NV25) Review

[ Part I ]

The NV25 chip was awaited for a long time by many as an echo of 3dfx's deals, as a competitor against ATI RADEON 8500 and as the second optimized and enriched incarnation of NV20. Let me dive directly into the root of the matter...

Attention! Before reading the review you should turn to the previous articles on NVIDIA GeForce3 (NV20) and ATI Radeon 8500 (R200).

Product line

The GeForce 4 line is based on two chips - NV17 and NV25 which is the today's main hero:

  • GeForce 4 Ti4600 - NV25 300 MHz core, 128 MBytes 325(650) MHz 128-bit DDR memory.
  • GeForce 4 Ti4400 - NV25 275 MHz core, 128 MBytes 275(550) MHz 128-bit DDR memory.
  • One more junior card on the NV25 will be announced later.
  • GeForce 4 MX460 - 300 MHz core, 64 MBytes 275(550) MHz 128-bit DDR memory.
  • GeForce 4 MX440 - 270 MHz core, 64 MBytes 200(400) MHz 128-bit DDR memory.
  • GeForce 4 MX420 - 200 MHz core, 64 MBytes 166 MHz 128-bit DDR memory.


  1. The GeForce 3 line will be quickly replaced with the GeForce 4 one.
  2. NV17 doesn't and won't support pixel and vertex shaders.
  3. NV17 will have MPEG2 hardware decoder and dynamic power management system, and the NV25 does not.
  4. NV17 has only two fill pipelines, and NV25 - four.
  5. NV25 has a superscalar (dual) T&L unit, NV17 has a single one.
  6. NV17 and NV25 have similar memory controllers (2x-channel one of the NV17 and a 4-channel one of the NV25).
  7. Both chips have the same set of systems for increasing the memory effective bandwidth (Z buffer compression and fast Z clear, MSAA, HSR).
  8. NV17 has 2 integrated LCD-panel controllers.
  9. Both chips have two independent RAMDACs, CRTC controllers, and integrated TV-Out and DVI interfaces.

This pretty monster will help promoting and advertising NV25 based products demonstrating advanced soft illumination, skeletal animation, hair and fur made of vertex shaders and per-pixel relief:




Main architectural innovations of the NV25 (vs. NV20)

  1. 2 independent CRTC controllers. Flexible support of all possible modes and of output of two frame buffers independent in resolution and in contents onto any accessible signal receivers.
  2. 2 normal 350 MHz RAMDACs integrated in the chip (with a 10bit palette).
  3. Integrated TV-Out.
  4. Integrated TDMS transmitter (for DVI interface).
  5. 2 units of interpretation and implementation of vertex shaders. They promise a considerable growth of a processing speed of a scene with complicated geometry. The units can't implement a different microcode of shaders, and the only advantage of processing of two vertices simultaneously is a performance increase.
  6. Improved fill pipelines provide hardware support of pixel shaders up to v1.3 inclusive.
  7. According to NVIDIA, an effective fillrate in the MSAA modes got higher, and now 2x AA and Quincunx AA modes will cause much less performance drop. The Quincunx AA is improved (positions of sample fetching are shifted). A new AA method appeared - 4xS.
  8. Improved separate caching system (4 separate caches for geometry, frame buffer and Z-buffer).
  9. Improved lossless compression (1:4) and fast Z clear.
  10. Improved hidden surface removal algorithm (Z Cull HSR).

Further we will check all these declared advantages of the new chip.

The above changes are rather evolutionary rather than revolutionary as compared with the previous NVIDIA's product (NV20). But it is typical of NVIDIA to release first a product carrying a great deal of new technologies and then its improved (optimized) variant. Just take TNT and TNT2, GF256 and GF2, and now GF3 and GF4. The experience shows that usually the second variant meets with great success.

Performance characteristics

First of all, a bit of explanation:

  1. The accelerator can't be examined ignoring its drivers. Chip's capabilities depend on whether the drivers support certain applications for two main APIs. Many characteristics from the table can depend on drivers and can be correct, first of all, for a certain version. Moreover, some possibilities can be available even if the drivers do not mention them (for example, clipping planes in D3D for NVIDIA cards). We will consider such features absent as a correctly written application mustn't try to use options the driver doesn't report about.
  2. The most of the data relate to Direct3D, and in OpenGL these parameters can differ. There are several reasons of it, and first of all, it should be noted that this gaming API is closer to the accelerator's hardware. Besides, capabilities of modern accelerators are much dependent on the D3D specification.

And now take a look at the summary table of the key characteristics of the chips and cards tested today. Keep in mind that in the nearest quarter the ATI RADEON 8500 will be a main competitor of NV25 based cards (GeForce 4 Ti 4600 and Ti 4600) because of the postponed release of RADEON 8500XT and because first R300 based products won't appear very soon.

Card GeForce3 Ti 500 RADEON 8500 GeForce 4 Ti 4600 (GeForce 4 Ti 4400)
Chip, revision, driver version
Chip NV20 R200 NV25
Revision A5 A23 A03
Driver version 27.30 6.018 27.30
Main parameters
Pipelines 4 4 4
Texture blocks 2 2 2
Textures at a pass 4 6 4
Core frequency, MHz 240 275 300 (275)
Fill rate (million pixels) 960 1100 1200 (1100)
Fill rate (million texels) 1920 2200 2400
RAMDAC, MHz 350 400 (+ external 240) 350*2
Local memory parameters
Memory frequency, MHz 250 275 325 (275)
Memory bus, bits 128 (DDR) 128 (DDR) 128 (DDR)
Technology, micron 0.15 0.15 0.15
Memory size, MB 64 64 128
Memory speed, ns 3.8 3.6 2.8 (3.6)
OpenGL version 1.3 1.3 1.3
DirectX version 8.1 8.1 8.1
GDI+ acceleration Yes Yes Yes
Pixel pipeline
Pixel shaders 1.0, 1.1 1.0..1.4 1.0..1.3
Range of calculated color values -1.0..+1.0 -8.0..+8.0 -1.0..+1.0
Texture stages 4 8 4
Combination stage 8 8 8
Multisampling 2,3,4 samples No 2,3,4 samples
Clipping planes 0 6 0
Vertex shader
Vertex shaders 1.0, 1.1 1.0, 1.1 1.0, 1.1
Vertex streams 16 8 16
Constants of vertex shader 96 192 96
Matrices for blending (max.) 4 4 4
Indexed blending No Up to 57 matrices No
Light sources 8 8 8
N-Patches No Yes No
RT-Patches No No No
Primitives 1048575 65536 1048575
Vertices 1048575 16777215 1048575
Other parameters
Pure Device Yes Yes Yes
Sprite scaling up to 64 256 8192
3D textures Yes (with anisotropy) Yes (without MIPMAP) Yes (with anisotropy)
Reflection mapping Yes (with anisotropy) Yes (without MIPMAP) Yes (with anisotropy)
Anisotropic filtering Yes Yes Yes
Anisotropy degree up to 2,3,4 bi/trilinear sampling 2,3 bilinear sampling in a line 2,3,4 bi/trilinear sampling
Frame buffer
Rendering buffer formats A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A8R8G8B8 X8R8G8B8 R5G6B5 A1R5G5B5 A4R4G4B4 R3G3B2 A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5
Z-buffer formats D32 D24S8 D16 D24X8 D32 D24S8 D16 D24X8 D32 D24S8 D16 D24X8
Texture formats
Maximum texture size (maximum repeat) 4096x4096(8192) 2048x2048(2048) 4096x4096(8192)
2D texture formats A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A1R5G5B5 A4R4G4B4 P8 V8U8 L6V5U5 X8L8V8U8 DXT1 DXT2 DXT3 DXT4 DXT5 D24S8 D16 D24X8 A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A1R5G5B5 A4R4G4B4 R3G3B2 L8 A8L8 V8U8 L6V5U5 X8L8V8U8 Q8W8V8U8 V16U16 W11V11U10 DXT1 DXT2 DXT3 DXT4 DXT5 A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A1R5G5B5 A4R4G4B4 P8 V8U8 L6V5U5 X8L8V8U8 DXT1 DXT2 DXT3 DXT4 DXT5 D24S8 D16 D24X8
3D texture formats A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A1R5G5B5 A4R4G4B4 P8 A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A1R5G5B5 A4R4G4B4 R3G3B2 L8 A8L8 Q8W8V8U8 W11V11U10 DXT1 DXT2 DXT3 DXT4 DXT5 A8R8G8B8 X8R8G8B8 R5G6B5 X1R5G5B5 A1R5G5B5 A4R4G4B4 P8


  1. GeForce4 Ti4600 has a higher clock speed of the core and memory than the RADEON 8500. The GeForce4 Ti4400 also has the same core and memory clock speed as the RADEON 8500.
  2. At last NVIDIA products got dual-monitor support, and unlike the R200, here both normal 350 MHz RAMDACs are integrated into the NV25 chip.
  3. The NV25's RAMDAC has a lower frequency as compared with the primary RAMDAC of the R200 (350 against 400 MHz)
  4. Organization of the internal architecture of the NV25 is close to the NV20 and R200 - 4 fill pipelines with two texture blocks on each. However, in case of the R200 results of their operation can accumulate twice, thus, allowing us to combine up to 6 textures at a pass; the NV25 limits them to 4. Nevertheless, there is no any applications capable to get a sound gain using 6 textures at a pass. However, the Next Doom is going to be such application.
  5. Again, NVIDIA doesn't support 1.4 pixel shaders (see R200 review in detail) and a more flexible mechanism of dependent sampling of texture values. Shaders are, in fact, translated into settings of sampling and combination pipelines; the number of stages of texture sampling pipeline remains the same - 4 of the NV25/NV20 against 8 of the R200; some slight changes in the combination pipeline make possible to support 1.2 and 1.3 shaders on the hardware level. Their difference from the 1.1 shaders is connected not with organization of more flexible dependent sampling, but with utilization and modification of Z values and other useful options.
  6. Combination pipelines of all chips have 8 stages and support all specified DirectX 8.1 operations.
  7. The current drivers of the NV25 do not support a larger number of constants to be enabled in vertex shaders (96 against 192 of the R200) or of vertex shader instructions (128). It seems that there are no other qualitative changes apart from the second T&L unit (which is also a vertex shader interpreter) are made in the pipeline.
  8. The NV25 memory now successfully works at the same frequency as the R200, with the rated access time being also the same. However, it doesn't mean the same efficiency as the R200 and NV20/NV25 approach issues related with memory operation differently. The NV25 prefers smaller blocks and an effective 4-channel crossbar controller, and the R200 uses larger blocks and intensive combined caching. What approach is more viable in modern tests and applications we will see later.
  9. All the cards have normal DirectX 8.1 and OpenGL 1.3 drivers. The OpenGL driver from ATI is considered less efficient than that of NVIDIA. But the difference is becoming narrower, and at present it depends on how the OpenGL works with geometry and whether it uses index buffers - the R200 itself is less efficient in delivering geometry via AGP than the NV20/NV25.
  10. To some reason, the current drivers of the NV20 and NV25 report that there are no clipping planes, though in our tests they work excellently. The reason is that NVIDIA uses a special pixel driver to realize clipping planes which uses the most part of slots of a combination pipeline and then an application becomes unable to use its own pixel shader and some other resources. It doesn't comply with the DirectX standard, and that is why clipping planes were disabled at the level of the reported capabilities.
  11. NV25 doesn't support N-Patches on a hardware level again.
  12. The drivers of the NV20 and NV25 do not support hardware tessellation of smooth surfaces (HOS based on RT-Patches). When a card doesn't support N-Patches on a hardware level the API tries to emulate them using RT-Patches. It makes operation of N-Patches very slow. NVIDIA thus had to disable the RT-Patches so that games supporting N-Patches won't be too slow.
  13. NV25 doesn't support indexed matrix blending like the NV20 as the shaders can help organize flexibly any schemes of matrix blending.
  14. Multisampling hasn't changed since NV20 - the same 2..4 samples which the R200 is not capable of.
  15. Realization of the anisotropy of NV25/NV20 is different from R200, and each approach has its advantages and disadvantages.
  16. The range of pixel shader values of the NV25 is still -1.0 to 1.0 - the higher precision of the R200 had no response to.
  17. All cards support a standard set of texture formats, though the R200 supports some more formats for additional data in shaders (normal and displacement maps) with an increased precision of component delivery (11 and 16bit - V16U16, W11V11U10); NV25 and NV20 make possible to use textures with the Z buffer format (D32, D24S8, D16, D24X8) necessary to realize Depth Buffer Shadows algorithms. Usage of this algorithm which is peculiar to NVIDIA products by applications in the drivers for DirectX is nonstandard.
  18. NV25 doesn't allow compressing 3D textures. It is a bad drawback of the drivers or the chip. At the same time the OpenGL drivers from NVIDIA have their own 3D texture compression format.
  19. NV25 supports all types of fog, like the NV20 does.

Here is a complete list of OpenGL extensions supported by the NV25 in the current drivers:


GL_RENDERER: GeForce4 Ti 4400/AGP/SSE2



  • GL_ARB_imaging
  • GL_ARB_multisample
  • GL_ARB_multitexture
  • GL_ARB_texture_border_clamp
  • GL_ARB_texture_compression
  • GL_ARB_texture_cube_map
  • GL_ARB_texture_env_add
  • GL_ARB_texture_env_combine
  • GL_ARB_texture_env_dot3
  • GL_ARB_transpose_matrix
  • GL_S3_s3tc
  • GL_EXT_abgr
  • GL_EXT_bgra
  • GL_EXT_blend_color
  • GL_EXT_blend_minmax
  • GL_EXT_blend_subtract
  • GL_EXT_compiled_vertex_array
  • GL_EXT_draw_range_elements
  • GL_EXT_fog_coord
  • GL_EXT_multi_draw_arrays
  • GL_EXT_packed_pixels
  • GL_EXT_paletted_texture
  • GL_EXT_point_parameters
  • GL_EXT_rescale_normal
  • GL_EXT_secondary_color
  • GL_EXT_separate_specular_color
  • GL_EXT_shared_texture_palette
  • GL_EXT_stencil_wrap
  • GL_EXT_texture3D
  • GL_EXT_texture_compression_s3tc
  • GL_EXT_texture_edge_clamp
  • GL_EXT_texture_env_add
  • GL_EXT_texture_env_combine
  • GL_EXT_texture_env_dot3
  • GL_EXT_texture_cube_map
  • GL_EXT_texture_filter_anisotropic
  • GL_EXT_texture_lod
  • GL_EXT_texture_lod_bias
  • GL_EXT_texture_object
  • GL_EXT_vertex_array
  • GL_EXT_vertex_weighting
  • GL_HP_occlusion_test
  • GL_IBM_texture_mirrored_repeat
  • GL_KTX_buffer_region
  • GL_NV_blend_sq

The same list in the latest drivers of the R200:

GL_VENDOR: ATI Technologies Inc.

GL_RENDERER: Radeon 8500 DDR x86/SSE2

GL_VERSION: 1.3.2475 WinXP Release


  • GL_ARB_multitexture
  • GL_ARB_texture_border_clamp
  • GL_ARB_texture_compression
  • GL_ARB_texture_cube_map
  • GL_ARB_texture_env_add
  • GL_ARB_texture_env_combine
  • GL_ARB_texture_env_crossbar
  • GL_ARB_texture_env_dot3
  • GL_ARB_transpose_matrix
  • GL_ARB_vertex_blend
  • GL_ARB_window_pos
  • GL_S3_s3tc
  • GL_ATI_element_array
  • GL_ATI_envmap_bumpmap
  • GL_ATI_fragment_shader
  • GL_ATI_pn_triangles
  • GL_ATI_texture_mirror_once
  • GL_ATI_vertex_array_object
  • GL_ATI_vertex_streams
  • GL_ATIX_texture_env_combine3
  • GL_ATIX_texture_env_route
  • GL_ATIX_vertex_shader_output_point_size
  • GL_EXT_abgr
  • GL_EXT_bgra
  • GL_EXT_blend_color
  • GL_EXT_blend_func_separate
  • GL_EXT_blend_minmax
  • GL_EXT_blend_subtract
  • GL_EXT_clip_volume_hint
  • GL_EXT_compiled_vertex_array
  • GL_EXT_draw_range_elements
  • GL_EXT_fog_coord
  • GL_EXT_packed_pixels
  • GL_EXT_point_parameters
  • GL_ARB_point_parameters
  • GL_EXT_rescale_normal
  • GL_EXT_secondary_color
  • GL_EXT_separate_specular_color
  • GL_EXT_stencil_wrap
  • GL_EXT_texgen_reflection
  • GL_EXT_texture_env_add
  • GL_EXT_texture3D
  • GL_EXT_texture_compression_s3tc
  • GL_EXT_texture_cube_m

The most of NV25 extensions remained standard which means a stronger influence of NVIDIA on the OpenGL. Now let's turn to the video cards based on two NV25 versions: GeForce4 Ti 4400 and 4600.


Both models are reference cards based on the NVIDIA GeForce4 Ti 4400 and 4600. The look very close to each other, though there are some differences. Besides, the Ti 4400 chip works at 300 MHz instead of 275 MHz of production cards. The frequency of the Ti 4600 correspond to the planned one.

The cards have an AGP x2/x4 interface, 128 MBytes DDR SDRAM located in 8 chips on the right and back sides of the PCB.

The cards are equipped with memory chips of the BGA form-factor from Samsung.

Access time of the Ti 4400 is 3.6 ns which corresponds to 275 (550) MHz.

Access time of the Ti 4600 is 2.8 ns which corresponds to 357 (714) MHz.

The cards use memory chips in a new BGA package. This form-factor provides more effective cooling of chips and memory (the GeForce4 Ti 4600 operates at a frequency a little less than the rated one for 2.8ns). Frequencies of our samples (core/memory) are:

  • NVIDIA GeForce4 Ti 4600 - 300/325 (650) MHz;
  • NVIDIA GeForce4 Ti 4400 - 300/275 (550) MHz.

Despite a high frequency of the chips and memory they do not warm up much, especially the memory chips. That is why I think that no additional cooling for memory will be provided on production cards. Let's return to the differences between the cards:

NVIDIA GeForce4 Ti 4400

NVIDIA GeForce4 Ti 4600

There are differences only in the right part which has a power transformation unit. The memory chips and the GPUs have different voltage levels and consumption currents.

Take a look at the cooler on the GPU:

Air is pumped through a channel with a fin heatsink by a fan located to the left.

The reference card based on the NVIDIA GeForce4 Ti became larger (Hercules 3D Prophet III Titanium 500 based on the reference design of GeForce3 Ti 500 is used for comparison (below)):

Compare the dimensions of the GeForce4 Ti and 3dfx Voodoo5 which is the largest gaming video card:

As you can see, our card is just a bit smaller.

The dual-head support is a distinguishing feature of this card from the previous ones. The most powerful accelerators from NVIDIA had never the TwinView support before (now this option is called nView).

Look at a size of the VGA (d-Sub) connector. There is also space for the second DVI connector which will probably be in great demand in the near future.

Below the VGA connector is a TV-out with an S-Video connector. The video-interface chip for this function is located on the back side of the card and is marked as CX25871 (up to 1024x768 supported); the chip is produced by Conexant. As the TV-out interface is integrated in the GPU the production samples will probably lack for this chip.

In the lower part of the card we have a DVI connector (digital/analog) which generates a signal for the second analog CRT monitor (a DVI-to-VGA adapter is used):

Later we will examine the dual monitor support in detail.


It is obvious that it makes no sense to overclock the junior model (Ti 4400). The GeForce4 Ti 4600 can operate stably at 320 MHz of the GPU and 365 (730) MHz of memory. The overclocking potential is just 20 MHz (it is possible that it depends on a sample), and the memory showed an excellent reserve taking into account that it is produced by Samsung. We were also able to overclock the 3.6ns memory on the TI 4400 up to 300 (600) MHz .


  • in course of overclocking you must provide additional cooling, in particular, a fan for the card (first of all, for its memory);

  • overclocking depends on the definite sample, and you shouldn't generalize the results of one card to all video cards of this mark or series. The overclocking results are not the obligatory characteristics of a video card.

Test system and drivers

Test system configuration:

  • Pentium 4 based system (Socket 478):
    • Intel Pentium 4 2100;
    • ASUS P4T-E (i850) mainboard;
    • 512 MBytes RDRAM PC800;
    • Quantum FB AS HDD, 20 GBytes;
    • Windows XP, Windows ME.

  • Athlon XP based system:
    • AMD Athlon XP 1800+;
    • EPoX 8KHA+ (VIA KT266A);
    • 512 MBytes DDR SDRAM PC2100;
    • Fujitsu 20 GBytes;
    • Windows XP, Windows ME.

The test systems were coupled with ViewSonic P810 (21") and ViewSonic P817 (21") monitors.

In the tests we used NVIDIA's drivers v27.20 and 27.30. VSync was off, S3TC was activated.

For the comparative analyses we used the following cards:

  • Reference card NVIDIA GeForce3 Ti 500 (240/250 (500) M, 64 M);
  • ATI RADEON 8500 (RADEON 8500, 275/275 (550) M, 64 M, driver 9.008 (Windows ME) / 6.014 (Windows XP)).

Driver and nView settings

In the tests we used v27.20 and v27.30 drivers (both versions are identical regarding an interface and speeds, that is why we will address settings of only v27.20 for the Windows XP).

Here we have a new AA level - 4xS. It appears only for new cards based on the NV25.

Now it is possible to adjust anisotropic filtering in the OpenGL. However, its feature is avaialble starting from v23.*.

A new feature allows to rotate an image at 90 degrees which is very helpful for designers working with LCD displays. Unlike program packets which are able to rotate an image by 90 degrees this feature is implemented on the GPU level, that is why it doesn't slow down 2D displaying and makes no compatibility problems with new OS versions.


nView is a data displaying management system. It consists of two parts:

  • Desktop manager;
  • Dual monitor support (including TV-out).

In the Desktop Manager mode we can create several (up to 32) virtual desktops on one screen:

Besides, we can manage windows, effects when working with the latter ones etc.:

Then you can create your own profile and safe there all made settings:

The most interesting function is dual monitor support. We already saw the TwinView function on the GeForce2 MX cards, that is why this tub isn't new for us:

Apart from the Clone mode there are others.

Of course, there is an Extended mode which allows a second display device to become an additional part of your desktop real estate. You can also adjust DVC settings (digital vibrance control) for each monitor separately (it is shown on the shots below: first DVC is enabled on the left screen, then on the right one):

The horizontal and vertical span mean that the desktop together with a control panel is just spread onto the second monitor,

Extension of the desktop allows many users to achieve their dream - to work on the first monitor and watch movies on the second one. It becomes really possible if you use TV-out as the second monitor.

To make the above shot we used a WinDVD player started on the primary monitor, then dragged to the secondary window and switched to the full screen.

If DVD playback protection will get enabled on the secondary monitor to some reason, you can open a DVD window on the primary monitor and then interchange the primary and secondary receivers in the drivers.

By the way, the NV25 doesn't support the MPEG2 hardware decoder. In our "program" case with the latest WinDVD version the CPU utilization wasn't more than 18% (the nView was activated).

Test results

2D graphics

Image quality in 2D is excellent. You can work comfortably in 1600x1200 at 85 Hz. I think that the quality of the Matrox G400/G450 is achieved in this respect.

Remember that estimation of 2D quality is subjective and depends on a certain card and on compatibility of a video card and a monitor.

3D graphics, MS DirectX 8.1 SDK - extreme tests

We used modified examples from the latest version of the DirectX SDK (8.1, release).

Optimized Mesh

This test demonstrates a practical limit of an accelerator's throughput when triangles are used. Several models are displayed simultaneously in a small window, each consisting of 50,000 triangles. No texturing. The models are minimal in size: each triangle is not greater than 1 pixel. Such result can not be obtained for real applications where triangles are usually large and where lighting textures are used. Below there are results for three drawing methods - Optimized for an optimal drawing speed (taking into account an internal cache of vertices on the chip), Unoptimized and Strip (when one Triangle Strip is displayed):

In the first case, Optimized model, the memory subsystem doesn't have a great effect, and we measure a pure performance of transformation and drawing of triangles. The Ti 4600 (NV25) thrives. 56M triangles/sec is a twice higher result as compared with the RADEON 8500 and Ti 500. This is achievement of the second T&L unit. In case of the Unoptimized model we measure efficiency of caching and of memory bandwidth. The result of the NV25 is proportional to the difference in frequencies of the R 8500 and Ti 4600. In case of the Strip the R200 loses; the NV25 beats the NV20 in accordance with the frequency difference.

The NV20 and NV25 performs better when the program geometry calculation is activated forcedly. The NVIDIA chips have an advantage thanks to the FastWrites mechanism which transfers graphics data directly into the accelerator from the processor passing by a system memory. In case of the Strip there is no more such advantage because a data rate is twice lower.

Performance of the vertex shader unit

This test demonstrates an ultimate performance of the vertex shader unit. A complicated shader calculates both specific transformations and geometrical functions. The test is carried out in the lowest resolution to minimize a shading effect. Z-buffer is off, and the HSR can't affect the results as well:

The dual T&L of the NV25 is beneficial again. Besides, one of the most powerful CPUs loses in a speed of graphics data processing. The NV25 has a more efficient delivery of geometry calculated on a program level as compared with the NV20 (the drivers are equal for both chips).

The R200's speed of processing of vertex shaders has grown twice and it is now equal to the program emulation speed. This time we decided to check whether the R200 processes vertex shaders on a program level and lowered the clock frequency to 1 GHz. The results (HARDWARE 1860, SOFTWARE 1470) show that they are processed on a hardware level. Well, ATI was able to optimize the drivers successfully.

Vertex matrix blending

This feature is used for true animation and skinning of models. We tested blending using two matrices both in a tough hardware variant and using a vertex shader with the same function. Besides, we obtained the results of the T&L program emulation:

This time the program emulation loses to the hardware implementation being limited by the graphics data rate via the AGP. As I mentioned before the NVIDIA products has some advantage thanks to the FastWrites support. This time (vs. the last big test of the R200) in case of the hardware implementation the shaders go on a par with the hardware blending, and now it makes no sense to use the latter on modern chips. It is interesting that the tough hardware blending is a bit slower on the NV20 and a bit faster on the NV25 than the shader one, but the difference is insignificant, which is reasonable as neither NV20 nor NV25 have a fixed T&L. In fact, functions of this unit are implemented by a special shader microcode, and equality of the results shows that optimization of the driver-compiled shaders is optimal.

EMBM relief

This test measures a performance drop caused by Environment mapping and EMBM (Environment Bump). We tested in 1280*1024 as exactly in this mode difference between cards and texturing modes is the most vivid:

The Ti 4600 outscores all other cards in an effective fillrate in all three modes. The R200 suffers most from the EMBM. The NVIDIA chips shade much more efficiently especially if we take it per unit of clock frequency - 240 MHz of the NV20 will be, thus, equal to 275 MHz of the R200.

Performance of pixel shaders

Again we used MFCPixelShader and measured performance of the cards in the high resolution using 5 shaders different in complexity for bilinear filtered textures:

The Ti 4600 is again riding high, and the dependence on the shader complexity and on the number of textures is very similar to the previous chip (NV20). The R200 looks weak, especially when fulfilling complex tasks. Reuse of texture units is dearer for it than for the NVIDIA products.

Well, in the DX 8.1 SDK tests the NVIDIA GeForce4 Ti 4600 is an undoubted leader. However, remember that only real applications will allow us estimate an overall balance of this chip. Stay tuned!

3D graphics, VillageMark (HSR efficiency)

To estimate realization of the HSR we used a test with a high OverDraw level - VillageMark v.1.17. Here are the results of both cards with enabled and disabled HSR:

Apart from obvious advantage of the NV25 in 1280x1024, the performance drop with the HSR disabled is quite small both for NV25 and NV20. But it doesn't mean that the HSR is less efficient. If for the R200 card we disable the HyperZ completely (including HSR, Z compression, fast Z-clear), for the NVIDIA cards we could disable only the Z compression, while the HSR (Z-Cull) is disabled in the 27.XX at default and can be activated with the help of keys in the register. On the whole, the NV25 performs better in the scenes with a high overdraw parameter.

It should be noted that the scene in this test is drawn not from the depth layer by layer but 'as is', that is why HSR of non-tile chips which performs best in this way of scene drawing doesn't have a great effect in comparison with tile architectures which sort a scene on a hardware level. As the most of real applications display scenes without sorting polygons we consider this test quite correct.

3D graphics, preliminary test based on the iXBT/Digit-Life RightMark Video Analyser

At the moment we are developing a 3DMark-like packet the tests of which will be freely available. We have created a little preliminary test based on one scene and an engine which will be a base of this packet. The test will have complicated geometry (over 150,000 polygons in a frame) and wide utilization of DirectX 8.1 features. Lighting is based on vertex shaders, shading - on pixel ones, EM and EMBM are used widely, i.e. up to 4 textures are put over one pixel. Besides, the Shadow Buffer technology is used to calculate shadows of objects in a real-time mode. The test doesn't depend much on a processor (later we will return to strong dependence on a processor in the 3D Mark 2001 in all High Detail scenes).

Here are some screenshots:

Test results:

The test doesn't depend much on resolution because of very complicated scenes and a big load on the geometrical part of the accelerator. But when AA is enabled which influences positively visual quality of the scenes with a great number of small polygons resolution becomes important. I think that resolution won't be a problem soon and all applications will be focused on flexibility of more and more complicating geometry. It is interesting that again in 1280*1024 the gap between the NV25 and the NV20 is the largest. The increased memory bandwidth and its doubled size helped the NV25 much in this mode. Note that this mode is typical of 17" and 18" monitors.

3D graphics, 3DMark2001 - synthetic tests


We measured this parameter only for 32-bit color depth:

The NV25 is again a leader. It is of really great interest to compare shading efficiency of the NV25 operating at the rated frequency of the Ti500 (240/500). The gain is noticeable, that is why architectural optimization of the fill pipeline and memory controller is also significant. The theoretical limit of this test is 960M pixels/sec for the Ti 500, 1100 for the RADEON 8500 and 1200 for the Ti 4600. This time the NV25's architecture approaches the theoretically maximum fillrate comparable to the R200. Despite the same production technology and just a little greater number of transistors the NV25 easily outdoes the NV20 both in the limiting working frequency and in efficiency of operation at the same frequency.

In case of several textures the chips have drawn much nearer to the theoretical limit. The best result of this test can be achieved at the highest resolution.

Scene with a great number of polygons

Remember that in the highest resolution the dependence on a fill rate almost disappears:

The NV25 becomes a leader when one light source is used. Its result is very close to the practical limiting bandwidth for triangles obtained earlier with the Optimized Mesh from DX8.1 SDK. You can see that the overall efficiency has increased due to the second shader unit if you compare results of the NV25 and NV20 at the same frequency. The R200 also came very close to the limiting value obtained in the SDK test, but it considerably falls behind in the absolute value, although the core frequency is almost equal to the NV25.

In case of 8 light sources the performance of the R200 falls down slower as compared with the NV20 and NV25, though the palm still belongs to NVIDIA.

Relief texturing

Look at the results of a synthetic EMBM scene:

The results reflect EMBM mostly in high resolutions; in 800x600 the the determining factor is geometry. It is interesting that at the same frequency the EMBM is implemented by the NV25 slower than by the NV20 - probably it is a cost of optimization of the fill pipeline which is very effective in case of usual shading and especially beneficial when the MSAA is enabled. And now comes the DP3 relief:

The NV25 again leads.

Vertex shaders

The test results are shown for several resolutions.

As the resolution increases the R200 becomes weaker as it is limited by the shading efficiency; the speed of the NV25 goes down much slower. Besides, the dual T&L of the NV25 is twice better in its architecture than the NV20 at the same frequency.

Pixel shader

Taking into account that in too low resolutions a bottleneck is geometry, and in too high ones it is memory bandwidth let's take a look at 1024x768 and 1280x1024:

The NV25 thrives again despite the same frequency with the NV20. However, pixel shaders do not have a great architectural advantage as the possibility of hardware realization is much poorer as compared with vertex shaders.


The NV25 outscores the NV20 by a great margin at the same frequency. In the low resolution a geometry processing speed makes a decent effect, but in middle ones everything takes its places again. I can't say the NV25 is leading firmly, but it is well seen that the NV25 was much improved as compared with NV20. Besides, its capabilities of sprite scaling are also wider.

Well, in the synthetic tests the NVIDIA GeForce4 Ti 4600 takes the palm, but you should remember that only real applications will let us make the final conclusions.

3D graphics, 3DMark2001 - gaming tests

3DMark2001, 3DMARKS

According to the general benchmarks the GeForce4 outscores its predecessor by 30%. The RADEON 8500 lost to the GeForce3 Ti 500 in the 3DMark2001 test.

The 3DMark2001 includes 4 gaming tests, three of which are implemented at low and high detailing graphics levels. High detailing means that the processor and video accelerator are much more loaded with additional effects and polygonal complexity of the scenes. However, at a high detailing level in these tests the performance becomes limited by a CPU frequency in case of a highly efficient accelerator. The GeForce 4 proved it. And we had to exclude High Detail tests.

3DMark2001, Game1 Low details

This is a war auto simulator. The developers state that this game scene spends processor time for calculation of physics and motion of objects as a real game. Characteristics:

  • Rendered triangles per frame (min/avg/max): 19773/33753/143422
  • Rendered textures per frame with 16 bit textures (min/avg/max): 7.5/8.8/16.5 MB
  • Rendered textures per frame with 32 bit textures (min/avg/max): 15.1/17.7/30.3 MB
  • Rendered textures per frame with texture compression (min/avg/max): 10.7/12.2/21.0 MB

In 1600x1200x32 the GeForce3 Ti 500 is beaten by the GeForce4 Ti 4400 by 30.5%, and by the GeForce4 Ti 4600 by 36.2%.

If we compare OSs we will see that the results in the XP are worse than in the ME.

3DMark2001, Game2 Low details

This is an arcade scene from a 3D Adventure or strategic game. The scenes have a high overdraw factor and a weak optimization of the geometry. The accelerator must provide optimization of operation with a Z-buffer. Characteristics:

  • Rendered triangles per frame (min/avg/max): 46159/51440/147828
  • Rendered textures per frame with 16 bit textures (min/avg/max): 8.0/8.8/10.1 MB
  • Rendered textures per frame with 32 bit textures (min/avg/max): 15.6/17.2/19.8 MB
  • Rendered textures per frame with texture compression (min/avg/max): 9.3/10.9/13.5 MB

In 1600x1200x32 the GeForce3 Ti 500 is beaten by the GeForce4 Ti 4400 by 27.4%, and by the GeForce4 Ti 4600 by 38.8%, and in 1280x1024x32 the figures are 35.1% and 45.3% respectively. It is interesting that again the peak falls on 1280x1024 and the drop falls on 1600x1200.

The ATI RADEON 8500 performs equally in Widows XP and ME, and the NVIDIA shows better scores in the former one.

3DMark2001, Game3 Low details

The scene is based on the "Matrix". A detail level is not high, it corresponds to the Quake2. There is skinning (matrix blending) and skeletal animation, detailed textures and a great deal of various bullet shells and pieces which load the GPU very much. Characteristics:

  • Rendered triangles per frame (min/avg/max): 16681/21746/39890
  • Rendered textures per frame with 16 bit textures (min/avg/max): 2.8/4.1/4.7 MB
  • Rendered textures per frame with 32 bit textures (min/avg/max): 5.7/8.2/9.4 MB
  • Rendered textures per frame with texture compression (min/avg/max): 5.0/7.2/8.4 MB

In 1600x1200x32 the GeForce3 Ti 500 falls behind the GeForce4 Ti 4400 by 19.3%, and behind the GeForce4 Ti 4600 by 29.1%.

Comparison of the OSs showed that the performance of all cards is higher in the ME.

3DMark2001, Game4

This test uses pixel shaders, vertex shaders and cube texturing to form water surfaces. That is why it is better to play this game only on the GeForce3/4 or RADEON 8500 (in the demo mode water surface is not displayed). Characteristics:

  • Rendered triangles per frame (min/avg/max): 55601/81714/180938
  • Rendered textures per frame with 16 bit textures (min/avg/max): 14.9/17.4/20.7 MB
  • Rendered textures per frame with 32 bit textures (min/avg/max): 28.4/33.5/40.0 MB
  • Rendered textures per frame with texture compression (min/avg/max): 28.4/33.5/40.0 MB

In 1600x1200x32 the GeForce3 Ti 500 falls behind the GeForce4 Ti 4400 by 25%, and behind the GeForce4 Ti 4600 by 37.5%.

Comparison of the OSs showed that the NVIDIA card performs better in the ME and the ATI RADEON 8500 has equal results both under ME and XP.

3D graphics, gaming tests

To estimate performance in 3D games we used the following tests:

  • Quake3 Arena v.1.17 (id Software/Activision) - a gaming test which demonstrates operation of cards in OpenGL using a demo benchmark of the Q3DM9 level with large textures - Quaver;
  • Return to Castle Wolfenstein (id Software/Activision) - a gaming test which demonstrates operation of cards in OpenGL using Checkpoint benchmark;
  • Serious Sam v.1.05 (Croteam/God Games) - a gaming test which demonstrates operation of cards in OpenGL using Karnak demo benchmark;
  • GLMark (Vulpine) - a synthetic test which demonstrates operation of cards in OpenGL enabling GeForce3 capabilities;
  • AquaMark v.2.2 (Massive Development) - a gaming test which demonstrates operation of cards in DirectX 8.1 using pixel shaders;
  • Giants: Citizen Kabuto (Planet Moon Studios/Digital Mayhem/Interplay) - - a gaming test which demonstrates operation of cards in Direct3D using Gamegauge demo benchmark.

Quake3 Arena

Quaver, highest quality modes

The tests with Quaver were carried out in 16-bit and 32-bit color modes at the highest detailing and complexity levels of geometry (r_subdivisions "1" r_lodCurveError "30000"). This benchmark loads accelerators with complicated geometry as well as with huge textures and a great deal of effects.

Pentium 4 2100

Athlon XP 1800+

The GeForce 4 which was purposely slowed down to the frequency of Ti 500 (d/c 240/500 MHz) shows much better performance than the Ti 500 which means good optimization of different units of the GeForce4 in comparison to the GF3.

We also overclocked the ATI RADEON 8500 to the assumed level of the next revision - 300/300 (600) MHz, and we can see that such gain won't help the chip.

Both developers worked well on the OpenGL ICD making the performances equal in the Windows XP and Windows ME, and the NVIDIA's drivers do have better results in the Windows XP.

In 1280x1024x32 the GeForce3 Ti 500 lags behind the GeForce4 Ti 4400 by 20.3% and behind the GeForce4 Ti 4600 by 24.3%. In 1600x1200x32 the figures are 26.5% and 33.3% respectively. The chip's frequency grew up from 240 to 300 MHz and now amounts to 25%.

Serious Sam

Karnak demo, Quality mode

Here are screenshots of the settings:

Pentium 4 2100

Athlon XP 1800+

The diagrams show both average and lowest performance results. The performance drop, when moving from 16 to 32-bit mode, showed that the time of 16-bit color has passed. All accelerators provide good playability even in 1600x1200x32.

In 1600x1200x32 the GeForce3 Ti 500 falls behind the GeForce4 Ti 4400 by 34.8%, and behind the GeForce4 Ti 4600 by 39.3%.

Return to Castle Wolfenstein (Multiplayer)

Checkpoint, highest quality modes

The tests were carried out in 32-bit color at the highest detail and quality levels of textures.

Pentium 4 2100

Athlon XP 1800+

Although this game is more GPU and CPU dependent the competitors take the same places.

Again we can see that the OpenGL ICD works excellently under the Windows XP. The NVIDIA based cards have better results in the Windows XP than in the Windows ME.

In 1600x1200x32 the GeForce4 Ti 4400 beats the Ti 500 by 25.6%, and the GeForce4 Ti 4600 outscores it by 34.6%, which are very good results for the GPU whose frequency is higher by 25%. As you can see, the memory bandwidth is of vital importance here.


Gamegauge, highest quality modes

We think that this game excellently shows power and capabilities of modern video cards when geometry is very complicated as compared with other benchmarks for DX (the game shows relief texturing technique based on the Dot3 and environment mapping which requires a high fillrate from the accelerators). The disadvantage of this test is dependence on a CPU frequency and on a platform.

Pentium 4 2100

Athlon XP 1800+

The performance gain is not so striking this time.

Look how better the performance is under the Windows ME than under the Windows XP. It is obviously not the drivers but the game which was adjusted for this OS.

The Ti 500 loses to the GeForce4 Ti 4400 by 7.9%, and to the GeForce4 Ti 4600 by 10.6% (in 1600x1200x32). Keep in mind that it is the Windows XP which demonstrates a lower performance. Besides, the engine of the game hardly reacts on power growth of a video card. Probably, it is CPU dependence which is guilty.


Highest quality modes

GLMark uses extensions of OpenGL from NVIDIA typical of the GeForce3, that is why it is interesting to compare GeForce3 and GeForce4 in this test, though the results of the ATI RADEON 8500 are also shown (but remember that this card is not able to use some bump mapping functions peculiar to the GeForce3 and some NVIDIA extentions for acceleration of GeForce3/4 cards. The cards were tested only in 32-bit color.

Pentium 4 2100

Athlon XP 1800+

This is a very complicated test (considering the number of polygons and effects of relief texturing). Only in 1280x1024x32 the GeForce4 allows playing comfortably. The Ti 500 yields to the GeForce4 Ti 4400 by 37.5%, and to the GeForce4 Ti 4600 by 41.5%.

The test of the GeForce4 at the Ti 500's frequency of 240/500 MHz showed once again that the architecture of the new GPU is much improved.


Default Quality Modes

The test uses a set of textures of 24 MBytes, pixel shaders are enabled, and the cards were tested only in 32-bit color.

Pentium 4 2100

Athlon XP 1800+

Almost a year ago the the AquaMark benchmark was created on the base of the AquaNox game. Scene complexity in the AquaMark was almost 130,000 polygons. However, the GeForce4 easily copes with it. In 1600x1200x32 the Ti 500 loses to the GeForce4 Ti 4400 by 58.7%, to the GeForce4 Ti 4600 by 69.5% ! It is interesting that this test makes strong demands to a GPU instead of the memory bandwidth. The difference between the 4400 and 4600 models is minimal.


The MIP-mapping technology improves image quality for scenes with objects that extend from the foreground deep into the background. It creates for each texture a set of MIP-levels (its copies of different detail levels) which are chosen based on the size and the resulting scale. The further the triangle is, the more blurry the MIP-level will be used. Trilinear filtering smoothes over sharp edges of MIP-levels. Thus, while bilinear filtering removes sharp edges between texture pixels, the trilinear one softens an image even more so that only close objects can be seen sharper. At the same time, walls which are at a too sharp angle for us are too blurry. And anisotropic filtering is used to cope with such inconvenient objects for bilinear and trilinear filterings.

Different processor makers realize this function differently. Besides, speed characteristics of anisotropic filterings of ATI and NVIDIA differ much as well. Only the resulting quality is similar.

But is that true? As you know, the NVIDIA's anisotropy (in case of GeForce3) has high quality, but it eats much as well. The performance drop can reach 50%! ATI's anisotropy (in case of RADEON 8500) is much cheaper and provides apparently the same quality.

Quality of anisotropy can be estimated by examples of walls, floors etc. And our attentive readers know that the RADEON 8500 doesn't use any anisotropy on some surfaces located at angles different from 90 degrees. Look at the screenshots of the Serious Sam game:



Here are animated GIF files:


At some angles the RADEON 8500 provides no sharpness. The NVIDIA GeForce3 and GeForce4 do not have such problems. It isn't good if a user can't choose between the full anisotropy with great losses and its cheaper approximation.

The GeForce4 has, in fact, the same anisotropy method as of the GeForce3, i.e. 3 levels, each having the maximum texture sampling value for realization of anisotropic filtering (Level2 - 8, Level4 - 16, Level8 - 32 samples).

NVIDIA's and ATI's approaches to anisotropic filtering realization

While bilinear and trilinear filterings are mathematically strictly defined (though some time ago NVIDIA called a trilinear filtering some approximation method - dithering of values from different MIP levels), the concept of anisotropic filtering doesn't imply definite algorithms of its realization. Approaches of NVIDIA and ATI to this issue are different. Let me show you some figures:

NVIDIA: the figure shows fetching of bilinear samples in the texture space during implementation of the anisotropic filtering. Depending on filtering quality settings and inclination of surface a standard bilinear (or trilinear) filtering is implemented from one to four times for points lying on a straight line which divides a pixel projected from the screen onto a texture surface along its long side (the line is shown with an arrow on the figure). The values obtained this way (blue circles) are averaged, and make the result of the filtering. Each value is based on four closest discrete values of the texture (rectangles) and can have its own independent coordinates. Such approach suits for arbitrarily oriented textures but it requires a great level of performance - for the visible part of triangles non-parallel to the screen the number of fetched texture samples grows up several times, so does the shading time.

The ATI's approach is more limited but more efficient as well:

The values are fetched in a line which can lie either horizontally or vertically in the texture's plane. For values of the projection vector which are close to the orts (the arrow on the figure) the filtering quality will be high, but as it turns the effect will be decreasing until this method starts making no sense at all. In real applications the filtering will work good on walls or ceilings, but the results will be vanishing on surfaces located at angles different from the right one the result will be less noticeable till the critical angle of 45 degrees is reached. However, such approach is beneficial from the computational point of view. First of all, we can choose organized lines from 2õN texture points in size (squares on the figure) which can be effectively fetched during N/2 cycles with the help of standard texture units meant for bilinear filtering. Then we filter values (circles on the figure) using every time the same offset values relative to the discrete points of the original texture. Such operation can be fulfilled at one clock by a special circuit of ten multipliers which is integrated into a texture unit; interpolation parameters are, thankfully, calculated just one time and remain unchangeable for all 1..5 calculated points. Besides, we can speed up this algorithm which is anyway efficient by calculating texture variants specially compressed on axes in advance (so called RIP mapping).

The NVIDIA's approach needs more time to get the result but it processes objects at any angles equally good, not only those positioned just horizontally or vertically. The ATI's method has a rational core as the most of modern games use mostly horizontal and vertical surfaces.


Return to Castle Wolfenstein

3DMark2001, Game1 Low details

3DMark2001, Game2 Low details

3DMark2001, Game3 Low details

3DMark2001, Game4

As you can see, the performance of the GeForce4 falls down by a greater margin as compared with the GeForce3. The Level8 kills all advantages of the GeForce4 as far as speed is concerned. But is it possible at least at Level4 to get the same quality as that of the RADEON 8500? Yes! There will be losses relative to the Level8, but high quality can be provided by making the LOD BIAS value lower. Till recently this parameter could be changed only in the Direct3D with the help of tweakers, for example, RivaTuner. The 27.* drivers allows making it in the OpenGL as well but only in the Registry. Let's see what we can get by setting LOD BIAS to -1 for the Serious Sam: The Second Encounter.

Anisotropic filtering Level 8

Anisotropic filtering Level 4, LOD BIAS = 0

Anisotropic filtering Level 4, LOD BIAS = -1

Anisotropic filtering Level 2, LOD BIAS = -1

Well, the effect is achieved. However, there are also some side effects - moire and texture noise, but the RADEON 8500 has the same when the anisotropy is enabled (at its maximum level). Here the performance drop is not so great. At the Level2 decreasing the LOD BIAS doesn't help any more, though quality of the Level4 at LOD BIAS = 0 can be achieved.


This function is used to remove a stair-step effect. When the AA is enabled the performance drop is even more considerable.

The Quincunx level is fast but it often makes textures soapy. In the GeForce4 we can use the next AA level (4x) which has excellent quality.

Let's look at quality of two the most interesting AA types of the GeForce3 Ti 500 and GeForce4 and compare them.

GeForce3 Ti 500 GeForce4
3DMark2001, Game 1
AA Quincunx
AA 4x
AA 4x AA 4xS
3DMark2001, Game 2
AA Quincunx
AA 4x
AA 4x AA 4xS
3DMark2001, Game 3
AA Quincunx
AA 4x
AA 4x AA 4xS

There is no much difference between the GF3 and GF4 at AA 4x and AA Quincunx levels. The AA 4xS doesn't improve visual quality as well.

New hybrid ÀÀ mode: 4xS.

The new hybrid (MS and SS simultaneously) mode of full-screen anti-aliasing is available on NV25 based cards. Two subunits (2x1) positioned one over the other and obtained the way typical of the 2õ MSAA are averaged in every original 2õ2 AA unit (a usual 4õ MSAA unit is shown on the right for comparison):

S1 is the first 2õ1 subunit, and S2 is the second one. Samples are calculated according to the multisampling method inside the subunit, i.e. from one selected texture value, but texture values can differ in upper and lower subunits, unlike in a usual 4x MSAA. From the accelerator's standpoint we just calculate a vertically doubled image in a standard 2x MSAA mode (2õ1 units). This mode can also be set up in the NV20 but only through undocumented driver parameters in the register. The NV25 based cards allow making this setting in the driver's control panel. It should be noted that the NV25 performs excellently: although the number of interpolated texture values is now twice larger, the performance differs from the 4õ by just a couple of percents, and visual quality is much better. This method can't improve the situation considerably on polygons' edges - SSAA and MSAA look similar there, but textures must be now less blurry. Moreover, for horizontal surfaces (landscapes, floor, ceiling) this method implements some anisotropic filtering functions (2õ quality). Later we will examine closely realization of the 4õS on real images and performance results.

And now let's estimate a performance drop.


Return to Castle Wolfenstein

3DMark2001, Game1 Low details

3DMark2001, Game2 Low details

3DMark2001, Game3 Low details

It is interesting that in AA 2x and AA Quincunx the performance is almost the same (thanks to a great memory bandwidth and optimization of the GeForce4 Ti 4600 in the multisampling mode). Other modes also became more attractive thanks to a greater performance of the GeForce4.

The 4xS mode (works only in Direct3D) turned out to be quite strange. Its speed and quality are approximately at the 4x level. Probably, this mode will be improved.

Joint operation of the anisotropic filtering and AA will be examined in our next reviews of production video cards on the GeForce4 Ti.


  1. The bugs and disadvantages of the NV20 in comparison with the R200 were cured and optimized in the NV25.
  2. Although the technology is the same, and the number of transistors is just a bit higher, the chip working at the same frequency as the previous model is much more efficient especially in intensive tasks and has a much higher frequency limit.
  3. The AA has become cheaper, especially in the Quincunx.
  4. Dual monitor support is excellent both on program and hardware levels.
  5. The chip doesn't belong to the new generation, it is just a debugged and improved version of the previous one.
  6. Similar technology and complexity promise that cards on this chip won't be priced higher than on the Ti500. In this respect the chip can be considered successful - much higher performance and wider capabilities at the same sum of money.
  7. Usage of the BGA memory is a successful and justified move.
  8. Some possibilities (anisotropy, EMBM) are worse a little than in the NV20; but taking into account a much higher clock speed it can be forgiven.
  9. I know that many fans and owners of NVIDIA cards expected more of this chip as almost a year passed since the GeForce3 was released. However, we consider the strategy of gradual growth and optimization more justified as the activity on the IT market decays. The most of new capabilities of the DirectX 8 arrived together with the GeForce3 are just starting their way towards real applications.

The Ti 4400 will probably be positioned as a direct competitor against RADEON 8500, including the price. The Ti 4600 will take a higher position, and lack of competitors will let its price go up without limit.

The new chip of NVIDIA (NV25) is able to sit firmly in the upper-level gaming market, and probably will be the main carrier of DX8 advanced technologies.

[ Part I ]

Write a comment below. No registration needed!

Article navigation:

blog comments powered by Disqus

  Most Popular Reviews More    RSS  

AMD Phenom II X4 955, Phenom II X4 960T, Phenom II X6 1075T, and Intel Pentium G2120, Core i3-3220, Core i5-3330 Processors

Comparing old, cheap solutions from AMD with new, budget offerings from Intel.
February 1, 2013 · Processor Roundups

Inno3D GeForce GTX 670 iChill, Inno3D GeForce GTX 660 Ti Graphics Cards

A couple of mid-range adapters with original cooling systems.
January 30, 2013 · Video cards: NVIDIA GPUs

Creative Sound Blaster X-Fi Surround 5.1

An external X-Fi solution in tests.
September 9, 2008 · Sound Cards

AMD FX-8350 Processor

The first worthwhile Piledriver CPU.
September 11, 2012 · Processors: AMD

Consumed Power, Energy Consumption: Ivy Bridge vs. Sandy Bridge

Trying out the new method.
September 18, 2012 · Processors: Intel
  Latest Reviews More    RSS  

i3DSpeed, September 2013

Retested all graphics cards with the new drivers.
Oct 18, 2013 · 3Digests

i3DSpeed, August 2013

Added new benchmarks: BioShock Infinite and Metro: Last Light.
Sep 06, 2013 · 3Digests

i3DSpeed, July 2013

Added the test results of NVIDIA GeForce GTX 760 and AMD Radeon HD 7730.
Aug 05, 2013 · 3Digests

Gainward GeForce GTX 650 Ti BOOST 2GB Golden Sample Graphics Card

An excellent hybrid of GeForce GTX 650 Ti and GeForce GTX 660.
Jun 24, 2013 · Video cards: NVIDIA GPUs

i3DSpeed, May 2013

Added the test results of NVIDIA GeForce GTX 770/780.
Jun 03, 2013 · 3Digests
  Latest News More    RSS  

Platform  ·  Video  ·  Multimedia  ·  Mobile  ·  Other  ||  About us & Privacy policy  ·  Twitter  ·  Facebook

Copyright © Byrds Research & Publishing, Ltd., 1997–2011. All rights reserved.