stayscrisp, on 10 July 2012 - 01:40 AM, said:

It didn't really include a library, as much as it did make one. I know how to make applications in DirectX, but this book so far had gone over wrapping all the DX code into it's own library, and then exporting it to use in other projects as a .lib file. It just threw me off how the author stated that you don't need to link the DirectX files to the actual .lib project, and shouldn't get any linker errors (which I did). But after linking the DirectX libraries to the project, it compiled fine. I'm not too good with the whole Debug/Release stuff yet, as i'm more concerned with learning the language before I learn about getting working EXEs and all that. Appreciate all the help though, always get it here

I'm using the brackets to include the code. It's a custom engine being built around DirectX, more so that I don't have to use DirectX code after I finish this engine. I didn't link anything yet, which is why i'm confused at VS finding the other include files, but not that one. Linking it works, but I wasn't sure if that was what I wanted to do when it came to an engine.

Sweet that's what I was thinking. Thanks guys, appreciate the help!

Thanks everyone for the advice! I might give directx another shot, but if I decide against it, ill try what you guys told me. Possibly starting with xna. Again, thanks guys!

Also, sorry for the double post, I can't figure out how to edit my old one

I was looking at Unity, but it looks like you have to use their environment. Can you just use it as a plain old engine with say, Visual Studio? Or is Unity just an engine attatched to the environment they created?