Hi,

    I'm kind of repeating a previous request so I may or may not recieve help. Is anyone able to recieve detailed debug info using SetDebugConfiguration on the IXAudio2 interface or through setting the registry values as documented in the March 2008 DirectX SDK?

    The only output I am recieving is regarding loaded Assemblies and Exception data whether I use registry settings or the SetDebugConfiguration method.

    Thanks in advance.

:)

You create the XAudio2 interface with the XAUDIO2_DEBUG_ENGINE flag in XAudio2Create(), right? Also, what version of VS do you use?

---

We are boki. The rest is known.
The not so known part of the rest: It is Björn or Bjoern, but never Bjorn.

Yes, sorry about that. Forget to say which version. I'm using Visual C++ 2008 express edition. And I am using the XAUDIO2_DEBUG_ENGINE flag.

Thanks

Well, it works in my C++ 2005 Express - with native code, but I saw native DX debug output while debugging managed applications, too. A quick look at the options in 2008 (I do not have the DXSDK installed there so I cannot confirm or deny your observations) do not reveal any new settings that would mess around with unmanaged debug output during managed debug sessions.

---

We are boki. The rest is known.
The not so known part of the rest: It is Björn or Bjoern, but never Bjorn.

Thanks for your help. I've been through the settings myself within 2008 and I could not find anything that looked out of place. Think it may be necessary to to do a clean reinstall of everything.

:(

I don't see any reason why what you've done wouldn't work.

Of course, neither SetDebugConfiguration nor the registry values do anything in the retail XAudio2 DLL, so the first thing to do would be to sanity-check that you're really getting XAudioD2_0.dll loaded.  VC's module list should tell you that, or the DLL load messages, or ProcExp (great tool - Google it).

If that's not the problem (and I'm sure it isn't), I'd guess that the debug spew is being produced but not displayed, for some reason.  If you're willing to try the low-level debugger toolkit at http://www.microsoft.com/whdc/devtools/debugging, it will almost certainly work and may help you figure out the problem.  (Just run your app under windbg.exe and watch the output.)

Dugan