C# new Video() - OS Lock
Author
I am trying to play a video using the Video class in C# but i initialized it in CreateDevice() and ResetDevce and both ways it gives my OS lock.
You shouldn't need to create a device to play a video. It should just be:
Video vid = new Video("yourVideo.mpg", false);
vid.Owner = this;
vid.Play();
-AJ
Video vid = new Video("yourVideo.mpg", false);
vid.Owner = this;
vid.Play();
-AJ
Author
Yes, I did mean LoaderLock and I got DirectX 2.0 yet when I use it I get compatibility issues with Direct3D and Direct3DX. There are no 2.0 versions for them and things like Mesh are now included in DirectX and Direct3DX at the same time.
Quote:Original post by brwarner
Yes, I did mean LoaderLock and I got DirectX 2.0 yet when I use it I get compatibility issues with Direct3D and Direct3DX. There are no 2.0 versions for them and things like Mesh are now included in DirectX and Direct3DX at the same time.
When you use the DirectX 2.0 assembly, you should not reference Direct3D and Direct3DX. However, be aware that there are quite a few differences between the 1.1 and 2.0 assembly.
Author
I deleted the refrences to the DIrect3D and Direct3DX libraires and updated the Common files with the Febuary release however there are still some issues
dxmut____ - Caps could not be found
dx_______ - Custom Vertex could not be found
dxmut____ - GraphicStream could not be found
Draw Text Format could not be found
I dont remember all the file names as they are on a seperate computer but shouldnt they be compatible with the Febuary release because I got them from its common folder?
dxmut____ - Caps could not be found
dx_______ - Custom Vertex could not be found
dxmut____ - GraphicStream could not be found
Draw Text Format could not be found
I dont remember all the file names as they are on a seperate computer but shouldnt they be compatible with the Febuary release because I got them from its common folder?
DrawTextFormat has become DrawStringFormat
The rest, well really you should go to the beta newsgroups (http://msdn.microsoft.com/directx/beta/default.aspx) as the readme states and where a lot of these things are already covered.
MDX 2.0 is not a drop in replacement, many things have changed names, other things have changed the way they work (mostly for the best), and other things are currently missing because.... well its a beta.
I covered some of the renaming on an older beta http://www.thezbuffer.com/articles/291.aspx
The rest, well really you should go to the beta newsgroups (http://msdn.microsoft.com/directx/beta/default.aspx) as the readme states and where a lot of these things are already covered.
MDX 2.0 is not a drop in replacement, many things have changed names, other things have changed the way they work (mostly for the best), and other things are currently missing because.... well its a beta.
I covered some of the renaming on an older beta http://www.thezbuffer.com/articles/291.aspx
Quote:
I dont remember all the file names as they are on a seperate computer but shouldnt they be compatible with the Febuary release because I got them from its common folder?
If you want to use the COMMON files with MDX 2.0 you need to use the set of files in the same folder that begin with W (for Whidbey)
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
