Shaderator is a productivity library intended to speed up complex Compute Shader development. It also provides means to Unit Tests shader code offering protection against regressions. Click on the image below to see the Lighting Talk from ACCU 2018 Conference.
Due to the nature of GPUs shaders are hard to debug. Back in the day developer wrote one, executed a batch and hoped for the best that the result is correct. Kernel function is usually executed hundreds of thousand times writing data to output buffer which can only be looked up when the Dispatch finished. This tool compiles .hlsl shader code to C++ and enables developer to leverage full Visual Studio debugging functionality to quickly find problems in the code.
If you use VS Code install recommended extensions from
configs/recommended_extensions.json
Install compiler and build tools
sudo apt-get install -y cmake build-essential gdb
Shaderators uses CMake to setup and run the build process.
Run the following commands to build:
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=ON ..
make
CMake will download the neccessary dependencies like GoogleTests.
To execute unit tests run from command line run
ctests --verbose
When using VS Code and all the recommended extensions were installed, then tests should be visible in the 'Test Explorer UI'.
Two ways of working were tested:
- using Visual Studio Code
- using Visual Studio 2022
Just follow the IDE instructions to configure project with CMake.
You can build using CMake extension, by just pressing build after the project was configured.
Run tests from eg. Test explorer UI.
Place breakpoint anywhere in the shader code to break.
NOTE: Hitting breakpoints require Debug build, so be sure to build this configuration.
Install VS with Google Test support.
- Open Shaderator.sln in VS 2022
- Build solution (better choose Debug configuration to see more variables under debugger)
- Set
BitonicSortproject inexamplesfolder as startup project (right click on the project in Visual Studio and select "Set as StartUp Project") - Put breakpoint anywhere in ComputeShaderSort11.hlsl shader file
- Press F5 to Debug
VS will start regular debugging session and you will be able to debug the .hlsl shader code as C++ code. You can see all variables, can add them to watch, pin or look-up values when hovering the mouse. CPU shader is obviously very slow. The intention is to provide tools for faster Computer Shader development.
If you have Visual Assist X installed debugging experience may be reduced.
- Open Shaderator.sln in VS 2022
- Build solution
- Set processor architecture for Unit Tests. In VS menu go to "Test -> Test Settings -> Default Processor Architecture" and select the platform for which you have built the solution (X86 or X64).
- Open Test Explorer. In VS menu go to "Test -> Windows -> Test Explorer"
- In Test Explorer right click on the Unit Test found and press "Run Selected Tests" or "Debug Selected Tests"
There are several examples in folder examples how to write a test for you shaders/kernels. The idea is not leave the production code as much untouched as possible, but it's not always possible. Sometimes variables or data types need to be wrapped in a Shaderator macros.
You also need to write an executor which will handle input and exectution of your specific kernel.
There are examples for:
- Direct Compute HLSL
- OpenGL GLSL
- OpenCL C
Functionality for your specific kernel may be missing and would need to be added. If that is the case please submit an issue or feature request on github.
Not yet, the project is in it's early phase, however it should work with many shaders. If there is interest, support for more HLSL language features will be added. At the moment matrices are not supported yet.
Submit any issues on github. Feel free to contact the author directly with information available on github.