Thanks for the reply. I followed the steps you outlined. However, in place of the DDI Version, the directx diagnostic tool is displaying: "Feature Levels: 9.3,9.2,9.1". I've attached a screenshot as well as uploaded all the info saved from the tool.
The DirectX 9.0c Control Panel includes access to a variety of configuration settings. Installation is easy: just copy the directx.cpl into the Windows/system32 folder. After installing the DirectX CPL file, you have the chance to access the Control Panel from your Settings menu.
Besides C++ code, writing shader code is another big part of building DirectX games. The Visual Studio shader editor recognizes HLSL, FX, and other types of shader files, and provides syntax highlighting and braces auto-completion, making it easier to read and write shader code. Debugging shader code from a captured frame is another great way to pinpoint the source of rendering problems. Simply set a breakpoint in your shader code and press F5 to debug it. You can inspect variables and expressions in Locals and Autos windows. Learn more about the HLSL Shader Debugger.
Troubleshooting issues in the code can be time-consuming. Use the Visual Studio debugger to help find and fix issues faster. Set breakpoints in your C++ code and press F5 to launch the debugger. When the breakpoint is hit, you can watch the value of variables and complex expressions in the Autos and Watch windows as well as in the data tips on mouse hover, view the call stack in the Call Stack window, and step in and step out of the functions easily. In the example in the screenshot below, the Autos window is showing us the data in the constant buffer and the value of each member of the device resource object instance, making stepping through DirectX code easy and efficient. 2b1af7f3a8