🔒 Locked

DirectX debugger delay

Started by Blackhole12 Oct 4, 2008 at 9:03 PM 1 replies 500+ views

Original Post

Oct 4, 2008 at 9:03 PM

When I have a debugger attached to my program (on both debug and release), the initialization of the DirectX9 runtime hangs for about 5 seconds.

DX3D = Direct3DCreate9(D3D_SDK_VERSION);

I first noticed this a few months ago when I was updating the drivers for my graphics cards - the most recent update caused this to occur, so I opted for a slightly older version of the drivers to avoid it. However, this problem is now being caused by a change to the August 2008 SDK. I decided to update my graphics driver to the most recent revision, to no avail. This hang does not occur on either debug or release if there is no debugger attached. Whats more interesting is that when debugging the direct3D9 C++ examples that are included with the SDK, the delay is even more obvious - 10 seconds. What in the world could be causing something like this? It can't be the device settings, because the delay is caused by the initialization of the directX runtime before any settings are specified or could be specified.

ET3D

139

ET3D

Oct 5, 2008 at 9:10 AM

If you're running Vista, try playing with the Privilege level of Visual Studio. If you're running as administrator trying removing that. I'm not sure it'd do any good, but IIRC there was some effect to that.

Blackhole12

Author

Blackhole12

Oct 5, 2008 at 3:19 PM

The only way I could find to remove its administrative privileges was to run it in compatability mode for windows XP SP2, but that didn't seem to fix anything.

Topic Locked

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