🔒 Locked

Direct X debug versions

Started by compugeekpro Mar 24, 2006 at 8:31 PM 1 replies 1.3k views

Original Post

Mar 24, 2006 at 8:31 PM

I have checked my Direct x files using dxdiag (direct x diagnotstics) and have found that my d3dx9d.dll and d3d9d.dll are debug versions. According to the notes, the debug versions run slower than the full retail versions. Do I really have a performance loss in games? I have a 7800 GT and it does seem a little slow (maybe due to the debug files). Are those two files used frequently in games such as Battlefield 2? If it is a performance hit, can I replace the files somehow with the retail version without reinstalling direct x? By the way, I have the Direct x sdk...is that what installed these files in my System32 folder? Thanks. -Sean-

MikeWW

Mar 24, 2006 at 8:54 PM

Hi,

You are correct in thinking that d3d9d.dll is the debug version, but it's existance simple means that you have the DirectX SDK installed (as you say you have). To find out which version (debug or retail) of Direct3D is being currently used go into the DirectX section of the Windows Control Panel and in the Direct3D tab you will see two radio buttons in the top left that specify whether or not the debug runtimes should be used instead of the retail run times (as well as settings for the amount of debug spew the debug runtimes should give). You can thankfully change which runtime is being used without a restart.

I find it helpful to place a shortcut to the DirectX control panel icon on the desktop so that I can quickly switch between the runtimes as I need to.

Hope this helps,

Mike.

DXnut

Mar 25, 2006 at 12:44 AM

Actually, you specify which DLLs to use in Project/Properties/Linker/Input. By specifying which .LIB files you want, you are specifying the DLLs to use.

So, you can set the LIBs for your debug compiles to the debug versions (ending with the "d") and the retail compile to use the retail versions.

Selecting retail/debug from the control panel adds additional options to the amount of debugging to perform and the output levels (how verbose it is in the debug window).

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.