# Debugging

We can't use breakpoints or print strings in deformer graphs, so we need to use other methods to debug compute kernels. Thankfully, there are a few ways to do this.

<figure><img src="https://3558733374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPratlX5Y75g7mK9upu8G%2Fuploads%2FPNO6769fx9MB9zkCoAcO%2FCapture.PNG?alt=media&#x26;token=b2e75863-6dc9-4a99-b850-0485b66dc46a" alt=""><figcaption></figcaption></figure>

One way is to write vertex colors to the Color pin. For example, say you had a resource buffer containing vertex indices that you want to apply an effect to. If you wanted to check which vertex indices are in the buffer, you could write a kernel to output the color red.

<figure><img src="https://3558733374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPratlX5Y75g7mK9upu8G%2Fuploads%2F41UbbjIY74aPaX7IybW5%2FCapture.PNG?alt=media&#x26;token=921603f6-77c7-46ac-97d6-4ad2d8ce1f2d" alt=""><figcaption></figcaption></figure>

The above code would check the vertex buffer for indices that do not contain a value of 0, and output the color red for those indices. In this case you can assume the buffer has already been populated with values somewhere else (ex. in the setup graph, or elsewhere in the update graph).&#x20;

We could then create a material to access the vertex color data and apply it to our skinned mesh (the same one that the deformer graph is also applied to).

<figure><img src="https://3558733374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPratlX5Y75g7mK9upu8G%2Fuploads%2FXiZXq3OQWubHyCvxJ9rP%2FCapture.PNG?alt=media&#x26;token=2d11fed9-4d41-47d9-b001-d34113b12782" alt=""><figcaption></figcaption></figure>

This would give us a visual indication of which vertices the deformer graph is acting on.
