If you include d3d11.h that should be enough as that should include all of what you need, you might need to include dxgi.h as well.
I'm including the following, but it still can't find the definition.
#include <dxgi.h>
#include <d3dcommon.h>
#include <d3d11_1.h>
#include <d3dcompiler.h>
I searched the whole "windows kits\8.0\include" directory but the only definition of D3DERR_INVALIDCALL is inside d3d9helper.h.
Apparently the problem is just that the documentation is not updated about the fact that they dropped the error codes that begin with D3DERR_.
Inside winerror.h I could find all the definitions for dxgi, d3d10 and d3d11 errors, but they are named and defined differently, for example:
//
// DXGI error codes
//
//
// MessageId: DXGI_ERROR_INVALID_CALL
//
// MessageText:
//
// The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect.
// Enable the D3D debug layer in order to see details via debug messages.
//
#define DXGI_ERROR_INVALID_CALL _HRESULT_TYPEDEF_(0x887A0001L)
where _HRESULT_TYPEDEF_ is just
#define _HRESULT_TYPEDEF_(_sc) ((HRESULT)_sc)
Apparently the problem is just that the documentation is not updated about the fact that they dropped the error codes that begin with D3DERR_.
i suspected something like this.
was there a specific directx 11.1 routine that said it returned d3derr_invalid call? no, cause you were using create dev & swap chain, just like i was a few days ago myself. so you were just trying to trap and process the documented return codes, eh? too bad their docs suck.
as soon as i saw that create dev and swap chain returned s_ok instead of d3d_ok, i realized dx11 error codes are a whole new ballgame.
they apparently have both the june 2010 and win 8 docs posted on msdn, identical info. apparently true for june 2010 sdk, and not for win8 sdk. you may want to "send a comment to microsoft about this document".
Yes, I was getting some errors so I wanted to catch all the possible return codes.
I sent a mail, hopefully they will update the documentation.
