Direct 3d problems

[milkymilk]

Whenever I run games that rely solely on Direct 3d (IE: Alien vs. Predator 2) It says it cannot find the direct3d.ren
I used the DirectX diagnostics, and both direct draw and direct 3d come out successful on the tests. I've tried those crappy detenator drivers, and all of them just crash my computer. I have to stick with my driver that came with my vid card. That one is the most stable. Can anyone help me?

[michaelwest]

Tell us what video card you have so we can help you.

[milkymilk]

what da heck... i have my specs on the signature thing.. oh wells

Win2k Pro
256 mb SDRAM
PNY Verto Geforce2 GTS/PRO
Pentium 3 500 MHz

----------------------------------------

hmm.. looks like diablo 2 cant detect my d3d either. check out the tests.

02.17.02 08:58:49 D2VideoTest running under Windows 2000 (Version 5.000)
Vendor: Intel
Version: Pentium III (Type 0, Family 6, Model 7, Stepping 2)
Speed: Approx. 497 MHz
Total Physical Memory: 255.48 MB
Application Path: C:\Program Files\Diablo II\D2VidTst.exe
imagehlp.dll loaded for better stack crawls.
----------------------------------------------

Able to access user registry to delete flag
Deleted vidtestrequiredflag
... continuing Video Test
Enumerating display device
Creating running dialog
Running dialog displayed, continuing ...
Ready to detect operating system
Detecting Operating System and DirectX...
osDetect()
Valid version of DirectX found. (4.8.0.400)
...Done Detecting Operating System and DirectX: Success
OSDetect passed: Registering window class...
... Done Registering window class
DDrawDetect...
Detecting boards which support DirectDraw...
Checking capabilities of NVIDIA GeForce2 GTS/GeForce2 Pro...
Supports 32 bit cutscenes.
Video Memory Total= 0.000 MB, Free= 0.000 MB
Passed requirements for Diablo II.
Destroyed DDraw window.
Direct3DDetect...
Detecting boards which support Direct3D...
Checking capabilities of NVIDIA GeForce2 GTS/GeForce2 Pro...
VendorID = 0x00000000, DeviceID = 0x00000000
***** Direct3D error: Create 3D HAL Device (mode enumeration) failed! - D3D_OK (0x0)
***** Direct3D error: Create 3D HAL Device (mode enumeration) failed! - D3D_OK (0x0)
Supports 32 bit cutscenes.
Couldn't find valid display mode for user interface screens.
Couldn't find valid display mode for game screens.
Destroyed D3D window.
Found no valid Direct3D devices to use!
GlideDetect...
Detecting boards which support Glide...
Missing glide3x.dll. Assuming no 3dfx boards present!
Done with Detection phase...
Creating final dialog ...
Recommending ddraw0 in final dialog.
Displaying info message in final dialog.
Show window in final dialog.
Ending final dialog for IDOK.
Done with Interactive phase...
Able to access user registry to delete flag
Video Test application completed without error.

[milkymilk]

someone please help me out

[wolf20]

U might wanna check on ur manufactures web page or contact them for support. It might be possible that ur card doesn't work properly.

J T

[FPoole]

Start->run
type dxdiag
disable direct3d then reenable it.
There is a glitch where d3d is disabled but does not show it...

worked for me and i had the same troubles...

[milkymilk]

it says direct3d is not availiable i couldnt even disable it

[FPoole]

How did dxdiag say direct 3d was running properly if it is not available? What version are you using? have you tried reinstalling it? are your drivers all updated?

[milkymilk]

i have no idea... but ill send my screenshots after i get home. Detenator drivers crash the sh^t out of my computer. Soo I have to stick with my driver that came with my graphics card. It only does it on windows 2000, when i ran windows 98, direct3d with my graphics card worked fine. the only problem was, win98 was mad buggy soo i switched to 2k pro.

[FPoole]

Well, if you haven't already you should start from scratch and download a fresh version of directx for win2k and reinstall that mofo. What detonators were you using?

[milkymilk]

here are some screenshots when i ran dxdiag

[milkymilk]

.

[milkymilk]

.

[milkymilk]

.

[milkymilk]

all of the detenators dont work for me

23, beta 27, the 21's, even the 16s

[FPoole]

Well...

Did you actually download and install a new version of directx?

[milkymilk]

Ya I did, direct x 8.1... didnt work either =(

[FPoole]

that is totally screwed. So I guess your system is not recognizing your card as a direct3d compatible one. Or something to that effect. One thing, when you installed the detonators, did you first uninstall the old drivers? I have had some difficulties with that. Where if I just install over the old drivers, then my system turns into a big pile of ****....

[milkymilk]

ya i tried that... still the same effect, though with the detenators, the system recognizes direct3d but everytime i play a game of any kind it freezes.

[FPoole]

When you try to play the games in D3d, do they work at all? I mean do you at least get into the game before it crashes? Who manufactured your video card?

[milkymilk]

ya i can sorta get to the game, but after a few plays, when i get into the menu of the game, it freezes. its manufacturer is PNY, vid card is called PNY Verto Geforce 2 GTS/PRO

[milkymilk]

when it freezes like that, is that called an infinite loop?

[FPoole]

This would seem to imply that you do not actually have a directx problem. Your current video drivers must not be compatible with whatever version of directx you are using. I think you are going to have to find a way to get some working updated drivers. If you are still using the ones you got with your card then you are bound to have troubles. Have you visited the pny website to get their latest drivers? You should look for a FAQ about your card and see if you can find anything there. Also you should check your agp aperature settings. I usually leave them set to about half of whatever the video card ram is. Also, if you are running a via chipset, make sure you have the latest drivers for that.

The detonator drivers usually help everyone, try them again.