When the application is in use, the rendering of the dataset and therefore the user interface looks fine, but the nature of the simulation does not behave as expected. In this experiment, you wrote a fluid dynamics emulator that uses DirectCompute to perform most of the computationally intensive parts of a simulator update. Use the Graphics Pipeline Stages window and the HLSL debugger to check the compute shader that is causing the problem. Use the graphics event call stack to determine if the compute shader is being executed by the Dispatch Directcompute event type. Use the chart list event to find new sources of error. This walkthrough shows how to use Visual Studio’s graphical diagnostics to investigate an estimate that a shader is producing incorrect results. Select Pipeline Stages from the Detailed Graphics Diagnostics toolbar to open the Graphics Pipeline Steps window.Select the third submit competition (which immediately precedes the Sketch event) and then in the Graphics Pipeline Stages window”In the Compute Shader section, select Start Debugging.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |