Your modified shader code is stored in a separate file to preserve the integrity of your project's original HLSL source file, but when you're satisfied with your changes you can choose Copy to.
Instead, the HLSL debugger supports Edit & Apply, which allows you to edit HLSL source files and then choose Apply to regenerate the frame to see the effect of your changes. The HLSL shader debugger doesn't support Edit & Continue in the same way that the CPU debugger does because the GPU execution model doesn't allow shader state to be undone. Nevertheless, the HLSL debugger provides a better, more CPU-like debugging experience than would be possible otherwise. You can add variables and registers to the Watch window, but expressions are not supported. It's not possible to debug an app and its shader code at the same time. The HLSL debugger doesn't support edit-and-continue, but you can make changes to your shaders and then regenerate the frame to see the results. However, the HLSL debugger is currently limited in the following ways: This is what gives the HLSL debugger a CPU-like debugging experience. This means that the work of the shader can be simulated on the CPU, where its inner workings are in full view. Because a graphics log contains enough information to recreate any part of the output, and because Graphics Analysis provides tools that can help you pinpoint the exact pixel and event where an error occurs, the HLSL debugger only has to simulate the exact shader thread that you are interested in. Graphics Analyzer recreates captured frames by using information that was recorded in a graphics log the HLSL debugger does not monitor GPU execution in real time as it runs shader code. However, because GPUs achieve high performance by running shader code on hundreds of threads simultaneously, the HLSL debugger is designed to work together with the other Graphics Analyzer tools to present all of this information in a way that helps you make sense of it. You can inspect the contents of variables, set break points, step through code, and walk up the call-stack, just like you can when you debug other languages. Debugging HLSL code in Visual Studio resembles debugging code that's written in other languages-for example, C++, C#, or Visual Basic.
The HLSL debugger can help you understand problems that arise in your shader code. The HLSL debugger in Visual Studio Graphics Analyzer helps you understand how your HLSL shader code operates under real conditions of your app. Applies to: Visual Studio Visual Studio for Mac Visual Studio Code
0 kommentar(er)
