Direct2D 1.1 Development Notes Special Effects (4) graphic debugging, direct2d1.1

Direct2D 1.1 Development Notes Special Effects (4) graphic debugging, direct2d1.1
Zookeeper

(For more information, see the source)

As described in the preceding section, this section describes how to debug a graph.

Unfortunately, Microsoft has not added the graphic debugging function for VS Express 2013 for Windows Desktop (WDExpress.

For paid version VS (VS2013 pro is free for students and instructors), the graphic debugging function is provided:

Debugging-graphics-enable Diagnosis

You can.

For the free version, VS Express 2013 for Windows (VSWinExpress) has the graphic debugging function.

Fortunately, a paid version, WDExpress, and VSWinExpress can coexist (from top to bottom WDExpress, VSWinExpress, VS2013 Pro ):

If you already have a paid version, you can skip the following section:

# Ifdef WDExpress = 1

If only WDExpress is installed on your computer, download and install VSWinExpress.

After the operation is successful, use the menu:

File -- open the project -- select the compiled exe file

Please note that you must directly run this program to see if it can be run, because some files (images and so on) are not in the same folder and you need to copy them.

You can.

# Endif

Then debug (Debugging-graphics-enable DiagnosisOr Alt + F5)

A new tab page is generated.

For the previous section "static", we can choose to capture one frame, dynamically select several more frames, and then click capture (or press the screen printing key.

Double-click a captured frame to open the debugger:

You can select the required window in the VIEW. The "graphic event list" is the painting step of the entire frame. Select "draw"

You can also view the rendering pipeline in this step:

In the image, just click:

Select the play button next to the pixel shadow to view the detailed steps of the Shader for this pixel (step-by-step debugging)

We can see that the coordinate information of this point is (0.53xxx, 0.38xxx)

The rest is NaN, because you didn't use these variables and the compiler optimized them directly. You can write waste code to view the values of these variables.

Of course, this is the graphic debugging tool provided by VS. It provides limited D2D debugging functions, and D3D is more convenient.

Major graphics card dealers also provide their own debugging tools, such

NSight of core graphics card

Amd gpu PerfStudio 2

Intel Graphics Performance Analyzers

Well, this is here.

Zookeeper