Hi, I actually have the exact same error (same configuration, VS11 preview on Win7 x64). However, it seems that if you don't enable the debug layer, the problem goes away (InputLayoutCreation returns S_OK, and everything is fine: in PIX, the InputLayout is what is expected). What is even stranger, is that shader reflection still works fine, and loading offline compiled shaders seem to exhibit the same problem, so this seems to point to a corruption at the debug layer level (however, I don't have the skills in assembly to understand what's happening).
That sounds pretty strange... The only way that I know of to give the SDK headers precedence is to move their inclusion to the first place in the list of directories. That means to put it before any other standardized inclusions (in my projects it is listed as so: "$(DXSDK_DIR)Include;$(IncludePath)") I am discussing the topic with some MS guys, so I'll let you know if there is anything else to try out...
[quote name='Razispio']
By the way, Jason, I am using your library (Hieroglyph) and it's really great. I just have some minor gripes in some places (why using a custom TArray or a custom math library?), but in general it just works fine, so thanks!
[/quote]
That's great - I appreciate your feedback. I must admit that if I started over I probably wouldn't roll my own stuff from scratch, but I started writing Hieroglyph almost 10 years ago when I was just starting out... it was a bit of a learning exercise, and I just never saw a compelling reason to remove it. Who knows though - I could eventually migrate to another standardized system down the road...
I would be really interested to see some screenshots of something you build with it - it might even be cool to add a user page on the codeplex site... Thanks again!
EDIT: one other thing I just thought of - you are still trying to use a feature level 11 device right? Specifically, you aren't passing the 11.1 feature level to the device creation method? I just wanted to double check...