Get Dir. X working?
That is almost certainly a compile-time error, not a linker error, but if Visual C++ can't find the header file, it would say so first. Very strange. If no-one else suggests anything more sensible, I'd try reinstalling everything at this point. Sorry that is not very helpfull.
Check in your directory settings, the include directory for the SDK must be topmost.
AFAIK an older version of ddraw may be included in your Visual Studio which doesn't have DirectDraw7 yet.
AFAIK an older version of ddraw may be included in your Visual Studio which doesn't have DirectDraw7 yet.
I think it has DD7, rumors say that winXp has DX8 or 9 installed from the start.
I just noticed that it doesent want to include the files that is under the directory c:\...\Microsoft DirectX SDK (April 2006)\Include. Can i tell vc++ to not ignore this folder, or should i move all the .h files to c:\...\VC98\Include. Then its problably the samt thing with the lib directory. Am i wrong?
I just noticed that it doesent want to include the files that is under the directory c:\...\Microsoft DirectX SDK (April 2006)\Include. Can i tell vc++ to not ignore this folder, or should i move all the .h files to c:\...\VC98\Include. Then its problably the samt thing with the lib directory. Am i wrong?
Hmm, i think the later DirectX SDKs will not properly install with VS6 anymore. You can probably get older stuff working (like DirectDraw), but with D3DX you'll get into trouble.
As it will not install properly you'll have to do the registration with Visual Studio yourselves. There should be a option called "Customize" somewhere (Menu "Tools" or "Extras"). In there you should find a tab with a list of directories for different kinds. One of these should be include files. There you have to add a new item on top with the include path to your "c:\...\Microsoft DirectX SDK (April 2006)\Include". You should do the same with the lib folder under the "library path" item. This allows VS to look into that include folder and also find the lib files.
The names of the items will differ as i don't have access to VS6.
As it will not install properly you'll have to do the registration with Visual Studio yourselves. There should be a option called "Customize" somewhere (Menu "Tools" or "Extras"). In there you should find a tab with a list of directories for different kinds. One of these should be include files. There you have to add a new item on top with the include path to your "c:\...\Microsoft DirectX SDK (April 2006)\Include". You should do the same with the lib folder under the "library path" item. This allows VS to look into that include folder and also find the lib files.
The names of the items will differ as i don't have access to VS6.
Quote:
AFAIK an older version of ddraw may be included in your Visual Studio which doesn't have DirectDraw7 yet.
I was thinking about this too.
You could search for multiple ddraw.h files on your system.
Also search for LPDIRECTDRAW7 in your ddraw.h file.
If everything looks ok, I would have to suggest either installing an older version of DirectX SDK, or install MSVC++ 2005 express and Microsoft Platform SDK.
Quote:Original post by slutbit
I dont know much programming, just the most simple commands. Im trying to follow the very first DirectX examples with ddraw.h and ddraw.lib I found in a book called "Windows Game programming for dummies" by André Lamothe.
For starters, it's not a good book. It never was. Further, it refers to a dated version of DirectX, and it makes numerous assumptions as to the reader being in a contemporary era - making the book harder to read now. For instance:
Quote:Different post by slutbit
I think it has DD7, rumors say that winXp has DX8 or 9 installed from the start.
Windows XP has DirectX 8 runtimes pre-installed, not the Software Development Kit (SDK). You have to download the SDK yourself, regardless of version, and it's so much easier to find and download the DX9 SDK now.
My recommendations:
- Download and install Microsoft Visual C++ 2005 Express Edition. It's free, and it's monumentally better than Visual C++ 6.0.
- Download and install the Microsoft Windows Platform SDK. It's necessary to develop Win32 applications using MSVC++ 2K5 EE.
- Download and install the Microsoft DirectX 9.0 April 2006 SDK. It includes documentation and tutorials to get you up to speed on the basics.
- Finally, return here for help with any step, and for tips on where to go after you've got everything running.
Quote:Original post by Endurion
Hmm, i think the later DirectX SDKs will not properly install with VS6 anymore.
Correct. VS6 is now completely unsupported by the DirectX team; while you might get DirectDraw working with it, there are no guarantees, and attempting to bludgeon it into submission may lead to more subtle and insidious bugs.
Get 2005 Express instead. It's free, fully supported, and IMHO a lot better.
I still use VS6 and DX7 and on occasion I have to reinstal everything. They work, but you have to mess around with setting directories and link your project to the lib files properly. My recomendations are to make sure the folder you installed the SDK to have relatively simple names (no brackets or spaces if possible) and to include the drive and path to the libraries in your linker settings. In short, don't trust long filename support and go back to the ol' 8.3 names (at least for the folder names).
If possible it'd be best if you can use the latest tools and libraries. The learning curve is about the same if you have a good book and once you're through a few tutorials your more up to speed with the rest of the world. The stuff I write only uses dx7 and I feel as though I'm way behind everybody else. (If dx7 could do alpha blending i might defend using it more, but it doesn't.)
If possible it'd be best if you can use the latest tools and libraries. The learning curve is about the same if you have a good book and once you're through a few tutorials your more up to speed with the rest of the world. The stuff I write only uses dx7 and I feel as though I'm way behind everybody else. (If dx7 could do alpha blending i might defend using it more, but it doesn't.)
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement