PDA

View Full Version : Direct3d problems with GF2 MX400


Abscond
01-23-02, 07:25 PM
My other computer, a compaq, has no AGP slot, so I had to resort to a voodoo5 5500 PCI some time ago.

Well I just bought a GF2 MX400 PCI card from PNY, plugged it in... no installation problems, no OpenGL problems. The performance increase was much more than what I expected too.

I went to install 3dmark to see what kinda score I'd get compared to my older voodoo5, and around half way into it.. where it starts to 'initialize texture conversion'.. it stops and says, "Could not create Direct3D device. Please contact madonion.com"

so, i go into the directx dianostic thing.. and try to test direct3d.. but of course, it gave an error.

here's what the FAQ for 3dmark2k1 says (from madonion.com):
Q: Why do I get a message that says: "Could not create Direct3D device"?

A: The texture conversion in the installer requires Direct3D. On some 3D accelerators like Voodoo3, Direct3D can not be initialized in the required mode if the desktop is in 32-bit color mode (as the 3D accelerator can not render in that color depth). Try changing the desktop to 16-bit mode, and start the installation again.

My desktop IS ALREADY on 16-bit mode :mad:

I tried to reinstall directx 8.1 and reinstall the 23.11's.. but neither of which helped.. I still can't play any direct3d based games.:(

anyone know what the problem is? or how i could fix it?

thanks in advance!

o770
01-23-02, 07:38 PM
could you explain what the directx error is?
for now, check if all the directx resources r enabled: cant remember the name of all of them but youll find out the agp texture acceleration, directdraw acc and direct3d acc. this is under the display tab.

RainMaQer
01-23-02, 07:39 PM
Welcome to the Forums...
Are you running the default benchmark? Did you just run the installation programs for the vid card and directx or did you try uninstalling the vid card drivers first? Then maybe reinstalling 3dmark... other than that... all I can think of is clean install of os.:beer:

Abscond
01-23-02, 08:39 PM
here's the error i get when i test direct3d in the display tab of the directx diagnostic:

Failure at step 8 (Creating 3D Device): HRESULT = 0x887602eb (error code)

I tried to look up that error code at ms's 'knowledge base'.. and of course, it didn't recognize it. And I've looked at the official directx FAQ.. and OF COURSE, it doesn't say anything about it. How typical.

Rain: I ran 3dmark2k1 a few weeks ago when i still had my voodoo5.. and then i just uninstalled it. So I've never actually been able to test the new MX since I can't even complete the installation. And yes, I uninstalled the drivers, and then reinstalled. I've tried the 21.81's too.. and they do they very same thing.

How could this be?! the GF2 line is one of the most popular line out, especially the MX... surely it would work perfectly...

I think a clean install of the os might do it.. but god, i really don't want to reformat.

o770
01-23-02, 08:45 PM
r you using any tweak program to config the driver settings?
be sure u havent disabled one of that directx resources i talked about above and that you have all the driver textures enabled, including the compressed ones. its difficult to know what could be causing this whithout knowing how your d3d settings r set to, post a reply with them..

RainMaQer
01-23-02, 09:07 PM
There must be reminence of the voodoo drivers somewhere... As a personal rule of thumb if I change vid cards it means a clean install.:eek: