DirectX7 compatibility with Voodoo3 drivers 1.02.18 and below
The 1.02.18 and lower drivers are not fully DirectX7 compatible. Some system experience trouble while using these drivers and DirectX7. Use DirectX 6.1 with these drivers. The speed improvement gained by DirectX7 versus DirectX6.1 are little to none. Uninstalling DirectX7 is not easy, so I wouldn't recommend trying DirectX7 to see if it works on your system.
If you already have DirectX7 installed and you are not experiencing any problems combined with the 1.02.18 or lower drivers, you will not have to uninstall it. If you are experiencing trouble don't forget to check the "Direct 3D troubles" section. It might be one of the general D3D troubles instead of DirectX7 specific.
The oldest drivers that do support DirectX7 are the 1.03 drivers, which where distributed in two seperate driver kits for DirectX 6 and DirectX 7. Most users had no problem using the 1.02.11 drivers with DirectX 7.
DirectX7 not working with 1.03 drivers
Make sure you have downloaded the correct version of the 1.03 drivers. There is a DirectX 6.1 and a DirectX7 version of these drivers.
Uninstalling DirectX7
DirectX 7 is an integral part of Windows 95/98 now and cannot be uninstalled.
That's what Microsoft says about this. But you might want to try
dxun, the DirectX Uninstaller by ebrink. You will have to use the 1.1 patch to uninstall DirectX7.
Another way to uninstall DirectX 7 is to use SETUP /ND. The switch /ND makes setup ignore new files & overwrite the files with what is on the Windows 98 disk. You will have to redownload all updates.
If your Glide and OpenGL games work fine, but Direct 3D games always give you a blank screen when you try to run them
- Previous Voodoo owners upgrading
This is directly from the "Voodoo Banshee FAQ" located at the 3dfx website:
Question #3
I had a Voodoo Graphics or Voodoo2 that I replaced with a Voodoo Banshee board. Now I cannot run any games, all I get is an error message or a black screen. Voodoo Graphics and Voodoo2 install a registry key that is used by Direct3D to build a list of secondary devices. If you remove a Voodoo Graphics and Voodoo2 card but do not uninstall the drivers this registry key remains. Games will continue to try and use Voodoo Graphics or Voodoo2 but will fail as the hardware is not present. To fix the problem you should un-install your existing Voodoo card as specified by the manufacturer of your board. If no uninstall procedure is documented you can download the following .inf file that will remove the registry key Direct3D looks for. The delv. inf file will remove the Direct3D registry keys used by Voodoo Graphics and Voodoo2. To use: download the file (Question # 3 on the Banshee FAQ), using Windows Explorer right mouse button click on the file in the download location and choose "Install". If you use the delv.inf file you will no longer be able to access Voodoo Graphics or Voodoo2 as a Direct3D device. If you installed the delv.inf file by mistake and need to re-enable the Direct3D key for your Voodoo2 or Voodoo Graphics card follow these steps: Download the restore file for Voodoo Graphics or Voodoo2. Then using Windows Explorer right mouse button click on the file in the download location and choose "Install".
- If no previous Voodoo card has been installed in the system then there is a registry conflict with a previous display adapter and the registry entries for the previous display card will have to be removed. Please see the "Registry cleaning" section.
- If Direct3D games are crashing back to the desktop etc. and you have an AMD K6 Super Seven board then you will need to set up your BIOS properly. Please look at the "BIOS settings" section.
- Also read the stuttering info below
Stuttering/Chrashing with transparencies
There seems to be a bug in the Direct3D drivers in the Voodoo3 driver version 1.02.11 & 1.02.18. It seems when tranparencies (like smoke or glass) are displayed, the display stutters, missing frames. Some machines even seem to crash when transparencies are displayed. The oldest Voodoo3 drivers (v1.00.00) seem to solve the stuttering problem and are available from the
VoodooFiles. If you are experiencing crashes in these games and tried installing the old drivers, please mail me to let me now if this solves it. Thanks!
Another solve someone mentioned was given to him by a Siemens Nixdorf engineer who suggested reverting to an older version of his bios. It solved his stuttering with his Gigabyte GA-5AX Super Socket 7 motherboard.
Direct3D games crashing
Make sure your motherboard is compatible with the V3. Check out the motherboard section
"No hardware acceleration found" when starting a Direct3D game
Click "Start: and "Run..." and type in "dxdiag"
Click on the "Display" tab at the top of the DirectX diags window. You should see a button that says "Test Direct3D" If that test works, then the problem is with the game.
If that doesn't work - make sure that Direct3D is enabled on that same window (there will be a button next to it that says "Enable" if it is disabled). If it says "no acceleration is available", close the dxdiag tool and go to the Control Panel - double click "System," then the Performance tab, then the "Graphics" button - and make sure the slider is on full "hardware acceleration", then reboot. You will now be able to enable the "Direct3D" acceleration in the dxdiag tool.
DxDiag doesn't show AGP detected on the display page
This is normal for a Voodoo card. Basically there are 3 kinds of AGP implementation as indicated in Intel's paper:
1. Uses the AGP just as a faster PCI slot.
(for example Banshee and Voodoo3/4/5)
2. Uses the AGP with the local video card memory for buffers and system memory for textures.
(for example Intel i740)
3. Uses the AGP with the local video card memory for buffers and texture and system memory for textures.
(for example TNT, G400)
Some diagnostics and utilities fail to identify that the card is AGP if the card uses the first approach, like Final Reality for example. Do not worry about this.
Direct3D FSAA settings will not be saved
In some cases Direct3D FSAA settings will not be saved UNLESS you first set the OpenGL/Glide FSAA ON FIRST.