hopefully this can lead to something :O
Back Buffer Format: X8R8G8B8
Depth/Stencil format: D24X8 (stencil buffer unavailable)
DirectQ 1.7.3 Graphical Issues
Moderator: InsideQC Admins
50 posts
• Page 3 of 4 • 1, 2, 3, 4
by Monster » Fri Oct 30, 2009 3:07 am
gl_cull 0 had no effect... Here is my dxdiag.... I didn't notice anything unusual with it.
http://www.sendspace.com/file/xlrdm3
Nope, not overclocking anything, never have.
http://www.sendspace.com/file/xlrdm3
Nope, not overclocking anything, never have.
-
Monster - Posts: 101
- Joined: Sat Jan 07, 2006 10:27 pm
- Location: North Carolina
by mh » Sat Oct 31, 2009 5:00 pm
One other question that's occurred to me. When you updated your DirectX, did you download it from Microsoft or did you just get d3dx9_37 (or whatever) from dllfiles or somewhere similar? Or have you ever downloaded a missing DirectX file from one of these sites? Not just for DirectQ, but for Fallout 3 or any other game?
I ask this because it's obvious that the problem you have is either with the depth buffer or with matrix transforms. We seem to have ruled out the depth buffer, and DirectQ uses functions from the D3DX library for matrix transforms. If you have an "unofficial" version of one of the D3DX DLLs then I can't legislate for what that version might or might not be doing.
Even if you haven't I would advise that you update your DirectX again. This time, before updating, go to C:\Windows\system32 and either delete the d3dx9_*.dll files or move them to somewhere else. Then go to http://www.microsoft.com/directx and use the websetup to download and install the files you're missing.
Let me know how that goes.
WHAT I NOW BELIEVE IS HAPPENING
A 3D co-ordinate system can be either right-handed or left-handed (there are other systems too, but let's ignore them for now). OpenGL by default uses RH, Direct3D by default uses LH. Direct3D does also provide functions to use a RH system if you want, and DirectQ uses them to avoid messing with the base data.
Something on your machine does not like this. Either you have a bad driver, a bad installation of Direct3D or a bad installation of D3DX. It's not using the RH system at all, despite having been told to do so, and despite it being a required part of Direct3D.
So, let's start with seeing if D3DX is the cause, get that to a known and verified state, and work from there.
I ask this because it's obvious that the problem you have is either with the depth buffer or with matrix transforms. We seem to have ruled out the depth buffer, and DirectQ uses functions from the D3DX library for matrix transforms. If you have an "unofficial" version of one of the D3DX DLLs then I can't legislate for what that version might or might not be doing.
Even if you haven't I would advise that you update your DirectX again. This time, before updating, go to C:\Windows\system32 and either delete the d3dx9_*.dll files or move them to somewhere else. Then go to http://www.microsoft.com/directx and use the websetup to download and install the files you're missing.
Let me know how that goes.
WHAT I NOW BELIEVE IS HAPPENING
A 3D co-ordinate system can be either right-handed or left-handed (there are other systems too, but let's ignore them for now). OpenGL by default uses RH, Direct3D by default uses LH. Direct3D does also provide functions to use a RH system if you want, and DirectQ uses them to avoid messing with the base data.
Something on your machine does not like this. Either you have a bad driver, a bad installation of Direct3D or a bad installation of D3DX. It's not using the RH system at all, despite having been told to do so, and despite it being a required part of Direct3D.
So, let's start with seeing if D3DX is the cause, get that to a known and verified state, and work from there.
-
mh - Posts: 2292
- Joined: Sat Jan 12, 2008 1:38 am
50 posts
• Page 3 of 4 • 1, 2, 3, 4
Who is online
Users browsing this forum: No registered users and 2 guests