Known limitations

Velocity9x refuses a draw an engine cannot express rather than drawing it wrong. On the GMA 950, the two Matrox 3D chips and the Rage 128 Pro a refused draw is drawn by the CPU instead; elsewhere it is not drawn.

By interface

• Direct3D: Direct3D 9 is not available. Direct3D 8 is offered 16-bit colour only (16-bit modes, textures and depth, no stencil), except on the HD 4600 and the Intel Gen3 chips, which get the DirectX 8 interface with pixel shader 1.1. A shader beyond 1.1 fails to create rather than drawing wrong.
• OpenGL: an OpenGL 1.1 ICD. Lighting runs on the HD 4600 only; every other card draws OpenGL unlit. Display lists, evaluators, and feedback and selection are not implemented yet.
• Glide: Glide 2 and 3. Glide, and 3DCIF everywhere, is 16-bit colour with a 16-bit depth buffer.
• ATI 3DCIF: mipmaps, the Rage Pro’s tiled texture layout, and meshes and TLVERTEX vertices are not done. The HD 4600 is not supported for 3DCIF.
• Colour depth: Direct3D renders at 32 bpp with a 24- or 32-bit depth buffer on the GMA 950, 900 and 3150, the HD 4600 and the Millennium II; several Radeons and the Mystique render 32 bpp with 16-bit depth only. Every other card’s 3D is 16-bit.
• Display: no packed 24-bpp modes, and no hardware cursor on any card.
• CPU rasterizer: the software Direct3D renderer, the default in the vbe package, has not been timed on a period machine. Expect it to be slow.

Operating systems

Windows 98 SE is the main target. One physical Trio64 on VESA Local Bus runs under Windows 95, installed by hand; that does not establish general Windows 95 compatibility. Windows Me has no validated configuration.

Open issues in the current release

The per-card issues are on each card’s page in the hardware database, and the full list is in the Velocity9x README’s known issues.