Hi,
I'm converting a game project to MDX2.0 (becuase with 1.1 it doesnt run properly on my new 64 bit setup - but thats another story)
Here's my problem:
First compile error: Microsoft.DirectSound.Device is multiply defined in DIrectSound.dll and DirectX.dll (2.0)
Action: remove refernce to DirectSound.dll
Second compile error: Microsoft.DirectSound.SecondaryBuffer is not defined
... becuase that was is the DirectSound.dll !!
What the hell am I doing wrong here Can it really be that MS have made it imposible to use a DirectSound.SecondaryBuffer along with in MDX 2.0
Any help greatly appreciated. ta.
Games with sound impossible in MDX 2.0
Gliksman
SecondaryBuffer is renamed to EffectsBuffer in MDX 2.0
Lots of things are renamed in in MDX 2.0 for consistency and to follow .net guidelines. Based on Tom's blog I expect some of the same names to make it to XNA framework.
I did some analysis of the API changes back in October: MDX 2.0 API changes they may help.
MDX 1.1 works fine with .NET 2.0 with one slight issue that is easy to solve (solving LoaderLock with MDX) so you may also want to follow Davids advice.
Richard.C.Bower
More accurately, MDX 2.0 is deprecated. From the readme:
Microsoft is working on a new managed gaming framework which will target Windows and Xbox 360 known as the XNA Framework. The majority of what exists today as the Managed DirectX 2.0 beta will become a key component of the XNA Framework. The MDX 2.0 libraries will remain unchanged as of the April 2006 SDK release and will continue to ship as a beta in DirectX SDK releases until a beta of the XNA Framework is made available. While we are striving to deliver a smooth transition from code written to use the Managed DirectX 2.0 beta, Microsoft can make no guarantees about the API compatibility between the Managed DirectX 2.0 beta and the upcoming graphics API’s in the XNA Framework. Microsoft will be providing guidance about the API differences as well as migration assistance as more information becomes available regarding the XNA Framework.
I recommend returning to MDX 1.1.
57Ford
stevenb01
Hi,
Thanks for the advice, I will check out the info on API changes.
The reason I moved to MDX2.0 was because I am experiencing a problem http://forums.microsoft.com/MSDN/showpost.aspx postid=397956&siteid=1 which I have written about and no one has been able to solve. I believe it may be related to using MDX1.0 with x64 architecture and OS. I have read that MDX2.0 includes 64 bit dlls so i thought I'd give it a try.
If anyone could shed some light on my original problem I'd be delighted.