Menu
NV31 brings directX 9.0 support to CeBit

NV31 brings directX 9.0 support to CeBit

With the GeForce FX alias NV30, of course, the graphics chip development does not stop at nVidia either and so the inexpensive NV31 will be presented at CeBit 2003. With performances on the level of a GeForce 4 Ti4600 and the technology level of the GeForce FX, a new chip awaits us for the home user.

The NV31 chip will not only be simpler than the NV30, it will be Graphics cards based on this product clock the memory and the chip significantly lower. However, this is not a problem if at least the supported features are correct. Based on the code name, one could at least assume so. Because every chip in the NV3X family should fully support DirectX 9.0 .

This clearly sets the NV31 apart from the products of the previous 'GeForce 4 MX' series. Because the GeForce 4 MX with its DirectX 7.0 support was technologically only a drilled GeForce 2.

  • NV15: GeForce 2 GTS (fixed-function TnL according to DX 7.0)
  • NV17: GeForce 4 MX (hardware-supported vertex shader, no pixel shader, according to DX 7.0)
  • NV20: GeForce 3 (vertex shader 1.1, pixel shader 1.1 according to DX 8.0)
  • NV25: GeForce 4 Ti (Vertexshader 1.1, Pixelshader 1.3 to DX 8.0/8.1)
  • NV30: GeForce FX (Vertexshader 2.0+, Pixelshader 2.0+, to DX 9.0 and higher)
  • NV31: GeForce FX? (Vertexshader 2.0+, Pixelshader 2.0+, according to DX 9.0 and higher)

Even if the official designation of the GeForce 4 MX does not necessarily indicate a 'backward' product, it did and does the code name does. AtAt this point, the question arises as to how the NV31 differs from the NV30. Is it just a time difference? Does nVidia perhaps dispense with the use of expensive DDR II modules or was the red pen used in other areas, such as the number of render pipelines? With all of this, it only seems certain that at least everything that is necessary for a fully DirectX 9.0 compatible product has not been deleted. We'll be smarter by this year's CeBit at the latest.